Has anybody got the following setup working?:
VMWare-Player version=2.5.1 build=build-126130
Windows 2000 as host, Linux-Debian as guest, guest can access the PhysicalDrive0 of host.
In this combination if vmware-player tries to access PhysicalDrive,
there is following error message in the log file:
Feb 25 13:44:20.656: vmx| FILE: File_FullPath: _wfullpath failed on (
.\PhysicalDrive0): 0
Feb 25 13:44:20.656: vmx| AIOMGR: '
.\PhysicalDrive0': Failed to get volume sector size: Unknown error 0 (0x0) (0).
Feb 25 13:44:20.656: vmx| AIOWIN32C: Failed to Queue cmd: Disk sector size check failed (6).
Feb 25 13:44:20.656: vmx| FILE: File_FullPath: _wfullpath failed on (
.\PhysicalDrive0): 87
Feb 25 13:44:20.656: vmx| VMXAIOMGR: Retry on read "
.\PhysicalDrive0" : Disk sector size check failed.
Feb 25 13:44:20.656: vmx| VMXAIOMGR: fileio : err=6 errCode=0 freeSpace=-1
Feb 25 13:44:20.656: vmx| VMXAIOMGR: "
.\PhysicalDrive0" : read s=0 n=4096 ne=1
Feb 25 13:44:20.656: vmx| VMXAIOMGR: v[0]=2843000:4096
What means: "_wfullpath failed on (
.\PhysicalDrive0): 0" and then "_wfullpath failed on (
.\PhysicalDrive0): 87" ?
Ist it so that vmware-player tries to read the information about Disk sector size on different places?
If it is so, then a couple lines above, in the same log-file, I can see the following info:
Feb 25 13:44:20.656: vmx| DISKLIB-DEVCRW: Facts for
.\PhysicalDrive0: Cap=16992864 Phys C/H/S=16383/16/63 BIOS C/H/S=1024/255/63 Adap=IDE
Feb 25 13:44:20.656: vmx| DISKLIB-DSCPTR: Opened : "
.\PhysicalDrive0" 0 (0xa)
Feb 25 13:44:20.656: vmx| DISKLIB-LINK : Opened 'C:\Programme\DeviceImage\VDI\Auto\test.vmdk' (0xa): fullDevice, 16980705 sectors / 8.1 GB.
Feb 25 13:44:20.656: vmx| DISKLIB-LIB : Opened "C:\Programme\DeviceImage\VDI\Auto\test.vmdk" (flags 0xa).
It would mean that vmware-player can estimate the sector size and calculate the size of available place an the amount of sectors (16980705 sectors / 8.1 GB.).
Have somebody an idea for some sort of workaround in this situation?
Thanks in advance,
Jurasix
