nicometo
Contributor
Contributor

The Boot Camp Partition is not prepared to run as a virtual machine

Hello all, I am getting the error "The Boot Camp partition is not prepared to run as a virtual machine. It appears that Windows did not shut down cleanly the last time it was used." It goes on to explain a procedure to correct the error (please see the attached screen shot for the specifics) when attempting to use my Boot Camp partition in VMWare Fusion.

I have gone through the procedure numerous times to no avail. In searching these forums, I see some older posts about this, but nothing recent, and certainly nothing answered. I am wondering if anyone can lend some assistance with this issue.

For what its worth, the following are the specifics of my system;

MacBook Pro 2.6 GHz

200 GB Hitachi Drive, with a 60 GB NTSF Partition for Boot Camp

VMWare Version 1.1.3 (also tried the Beta version 2.0b1)

The Boot Camp volume, which works perfectly fine when booted directly to it is running Windows XP SP 3.

It was created using the Boot Camp Assistant, then I used Ghost to apply a standard corporate image.

The following is the log I get;

Jun 17 17:04:11.402: vmfusion| Log for VMware Fusion pid=2133 version=1.1.3 build=build-94249 option=Release

Jun 17 17:04:11.403: vmfusion| Hostname=R0175435.local

Jun 17 17:04:11.403: vmfusion| Using log file /Users/tsn03/Library/Logs/VMware Fusion/vmware-vmfusion.log

Jun 17 17:04:11.407: vmfusion| Msg_Reset:

Jun 17 17:04:11.407: vmfusion| http://msg.dictionary.load.statFailed Unable to get information about file "/Library/Application Support/VMware Fusion/messages/en/vmware.vmsg": No such file or directory.

Jun 17 17:04:11.407: vmfusion| -


Jun 17 17:04:11.407: vmfusion| Cannot load message dictionary "/Library/Application Support/VMware Fusion/messages/en/vmware.vmsg".

Jun 17 17:04:11.473: vmfusion| UUID: Unable to open /dev/mem: No such file or directory

Jun 17 17:04:11.545: vmfusion| Msg_Reset:

Jun 17 17:04:11.545: vmfusion| http://msg.dictionary.load.statFailed Unable to get information about file "/Library/Application Support/VMware Fusion/messages/en/tip_list.vmsg": No such file or directory.

Jun 17 17:04:11.545: vmfusion| -


Jun 17 17:04:11.545: vmfusion| Cannot load message dictionary "/Library/Application Support/VMware Fusion/messages/en/tip_list.vmsg".

Jun 17 17:04:11.617: vmfusion| HOSTDEV-MAC: HostDeviceInfo_FindHostSoundDevices: Found default sound devices .

Jun 17 17:04:11.622: vmfusion| Could not open /proc/net/dev

Jun 17 17:04:11.622: vmfusion| SGMAC: XXX: SGHostEnumerate not yet implemented

Jun 17 17:04:11.759: vmfusion| SMBIOS: can't open /dev/mem: Could not find the file

Jun 17 17:04:11.759: vmfusion| VmhsHostInfoPopulateSystem: Could not get information from smbios to populate VMDB.

Jun 17 17:04:11.759: vmfusion| UUID: Unable to open /dev/mem: No such file or directory

Jun 17 17:04:11.760: vmfusion| HOSTINFO: Seeing Intel CPU, numCoresPerCPU 2 numThreadsPerCore 1.

Jun 17 17:04:11.760: vmfusion| HOSTINFO: This machine has 1 physical CPUS, 2 total cores, and 2 logical CPUs.

Jun 17 17:04:11.864: vmfusion| Foundry Init: setting up global state (0 threads)

Jun 17 17:04:11.864: vmfusion| Foundry Init: version 2, hostType 1, hostName (null), hostPort 0, options 0x203

Jun 17 17:04:22.038: vmfusion| Cmd /host2/#_client/util/file/cmd/##4f/op/stat/ failed: Invalid path

Jun 17 17:04:22.312: | UUID: Unable to open /dev/mem: No such file or directory

Jun 17 17:04:22.314: | Reloading config state: /Users/tsn03/Library/Application Support/VMware Fusion/Virtual Machines/Helper/naos-1.0.vmwarevm/temp.vmx

Jun 17 17:04:22.445: vmfusion| readlink /var/run/vmware/3b37a0b126365e6259bc5be70a9a3156: No such file or directory

Jun 17 17:04:22.450: vmfusion| readlink /var/run/vmware/%2fUsers%2ftsn03%2fLibrary%2fApplication%20Support%2fVMware%20Fusion%2fVirtual%20Machines%2fHelper%2fnaos%2d1%2e0%2evmwarevm%2ftemp%2evmx: No such file or directory

Jun 17 17:04:22.503: vmfusion| DISKLIB-LINK : "NAOS 1.0-SCSI_0-1.vmdk" : failed to open (The system cannot find the file specified).

Jun 17 17:04:22.503: vmfusion| DISKLIB-CHAIN : "NAOS 1.0-SCSI_0-1.vmdk" : failed to open (The system cannot find the file specified).

Jun 17 17:04:22.503: vmfusion| DISKLIB-LIB : Failed to open 'NAOS 1.0-SCSI_0-1.vmdk' with flags 0x17 (The system cannot find the file specified).

Jun 17 17:04:22.503: vmfusion| VMHS: failed to open 'NAOS 1.0-SCSI_0-1.vmdk' : The system cannot find the file specified (27).

Jun 17 17:04:22.503: vmfusion| Cmd /host2/#_client/util/disk/cmd/##89/op/getDiskInfo/ failed: The system cannot find the file specified

Jun 17 17:04:23.041: vmfusion| VMHSVMCbPower: Setting state of VM /vm/#eb2a5b0c46a54c70/ to powerOn with option hard

Jun 17 17:04:23.042: vmfusion| VMHS: Exec()'ing /Library/Application Support/VMware Fusion/vmx/Contents/MacOS/vmware-vmx, /Users/tsn03/Library/Application Support/VMware Fusion/Virtual Machines/Helper/naos-1.0.vmwarevm/temp.vmx

Jun 17 17:04:23.173: vmfusion| Mounting virtual machine paths on connection: /db/connection/#120/, /Users/tsn03/Library/Application Support/VMware Fusion/Virtual Machines/Helper/naos-1.0.vmwarevm/temp.vmx

Jun 17 17:04:23.194: vmfusion| Mount VM completion for vm: /Users/tsn03/Library/Application Support/VMware Fusion/Virtual Machines/Helper/naos-1.0.vmwarevm/temp.vmx

Jun 17 17:04:23.195: vmfusion| Mount VM Complete: /Users/tsn03/Library/Application Support/VMware Fusion/Virtual Machines/Helper/naos-1.0.vmwarevm/temp.vmx, Return code: OK

Jun 17 17:04:26.500: vmfusion| VMX status has been set for vm: /Users/tsn03/Library/Application Support/VMware Fusion/Virtual Machines/Helper/naos-1.0.vmwarevm/temp.vmx

Jun 17 17:04:26.500: vmfusion| Disconnect check in progress: /Users/tsn03/Library/Application Support/VMware Fusion/Virtual Machines/Helper/naos-1.0.vmwarevm/temp.vmx

Jun 17 17:04:26.500: vmfusion| Disconnect check in progress: /Users/tsn03/Library/Application Support/VMware Fusion/Virtual Machines/Helper/naos-1.0.vmwarevm/temp.vmx

Jun 17 17:05:40.432: vmfusion| Disconnect check in progress: /Users/tsn03/Library/Application Support/VMware Fusion/Virtual Machines/Helper/naos-1.0.vmwarevm/temp.vmx

Jun 17 17:05:40.432: vmfusion| Unmounting the vm: /Users/tsn03/Library/Application Support/VMware Fusion/Virtual Machines/Helper/naos-1.0.vmwarevm/temp.vmx

Jun 17 17:05:40.432: vmfusion| Unmounting VM complete: /Users/tsn03/Library/Application Support/VMware Fusion/Virtual Machines/Helper/naos-1.0.vmwarevm/temp.vmx

Jun 17 17:05:40.828: vmfusion| HardwareVersion::SetHardwareVersion: Invalid HW version: 1.

Jun 17 17:05:40.829: vmfusion| HardwareVersion::SetHardwareVersion: Invalid HW version: 1.

Jun 17 17:05:40.853: vmfusion| HardwareVersion::SetHardwareVersion: Invalid HW version: 1.

Jun 17 17:05:40.853: vmfusion| HardwareVersion::GetVMMaxMemory: Invalid HW version: 1.

Jun 17 17:05:40.854: vmfusion| HardwareVersion::SetHardwareVersion: Invalid HW version: 1.

Jun 17 17:05:40.854: vmfusion| HardwareVersion::GetVMMaxMemory: Invalid HW version: 1.

Jun 17 17:05:40.854: vmfusion| HardwareVersion::SetHardwareVersion: Invalid HW version: 1.

Jun 17 17:05:40.854: vmfusion| HardwareVersion::GetVMMaxMemory: Invalid HW version: 1.

Thanks to anyone with any help.

0 Kudos
2 Replies
WoodyZ
Immortal
Immortal

The Boot Camp volume, which works perfectly fine when booted directly to it is running Windows XP SP 3.

It was created using the Boot Camp Assistant, then I used Ghost to apply a standard corporate image.

That may have something to do with it as the last time I looked Ghost, depending on the version you're using, was not fully compatible with GPT (GUID Partition Table). What version of Ghost did you use?

Copy and paste the following command in a Terminal (/Applications/Utilities/Terminal) and post the output. Note if disk0 is not the correct disk then use the appropriate number.

"/Library/Application Support/VMware Fusion/vmware-rawdiskCreator" print /dev/disk0

You could also try the following...

1. Close Fusion

2. In a Terminal (/Applications/Utilities/Terminal) copy and paste the following command and then press Enter and it will remove the Boot Camp partition Virtual Machine meta data. Note: This does not effect the Boot Camp partition install of Windows. Also be sure you copy the entire command line below from "rm" at the beginning to the " (quote) after the s in Machines. Smiley Happy

rm -dfr "/Users/$/Library/Application Support/VMware Fusion/Virtual Machines"

3. Reboot the Host Mac OS X

4. Start Fusion and select Boot Camp partition and click Run

nicometo
Contributor
Contributor

Thanks for the response. I have all ready tried removing the VM, rm -dfr "/Users/$/Library/Application Support/VMware Fusion/Virtual Machines", but that didn't work too well.

Ghost is Ghost32 version 11.0.

Lastly, here is the last command...

Nr Start Size Type Id Sytem

1 1 409639 BIOS EE Unknown

2 409640 261881856 BIOS AF HFS+

3 262553640 128168288 BIOS B Win95 FAT32

Message was edited by: nicometo - Added Ghost version number

0 Kudos