I get the impression that the code in WS 8 that handles the usage of physical disks with a VM is a regression of what we had with earlier versions.
So far I noticed:
If you experience similar issues please post here.
I do not want to discuss details here - justy collect a list of the new problems with WS 8
Please also include a link to your original post - if there is one.
Thanks Ulli
I'm experiencing identical Physical Disk in Use message after upgrading from Workstation 7 while trying to run Linux OS from the same disk my Windows (with Workstation 😎 is installed on. This is a regression from WS7 for me.
I can't say anything for performance, since I couldn't get it to work even after several VM restarts.
I hope this helps,
Jernej
Identical situation for me.
After upgrade to VMware Player 4.0 I'm unable to run virtual machine (Kubuntu 64bit) with access to two physical partitions. Error displayed:
Cannot open the disk 'G:\Virtual Machines\KUbuntu 64-bit\KUbuntu 64-bit-12.vmdk' or one of the snapshot disks it depends on.
Reason: The physical disk is already in use.
Nothing has helped to solve the problem so far. My host OS: Win7 64 Pro.
I have just solved mine - installed previous version :smileyangry:
Player 4 (based on WS 😎 - does not work. Player 3 (based on WS 7) - works just fine on XP. Same system, same OSs, same disks.
At the same time, Player4/WS8 works fine on Windows 7 (I have 3 physical disks - XP, W7 and Linux - I attach Linux disk as physical to VM) - go figure.
Try to add user __vmware__ with Full Access rights to file "filename.vmdk". This works in my case.
Unfortunately, this did not work for me. Could you post more details?
If I remember correctly there is/was an issue with physical disks in earlier versions of Workstation on a Windows host. Whether it still exists in WS8 I don't know. I only have noticed this problem on Vista hosts or later. To access a physical disk without any problems it sometimes must be taken offline in the host. For example for me to access a vista guest that resides on a physical disk I must take that disk offline. Vista and Win7 etc do something weird, accessing partitions and holding locks on them even if they aren't actually assigned driver letters. Most people don't know about that but I remember you heavily active in vms for a long time-- I remember your BSD VM article from a long time ago-- so maybe you do.
Compound that with most people don't know how to take a disk offline. You usually have to use the command line from what I remember (diskpart). VMWare could do a much better job of explaining this issue.
The fragmentation issue I have no idea. One thing I noticed immediately since switching to WS8 is it told me for some of my VMs that they were fragmented. None of them were direct access though.
Strange.. "Successfully locked volume", "Successfully dismounted volume"... and then "IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS failed on volume". Did you tried to run VMware Player as Administrator?
P.S.
I'm using VMware Workstation 8.
Oh, wait, did you checked "Use entire disk" OR "Use individual partitions"?
NetSpider wrote:
Oh, wait, did you checked "Use entire disk" OR "Use individual partitions"?
Use individual partitions. Two of them are actually used.
2011-11-17T18:38:32.280+01:00| vmx| I120: W32Util_DismountVolumes: IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS failed on volume \\?\Volume{6b560058-d546-11e0-a467-005056c00008}: 87
\\?\Volume{6b560058-d546-11e0-a467-005056c00008 - looks like this volume is in use.
Run from command prompt:
mountvol
This command will show you the list of mounted volumes e.g.
\\?\Volume{e6d459d5-7840-11e0-af4d-806e6f6e6963}\
C:\
\\?\Volume{e6d459d6-7840-11e0-af4d-806e6f6e6963}\
D:\
Find in this list volume with ID: \\?\Volume{6b560058-d546-11e0-a467-005056c00008 and hope you will get the answer.
Volume with this ID \\?\Volume{6b560058-d546-11e0-a467-005056c00008} is one of three partitions not being used by VM. Two physical disks are in RAID1 managed via Windows dynamic disks, and have three partitions. One of them is causing problems. These disks have nothing to do with other physical disk used by vmware, but ... I disabled RAID1 on them and virtual machine started without problem!
So problem has been solved. Thank you!
I'll try to re-enable mirroring tomorrow, hope the problem is not directly related to presence of RAID1 in the system.
I think you cannot use this volume in Virtual machine and in Windows at the same time. Windows cannot free this Volume for you because it is always used by its software RAID in exclusive mode.
NetSpider wrote:
I think you cannot use this volume in Virtual machine and in Windows at the same time. Windows cannot free this Volume for you because it is always used by its software RAID in exclusive mode.
But it worked in previous version! Anyway, volume which caused problems is not used in Virtual machine at all.
Edit: with mirroring enabled, the problem returned. I'm forced to downgrade again, or forget Windows-based RAID1.
Continuum,
Here http://communities.vmware.com/thread/337285?tstart=0 is the link to my findings on the first issue.
bnod
Another strange problem with VMWare.
I have 4 disks:
DISKPART> list disk Disk ### Status Size Free Dyn Gpt -------- ---------- ------- ------- --- --- Disk 0 Online 373 GB 484 KB * Disk 1 Online 373 GB 216 GB * Disk 2 Online 466 GB 0 B Disk 3 Online 1863 GB 0 B
First two of them are Dynamic, so I've created mirrored partition C:\ (156 GB)
After mirror was built I can't boot OS in VMWare and get the following error:
vmx| I120: DISK: OPEN ide0:0 'D:\VM\back\HDD2.vmdk' persistent R[]
vmx| I120: W32Util_DismountVolumes: Locking and dismounting volumes backed by a particular disk area (offset 0 size 500107862016) on PhysicalDrive2...
vmx| I120: W32Util_DismountVolumes: IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS failed on volume \\?\Volume{e6d459d5-7840-11e0-af4d-806e6f6e6963}: 234
vmx| I120: W32Util_CloseDismountHandle: Unlocking and closing handles for 0 volumes on PhysicalDrive2...
vmx| W110: DISKLIB-FLAT : Open: Failed to dismount physical drive 2. Perhaps its volumes have open files on them?
vmx| I120: DISKLIB-FLAT : "\\.\PhysicalDrive2" : failed to open (73): .
vmx| I120: DISKLIB-LINK : "D:\VM\back\HDD2.vmdk" : failed to open (The physical disk is already in use).
vmx| I120: DISKLIB-CHAIN : "D:\VM\back\HDD2.vmdk" : failed to open (The physical disk is already in use).
vmx| I120: DISKLIB-LIB : Failed to open 'D:\VM\back\HDD2.vmdk' with flags 0xa The physical disk is already in use (73).
vmx| I120: DISK: Cannot open disk "D:\VM\back\HDD2.vmdk": The physical disk is already in use (73).
vmx| I120: Msg_Post: Error
vmx| I120: [msg.disk.noBackEnd] Cannot open the disk 'D:\VM\back\HDD2.vmdk' or one of the snapshot disks it depends on.
vmx| I120: [msg.disk.configureDiskError] Reason: The physical disk is already in use.
When I've deleted software mirror - VMWare start works just fine:
Is this bug of MS Windows or VMWare? :smileyconfused:
P.S.
\\?\Volume{e6d459d5-7840-11e0-af4d-806e6f6e6963} - is the UUID (UNC) of C:\ (Disk 0) :smileyshocked:
Hi,
I have found the same error-situation concerning access to PhysicalDisk (VMware-Player v. 3.1.6 and v.4.0.0).
Testing both verions of VMwPlayer we are using the same hardware and the same host-OS (Win 7 Professional x64bit).
Log-part for VMwPlayer 3.1.6:
Oct 20 13:11:35.005: vmx| DISK: OPEN scsi0:0 'C:\Program Files (x86)\Test\Test-0.vmdk' persistent R[]
It is clear now, that beginning with version 4.0.0, a completely new method of accessing the physical drives is implemented. The question is, is it an intention to completely close the access to physical drives or it is only a temporary state of development? Are there some configuration options which could allow us to ignore the new method of access to physical drives?
Thanks for reply,
Jurasix