Help VMware is preparing Boot Camp for every?

[katman13]

I'm running System Version: Mac OS X 10.5.1 (9B18) Boot Camp And I get a box "Boot Camp Partition" : Vmware Fusion is preparing your Boot Camp partition to run as a virtual machine. And just set there, and never stops. Help?

[jettca1]

I'm right there with you. Any help out there?

[MandarMS]

Please try the following:

1) Go to ~\Library\Application Support\VMware Fusion\ and delete the virtual machines folder

2) Go to Startup Disk and reboot into Windows

3) After you boot into Windows, then boot back into the Mac

4) Launch VMware Fusion, select Boot Camp partition and click Run

[rcardona2k]

, do you really mean for the users to delete the "Helper" VM folder in the Virtual Machines folder?

[MandarMS]

not the "Helper" folder but just the Boot camp folder

[rcardona2k]

not the "Helper" folder but just the Boot camp folder

Thanks the "Boot Camp" folder is one folder level below the "Virtual Machines" folder in the path above. I was just making sure, so the Helper folder would not get deleted accidentally.

[admin]

I don't think it matters, I would expect Fusion to recopy the helper VM from /Applications/VMware Fusion.app/Contents/Resources/naos-1.0.vmwarevm/ if it were missing.

[rcardona2k]

At least one user has had to copy the helper manually to have naos run properly. I know the naos VM is embedded in the Fusion.app (I'm tempted to it delete it). I was just saying if that initial 80 MB copy were avoidable it might be better. Do you think naos can get into 'wedged' state requiring it to be re-copied? I think that VM starts in a non-persistent mode so it runs fresh every time? I would be interested in hearing about any cases where naos might need to be refreshed. Thanks.

[jettca1]

I'll give that a try. Currently, I'm stuck in Windows for some work stuff, but I'll be up for air in an hour or so

More soon...

[jettca1]

Ok, VMware has been churning again on my boot camp partition for about 15 minutes.

It says "This may take a few minutes." How many is "a few"? 15, 500?

Thanks for your continued assistance.

[jettca1]

Additionally, this is after following the above procedure of deleting ~/Library/Application Support/VMware Fusion/Virtual Machines/Boot Camp/, rebooting into Windows, and rebooting into Mac OS X.

Currently, an ls -l of ~/Library/Application Support/VMware Fusion/Virtual Machines/Boot Camp/ yields this:

total 0

drwxr-xr-x 3 jett staff 102 Dec 21 02:51 %2Fdev%2Fdisk0

drwxr-xr-x 3 jett staff 102 Dec 21 02:51 .

drwxrwxrwx 5 root staff 170 Dec 21 02:51 ..

Yes, 'jett' is my username.

[rcardona2k]

There's nothing special about the boot camp partition under _{/Library/Application Support, except where it's stored. I recommend moving or copying that VM that maps to the Boot Camp partition. In the Finder use Go > Go to Folder > and copy and paste what's inside the quotes: "}/Library/Application Support/VMware Fusion/Virtual Machines/Boot Camp". Open the %2Fdev%2Fdisk,,, folder and open the drag the Boot Camp partition bundle temporarily to the desktop, rename it, and move it into ~/Documents/Virtual Machines. Then double-click on it. If VMware asks whether you copied or moved the VM, choose "moved" (even if you made a copy).

This should bypass the "preparing" process and assuming your VM is OK it will boot the Boot Camp partition. If the VM is not adequately prepared you may get a blue screen of death (BSoD) with the stop code 0x7B. If it works great, if not, at least you tried.

[jettca1]

Success! While the moving of the machine didn't work, it lead me to check some permissions issues I'd been having on my machine lately. I highly recommend checking our this discussion on apple.com:

http://discussions.apple.com/message.jspa?messageID=6149364#6149364

It can create a whole world of pain for you, if it's happened.

When I double-clicked the machine, Fusion told me it was simply 'unable' to open it. I noticed the naos machine & decided to double-click that. Why not? How could I further break it? Fusion told me it's first intelligent thing:

Fusion is unable to create the directory ~/Library/Preferences/VMware Fusion/. Would you like to continue, even though this directory could not be created?

(that's a paraphrase by the way)

It so happened that Fusion had no write permissions to ~/Library/Preferences/. Sure explains a lot. I opened Terminal & executed the following command:

chmod 777 ~/Library/Preferences

I tried double-clicking the boot camp machine again, and it asked for my password (first time), so I knew something new was happening.

Eventually, it booted! Yay! I'm on my way now, installing VMware tools, etc...

Thanks for everyone's help!

[rcardona2k]

Permissions or ownership is a large part of the problems in these forums, especially with "archive and installs" of Leopard. It would be nice if Fusion managed these for the private files they create, e.g. chown -R username ../App Support/Virtual Machines and chmod to the right permissions, upon startup of the Boot Camp VM would be good.

[OWNAGE_TIME]

I'm having the same issues as described in this thread. Nothing is helping