The file specified is not a virtual disk vmware workstation как исправить

Hi everyone,

first I have to thank you to let me understand how to fix the VM boot issue.

I want to add my experience extending what already did by André (a.p.). This because the .vmdk files posted by André  – I think – cannot work for anyone.

In my case, quite similar to the one posted by rezeq1989, I had:

– to make a chkdsk /r/f

     so one of the .vmdk file changed its size to zero;

– create a new virtual disk with the same size of the disk not recognized by the VM player;

– replace the zero byte .vmdk file with the one of the new created .vmdk files; in case the zero byte .vmdk file is the last of the series, than, the new created .vmdk file to use for replacement should be the last as well (that is smaller than the others).

That’s all.

Gigi

В этой статье мы расскажем о возможных причинах, по которым не запускается виртуальная машина VMware Workstation. Мы рассмотрим самые распространённые ошибки, а также разберём, почему они возникают и как их исправить.

Ошибка VMware Workstation and Device/Credential Guard are not compatible

При включении VMware Workstation на Windows 10 может возникнуть ошибка со следующим текстом:

VMware Workstation and Device/Credential Guard are not compatible. VMware Workstation can be run after disabling Device/Credential Guard. Please visit http://www.vmware.com/go/turnoff_CG_DG/ for more details

Чаще всего эта ошибка возникает из-за того, что включено ПО Device Guard — оно помогает защитить систему от вредоносных файлов. Device Guard позволяет настроить список файлов, которые Windows будет считать безопасными. Если на компьютер попадут файлы, которые не входят в список, система автоматически удалит их. Работе VMware в таких случаях мешает компонент Hyper-V.

Как исправить

Чтобы исправить ошибку, отключите Hyper-V с помощью функционала «Выполнить».

Ошибка Cannot open the disk

Ещё одна распространенная ошибка при запуске виртуальной машины в VMware — Cannot open the disk. Её текст следующий:

An unexpected error was received from the ESX host while powering on VM.

На следующей строке будет указана одна из причин этой ошибки. Разберём, что означает каждая:

1) Failed to lock the file. Это значит, что процесс, который вы используете, не может открыть файл. При этом файл используется другим процессом. Что может привести к ошибке:

• при работе с ВМ вы пытаетесь запустить вторую ВМ, используя тот же VMX-файл,
• вы запустили ВМ с подключенным диском при помощи утилиты vmware-mount,
• вы добавили виртуальный диск к ВМ, которая уже используется.

2) The parent virtual disk has been modified since the child was created. Эта ошибка возникает, если повреждён снимок ВМ.

3) The destination file system does not support large files означает, что на целевом хранилище невозможно открыть файл ВМ того же размера.

4) Could not open/create change tracking file. Эта проблема может возникнуть, если файл filename-ctk.vmdk создавался ранее и не очищался перед созданием новой ВМ. Здесь filename — это название вашего файла.

5) Cannot allocate memory. Тот случай, когда в модуле VMFS не хватает места.

6) The file specified is not a virtual disk возникает в случаях, если повреждён .VMDK-файл дескриптора.

7) Insufficient permission to access file. Такая проблема может возникнуть при использовании хранилищ типа NFS. Она сообщает о том, что экспорт NFS работает неправильно, так как права на чтение и запись файла не даны либо даны некорректно.

Как исправить

Единого решения для этого типа ошибки нет. Чаще всего причина связана с локальными настройками компьютера. Рекомендации по исправлению ошибки описаны в официальной документации.

I am running Windows 10 using VMware Workstation 16 on my Window 10 Laptop. All was well until I put my VM into suspended mode and then put my computer to sleep for the night. Once I booted it up it gave me an error saying that it couldn’t find the virtual disk (sorry I don’t have the exact error message). So, I provided it a VMDK file from yesterday. Now I am getting this error.

The file specified is not a virtual disk

Cannot open the disk 'C:Users[user]DocumentsVirtual MachinesWindows 1809 - BoxWindows 1809 - Box-000005-s015.vmdk' or one of the snapshot disks it depends on.

Module 'Disk' power on failed.

Failed to start the virtual machine.

I must’ve given it the wrong vmdk file. But when I go to Settings, it is not letting change the file path to a different vmdk.

VMWare VM settings:

I have two questions:

1. Why did the VM loose track of the VMDK disk when I put it into suspended mode?
2. How can I give VMware the correct VMDK so that the VM will boot up again?

Не запускается виртуальная машина в VMware Workstation

В этой статье мы расскажем о возможных причинах, по которым не запускается виртуальная машина VMware Workstation. Мы рассмотрим самые распространённые ошибки, а также разберём, почему они возникают и как их исправить.

Ошибка VMware Workstation and Device/Credential Guard are not compatible

При включении VMware Workstation на Windows 10 может возникнуть ошибка со следующим текстом:

Чаще всего эта ошибка возникает из-за того, что включено ПО Device Guard — оно помогает защитить систему от вредоносных файлов. Device Guard позволяет настроить список файлов, которые Windows будет считать безопасными. Если на компьютер попадут файлы, которые не входят в список, система автоматически удалит их. Работе VMware в таких случаях мешает компонент Hyper-V.

Как исправить

Чтобы исправить ошибку, отключите Hyper-V с помощью функционала «Выполнить».

Откройте командную строку от имени администратора. Поочередно выполните команды:

Затем перезагрузите компьютер.

Ошибка Cannot open the disk

Ещё одна распространенная ошибка при запуске виртуальной машины в VMware — Cannot open the disk. Её текст следующий:

На следующей строке будет указана одна из причин этой ошибки. Разберём, что означает каждая:

1) Failed to lock the file. Это значит, что процесс, который вы используете, не может открыть файл. При этом файл используется другим процессом. Что может привести к ошибке:

• при работе с ВМ вы пытаетесь запустить вторую ВМ, используя тот же VMX-файл,
• вы запустили ВМ с подключенным диском при помощи утилиты vmware-mount,
• вы добавили виртуальный диск к ВМ, которая уже используется.

2) The parent virtual disk has been modified since the child was created. Эта ошибка возникает, если повреждён снимок ВМ.

3) The destination file system does not support large files означает, что на целевом хранилище невозможно открыть файл ВМ того же размера.

4) Could not open/create change tracking file. Эта проблема может возникнуть, если файл filename-ctk.vmdk создавался ранее и не очищался перед созданием новой ВМ. Здесь filename — это название вашего файла.

5) Cannot allocate memory. Тот случай, когда в модуле VMFS не хватает места.

6) The file specified is not a virtual disk возникает в случаях, если повреждён .VMDK-файл дескриптора.

7) Insufficient permission to access file. Такая проблема может возникнуть при использовании хранилищ типа NFS. Она сообщает о том, что экспорт NFS работает неправильно, так как права на чтение и запись файла не даны либо даны некорректно.

Как исправить

Единого решения для этого типа ошибки нет. Чаще всего причина связана с локальными настройками компьютера. Рекомендации по исправлению ошибки описаны в официальной документации.

Источник

Vmware workstation 15 player error while powering on

I am using Player 15.5.7 on a Windows 10 host. The guest is Ubuntu 21.04. I am trying to add a physical drive (USB flash) as a second hard drive within the VM. The USB drive contains a multipartitioned bootable (not live) Ubuntu 21.04 installation. The purpose of this exercise is to use commands (e.g., dd) and tools (e.g., Systemback) installed on the USB drive to make images and clones of the guest system when it is not running.

A previous answer suggests that using a physical disk in a VM requires that no drive letters be assigned. This is not a problem: Windows diligently reminds me, every time I plug in the Ubuntu USB drive, that it must reformat that drive before it can assign drive letters. The previous answer also states that the disk should be flagged as offline in diskmgmt.msc . This is apparently not an option for a Linux drive.

I can set up the USB drive as a second hard drive in Player’s Settings, assigned to PhysicalDrive4 (its entry in diskmgmt.msc ). But when I run the VM, I get this:

Error while powering on: The physical drive is already in use

Cannot open the disk ‘W:Ubuntu-0.vmdk’ or one of the snapshot disks it depends on.

Module ‘Disk’ power on failed.

Failed to start the virtual machine.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I am not sure if this will help what you are trying to achieve. You could also have a writeable ISO mounted as a USB device of the VM.

Have a look at this thread/post.

In the same thread, there is also a method to mount VMDK as a USB device (but this is probably not what you want).

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I cannot answer your question, but the purpose interest me.

If you want to «make a clone of the guest when it is not running», why don’t you just use Windows robocopy to create, in a reliable manner, an identical copy (which can be called a clone)? It stops being identical when you open it and answer «I copied it». When you run it, it also stops being identical, for networking purposes, if you don’t have a static network configuration — otherwise, it will be indentical for networking . which behavior you may or may not want to achieve.

I think that a reliable OS copy is more reliable than «dd», which does not handle possible disk errors.

But yeah, you might mean something else altogether?

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Thanks for your reply.

For more on the purpose, see https://raywoodcockslatest.wordpress.com/2021/08/18/vmware-v2p. Basically, this is a V2P effort. I can’t see my original message in this reply page; not sure if my question stated that explicitly.

I wasn’t aware that Windows robocopy could clone the Linux guest’s ext4 or swap partitions as a solution internal to the VM. Most Windows tools seem unable to see such filesystems. But without the desired physical drive solution, I would still need to run Windows from an ISO inside the VM to run its robocopy command against the VM’s Ubuntu installation. I don’t have a bootable Windows ISO, but I welcome links to good guidance on how to create one.

Maybe you mean that I should run robocopy in the Windows host, as an external solution. That would copy the VM. But I don’t believe that would get me any closer to creating a bootable Linux ISO or physical clone of the VM.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I meant strictly the latter. However, your term «physical clone of the VM», only now got my attention. You meant to achieve a physical computer, which meaning I missed. I don’t know what a generic solution to that would be. However, back in the day, I created physical computers into a bootable CD/DVD (where bootable ISO was the intermediate step, if I remember right), using Puppy Linux distro. It had «mastering» built in. On top of that, you could use more extreme editors for changing the «boot initialization files» (for instance control what the OS loads initially). I haven’t seen such mastering anywhere else. Puppy Linux is still there with many different variations (where Ubuntu compatible version is one of them). Maybe you can Master a Puppy Linux ISO with Ubuntu software, too — not sure — barebone, Puppy, sure it can be Mastered.

The above doesn’t obviously give you Ubuntu Linux mastered version.

As for Windows ISOs, you can freely download them from Microsoft. For activation you need a license, but almost everything works without activation (on Windows 10).

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Sounds like the disk is mounted by Windows anyways, even while it cannot read the partition. and if you can’t set it as «off line» then I»m not sure if there’s anything you can do about it.

Perhaps you can set it to be assigned to the VM automatically. I’m not sure how helpful that would be as that setting is AFAICR per host.
The «use a USB disk to access physically from a VM via a (RDM) raw device mapping» is a bit of an exercise that is bound to be a painful one.

Our forum’s expert @continuum might have some ideas about it.
He certainly is the one who can give you tips for the P2V/V2P scenario, if he has the time.

I’d say that his old live CDs would be the better option here.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I think you guys are right. Having glanced at those old live CDs, it does seem that this may require remastering. I know the word. I know less of what it might entail. It could get out of my depth pretty quickly.

I think the only bootable ISOs from Microsoft are installers, not systems ready-to-run.

It appears the best step at this point may be to retry with the Ubuntu VM on a Linux host. At least there won’t be the problem that the host prevents the VM from seeing the physical drive.

Thanks for your quick replies and suggestions.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

OK, your target is actually a mastered live-Ubuntu version. I can see many different possibilities in this:

a) Edit the current Ubuntu ISO. Not sure how this is going to work — not in my expertise at all. Anyway, Ubuntu ISO is both: live and installable.

b) Use a project which was said to be «How you create your own Linux distro from scratch». I haven’t tried that, but the idea seems relevant. Not sure if they are targeting from both live and installable.

c) Use some other distro, which is really targeted for live use. Ubuntu live is only so and so compared to Puppy Linux. In comparison, Ubuntu live is very slow and cumbersome. Puppy is lightning fast on any computer, because it works from RAM and is very small to load. Ubuntu live uses the media a lot — obviously, if USB-3 is supported, Ubuntu live might be bearable, with a slow media, it is not.

With a live distro, you also have the problem how you save your data from a live session. Puppy has that all figured out with many possibilities. (One being that the boot media is completely safe from outside hacks). In my remastering, I was also shielding the computer hard disks from the Puppy live user.

I’m very disappointed with current Ubuntu versions from the perspective of an average or newbie user . they don’t even try to fix (within same LTS version anyway) obvious bugs and missing functionality that was there with previous versions and there any many such things. So, depending on your audience, a different distro might be better.

Puppy has its shortcomings, like, in short, a missing user-model, but I’m not sure if any of that matters on a live-boot (every user can have their own boot media anyway, as one example).

d) Not sure if the Ubuntu VM is the correct source. It is NOT working on the physical computer, but on VMware — for instance, all the drivers are wrong. Not really my expertise, but that seems to be the case. So, that’s why I didn’t first understand that you are trying to create a physical-computer-compatible boot from a VM-computer.

(And yes, sorry, my reference to Microsoft ISOs was installation ISOs, so a wrong reference.)

Источник

Vmware workstation 15 player error while powering on

I have used VMware 12 player for a long time with almost no problem at all.

When I tried to find out if that installation was 32 or 64 bit I find WMware player 15 available.

My Pc is recently improved with Samsung SSD 500GB for C: and run nicely.
But now I can not use new installation of VMware 15 Player.

I would be very happy if someone can help me out.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Solved the problem myself!

VMware 15 stored de old locations of OS installed, even when it got wrong info after partition change on the HD. That completely blocked all new installetions and only responded with error warning and disappered on the screen. When all registres was erased and empty a new installation was OK without any old wrong info.
So next step is to istall new OS again and start from the beginning.

I am now very happy to have it working again.

This was not a final working slolution! Windows 10 Home ver. 1809 was not compatible with VMware 15 player.

Final solution was to erase all data related to VMware 15 player.
Then a download of VMware 14 Player and install.
Now it works perfect, even with old VMware 12 player sored OS material..

When it got located. om my new SSD it was amazing better performace.

I can leave it for a time if other can be helpted by my finding how to solv it.

Источник

Vmware workstation 15 player error while powering on

I just loaded vmware player ver3. I have a GM service manual database that has to be run on VMware player but I continue to get the following error

Any help would be appreciated

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Has anyone come accross a fix for this other than downgrading? We’ve installed Player 3.1.0 but recieved this error on some machines. Downgrading to 2.5.2 (the last release our organization allowed before 3.1.0) seems to fix this error. We want to upgrade to 3.X but need to find a solution to this problem!

Running Win XP Prof SP3 as host and VM.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Come on — which one ?

VMplayer 3 has massive issues with USB-devices — is that what you are talking about ?

Part of those issues can be fixed — but we need input

________________________________________________
Do you need support with a VMFS recovery problem ? — send a message via skype «sanbarrow»
I do not support Workstation 16 at this time .

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I figured it was self explanatory to the thread I was replying on.

«Error while powering on: internal error».

The VM doesn’t start at all, it resides in a folder on C:; RAM varies between 1GB-4GB depending on the user; VMs are standardized so it’s not a VM a user created

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

can you run other VMs ?

can you run VMs if you disable USB for the VM ?

can you start VMs if you disable the vmusbarbservice on the host ?

what driver does your GM device use ? — is it a USB-device ?

what driver is used for the USB-root-hubs on your host ?

________________________________________________
Do you need support with a VMFS recovery problem ? — send a message via skype «sanbarrow»
I do not support Workstation 16 at this time .

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Ok, so after some troubleshooting and testing I’ve come up with the following:

1) VM’s are all stored locally in a folder on C:

2) Can’t run other VMs (even new VMs)

3) Can’t run VMs if USB is disabled

4) Can’t run VMs if vmusbarbservice is disabled on the hose

5) No USB drivers are being used

6) USB-root-hubs is the Windows built-in

Uninstalling, doing a /clean and then re-installing VMware Player seems to fix the errors.

Errors seem to happen when VMware Player is pushed through SCCM and installed.

SCCM is updating from 2.5.2 to 3.1.0

Could modifying VMware Player’s dislay name reg key have anything to do with the errors?

Источник