VMware Communities
Flash2
Contributor
Contributor

ERROR: Could not create the virtual disk for your Boot Camp virtual machine.

Am running:

MacBook Pro 2.4GHz Intel Core 2 Duo with 4GB RAM.

Mac OS X 10.5.1

VMware Fusion Version 1.1 (62573)

Windows XP Pro SP2

Everything worked fine for several weeks. The trouble initially started after an OS X update arrived. VMware started reporting that it could not connect to peer process. In trying to fix this I upgraded the Fusion from 1.0 to 1.1. I also deinstalled VMware completely and removed all the library files.

On reinstalling it started the "Could not create the virtual disk for your Boot Camp virtual machine." when I tried to start the Boot Camp partition.

The Boot Camp partition works fine on it's own booting straight into windows.

In desperation I booted directly into Windows and deinstalled VMware tools then deleted every VMware file and reference that I could locate. Went back and deinstalled and deleted all traces of VMware from OS X too. Did a drive check and repair on both disks. Then reinstalled and IT STILL COMES UP WITH THE SAME ERROR!

Been at it 2 days now and it's driving me insane.

It will happily create new VMs that aren't on Boot Camp.

In the "/Users/yournamehere/Library/Application Support/VMware Fusion" folder there is only one folder and that is called "Virtual Machines" and inside that there is only one folder and that is called "Boot Camp" but there are no files inside any of these folders. To clarify, inside "/Users/yournamehere/Library/Application Support/VMware Fusion" there is only one thing, a folder called "Virtual Machines", and inside that there is only one thing, an empty folder called "Boot Camp". If I delete the "/Users/yournamehere/Library/Application Support/VMware Fusion" folder then it can recreate the aforementioned structure but nothing more.

Please help!

Reply
0 Kudos
5 Replies
Flash2
Contributor
Contributor

Oops should have added...

If I enable root, then I can go in under root and get everything working whilst logged in as root, but then on returning to the regular login get the same problem as before Smiley Sad

Reply
0 Kudos
Flash2
Contributor
Contributor

Went back in as root and got the Boot Camp partition working through Fusion again. Then back in as me (who is an admin) and it still wouldn't work. So I copied root's "Library/Application Support/VMware Fusion" folder over to my own folder. This time VMware reported that could not start the Boot Camp because it had insufficient permissions. So I tried selecting to "VMware Fusion" folder, doing File/Get Info, and modifying the permission through the GUI, but this operation crashed the finder on both myself and root. Went into Terminal as root and did "chmod -R 777" on the "VMware Fusion" folder and tried to start Boot Camp again through my own account, now I'm back to the "Failed to connect to peer process error".

The Boot Camp still runs under Fusion for root through...

Any ideas?

Reply
0 Kudos
Flash2
Contributor
Contributor

Deleted the "Boot Camp partition" file from within the "/Users/me/Library/VMware Fusion/Boot Camp/%2Fdev%2Fdisk0" folder and VMware could not recreate it. Then deleted the "/Users/me/Library/VMware Fusion/Boot Camp" folder itself and recreated it manually, exact same result, VMware could not create the "Boot Camp partition" file. No logs were created.

Replaced the "/Users/me/Library/VMware Fusion/Boot Camp/%2Fdev%2Fdisk0" folder with roots copy, and was back to the peer process error. Had deleted the logs in advance and it didn't create any new ones.

Am now going to look into fixing the peer process error as this seems to be closer to working...

Reply
0 Kudos
Flash2
Contributor
Contributor

Here is the console log:

01/01/2008 22:11:29 .com.vmware.fusion[723] Cannot load message dictionary "/Library/Application Support/VMware Fusion/messages/en/vmware.vmsg".

01/01/2008 22:11:29 .com.vmware.fusion[723] Cannot load message dictionary "/Library/Application Support/VMware Fusion/messages/en/vmware.vmsg".

01/01/2008 22:11:29 .com.vmware.fusion[723] VMXVmdbAccept_LocalPipe: Can't change to pipe directory , error 13.

01/01/2008 22:11:29 .com.vmware.fusion[723] VMXVmdb_Init: failed to accept

01/01/2008 22:11:29 .com.vmware.fusion[723] ASSERT bora/lib/sync/syncMutexPthread.c:65

01/01/2008 22:11:29 .com.vmware.fusion[723] Dumping core...

01/01/2008 22:11:31 .com.vmware.fusion[723] Child process 732 failed to dump core (status 0x6).

01/01/2008 22:11:31 .com.vmware.fusion[723] VMware Fusion Error:

01/01/2008 22:11:31 .com.vmware.fusion[723] VMware Fusion unrecoverable error: (vmx)

01/01/2008 22:11:31 .com.vmware.fusion[723] ASSERT bora/lib/sync/syncMutexPthread.c:65

01/01/2008 22:11:31 .com.vmware.fusion[723] A log file is available in "/var/folders/35/35QvMXslEbqnE6o2xyBUzk+++TI/-Tmp-//vmware-Laura/vmware-Laura-731.log". Please request support and include the contents of the log file.

01/01/2008 22:11:31 .com.vmware.fusion[723] To collect files to submit to VMware support, run "/Library/Application Support/VMware Fusion/vm-support.tool".

01/01/2008 22:11:31 .com.vmware.fusion[723] We will respond on the basis of your support entitlement.

Here is the VMware log:

Jan 01 22:11:29.745: vmx| Log for VMware Fusion pid=731 version=1.1 build=build-62573 option=BETA

Jan 01 22:11:29.746: vmx| Hostname=Macintosh.local

Jan 01 22:11:29.746: vmx| Command line: "/Library/Application Support/VMware Fusion/vmx/Contents/MacOS/vmware-vmx-debug" "-E" "en" "-D" "2AGHjwpggDSwAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=" "-#" "product=1;name=VMware Fusion;version=1.1;licensename=VMware Fusion for Mac OS;licenseversion=6.0 build-62573;" "-@" "pipe=/var/folders/35/35QvMXslEbqnE6o2xyBUzk+++TI/-Tmp-//vmware-root/vmx9c1389e65da8819c;readyEvent=10" "/Users/Laura/Library/Application Support/VMware Fusion/Virtual Machines/Boot Camp/%2Fdev%2Fdisk0/Boot Camp partition.vmwarevm/Boot Camp partition.vmx"

Jan 01 22:11:29.750: vmx| Msg_Reset:

Jan 01 22:11:29.750: vmx| 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.

Jan 01 22:11:29.750: vmx| -


Jan 01 22:11:29.750: vmx| Cannot load message dictionary "/Library/Application Support/VMware Fusion/messages/en/vmware.vmsg".

Jan 01 22:11:29.752: vmx| Ready event: 10

Jan 01 22:11:29.769: vmx| UI Connecting to pipe '/var/folders/35/35QvMXslEbqnE6o2xyBUzk+++TI/-Tmp-//vmware-root/vmx9c1389e65da8819c' with user '(null)'

Jan 01 22:11:29.769: vmx| VMXVmdbAccept_LocalPipe: Can't change to pipe directory , error 13.

Jan 01 22:11:29.769: vmx| VMXVmdb_Init: failed to accept

Jan 01 22:11:29.769: vmx| VMXVmdb_Init Failed: ret = VMDB failure

Jan 01 22:11:29.769: vmx| Flushing VMX VMDB connections

Jan 01 22:11:29.769: vmx| ASSERT bora/lib/sync/syncMutexPthread.c:65

Jan 01 22:11:29.769: vmx| Backtrace:

Jan 01 22:11:29.769: vmx| Backtrace[0] 0xbfffe718 eip 0x25357c

Jan 01 22:11:29.769: vmx| Backtrace[1] 0xbfffeb48 eip 0x013b3a

Jan 01 22:11:29.769: vmx| Backtrace[2] 0xbfffeb68 eip 0x19bce9

Jan 01 22:11:29.769: vmx| Backtrace[3] 0xbfffeb98 eip 0x21597b

Jan 01 22:11:29.769: vmx| Backtrace[4] 0xbfffec18 eip 0x1a58b6

Jan 01 22:11:29.769: vmx| Backtrace[5] 0xbfffec38 eip 0x0317b7

Jan 01 22:11:29.769: vmx| Backtrace[6] 0xbffff5b8 eip 0x0345db

Jan 01 22:11:29.769: vmx| Backtrace[7] 0xbffff688 eip 0x005d27

Jan 01 22:11:29.769: vmx| Backtrace[8] 0xbffff788 eip 0x006161

Jan 01 22:11:29.769: vmx| Backtrace[9] 0xbffff7c8 eip 0x0028c6

Jan 01 22:11:29.769: vmx| Backtrace[10] 0xbffff7e4 eip 0x0027e1

Jan 01 22:11:29.769: vmx| Backtrace[11] 00000000 eip 0x00000a

Jan 01 22:11:29.770: vmx| Dumping core...

Jan 01 22:11:31.770: vmx| Child process 732 failed to dump core (status 0x6).

Jan 01 22:11:31.770: vmx| Msg_Post: Error

Jan 01 22:11:31.770: vmx| http://msg.log.error.unrecoverable VMware Fusion unrecoverable error: (vmx)

Jan 01 22:11:31.770: vmx| ASSERT bora/lib/sync/syncMutexPthread.c:65

Jan 01 22:11:31.770: vmx| http://msg.panic.haveLog A log file is available in "/var/folders/35/35QvMXslEbqnE6o2xyBUzk+++TI/-Tmp-//vmware-Laura/vmware-Laura-731.log". http://msg.panic.requestSupport.withLog Please request support and include the contents of the log file. http://msg.panic.requestSupport.vmSupport

Jan 01 22:11:31.770: vmx| To collect files to submit to VMware support, run "/Library/Application Support/VMware Fusion/vm-support.tool".

Jan 01 22:11:31.770: vmx| http://msg.panic.response We will respond on the basis of your support entitlement.

Reply
0 Kudos
MandarMS
Expert
Expert

for peer process error please go through the thread http://communities.vmware.com/message/827674

Reply
0 Kudos