VMware Communities
Talos2000
Contributor
Contributor

Fusion does not detect Bootcamp partition after resize

I have fusion 2.0.3 running under OSX 10.5 on a brand new MacBook Pro. Out of the box, I used Bootcamp to creat a 40G dual-boot partition for windows. I installed 64-bit Vista on that partition. Back in OSX, I installed Fusion. It automatically detected the Windows partition. For several days I have successfully Vista within Fusion. Then my 40G partition filled up and I had to increase it. Long story. I used Winclone to clone the 40G partition. I used Disk Utility to erase and delete the 40G partition, and to re-size the Mac partition to fill the whole disk. Then I used bootcamp to re-partition the drive to create a new 80G windows partition. I used Winclone to re-build the Vista image onto the 80G partition. I cold-booted into Vista, and everything was just as I left it. Back in OSX, I ran VMware Fusion, but now it cannot find my bootable Vista disk partition, and I don't see any obvious way to hook it up. How to I fix this?

Reply
0 Kudos
3 Replies
WoodyZ
Immortal
Immortal

Note: These direction are different then what have previously been posted so read and follow through... Note: These steps assume you have a single Apple default install of Windows on a single Boot Camp partition and a single default VMware Fusion Boot Camp partition Virtual Machine (without a snapshot*) and if you have modified the Boot Camp partition Virtual Machine to add additional Hard Drives either Virtual or RAW Disk then do not use these directions unless you backup the Boot Camp partition Virtual Machine Package first. *Also note that Fusion 2.0.0 could accidentally have a Snapshot with the Boot Camp partition Virtual Machine and it shouldn't have been allowed to, so you should check to make sure that condition does not exist as well. (With Fusion closed if the Boot Camp partition Virtual Machine Package is over 1 MB in size then you could have a Snapshot in place and do not proceed with these directions.)

===

1. If Fusion is open then close it.

2. In a Terminal (/Applications/Utilities/Terminal) copy and paste the following command, as is, and then press Enter and it will remove the Boot Camp partition Virtual Machine meta-data and the Helper Virtual Machine.

Note: This does not effect the Boot Camp partition install of Windows in that it doesn't delete it. Also be sure you copy the entire command line below, as is, from "rm" at the beginning to the " (quote) after the s in Machines.

rm -dfr "/Users/$/Library/Application Support/VMware Fusion/Virtual Machines" 3. Start Fusion (/Applications/VMware Fusion) and select Boot Camp partition on the Virtual Machine Library window and then start the Boot Camp partition Virtual Machine. Note: The next two events can be reversed depending on Fusion 1.x or Fusion 2.x. although it doesn't really matter as both events should occur. Next, one should see a Boot Camp partition message stating "VMware Fusion is preparing your Boot Camp partition to run as a virtual machine. This may take a few minutes. This will happen once." Next, an Authenticate dialog box appears. "VMware Fusion requires that you type your password." Enter your Name and Password then click OK. (This is necessary to unmount the Boot Camp partition for Fusion to have direct access to it.) === When the Boot Camp partition Virtual Machine boots for the first time after this VMware Tools may want to or will install/update and reboot the Boot Camp partition Virtual Machine. === If at any point the preparing Boot Camp partition Virtual Machine fails then... The vmware.log file from the Helper Virtual Machine will be needed so in a Terminal (/Applications/Utilities/Terminal) copy and paste the following command, as is, and then press Enter and it will copy the target vmware.log file to your Desktop as Helper_vmware.log and you can then archive and attach the file to a reply post. Also be sure you copy the entire command line below, as is, from "cp" at the beginning to the g in Helper_vmware.log. cp "/Users/$/Library/Application Support/VMware Fusion/Virtual Machines/Helper/naos-1.0.vmwarevm/vmware.log" ~/Desktop/Helper_vmware.log

Reply
0 Kudos
admin
Immortal
Immortal

Delete the Boot Camp metadata (e.g everything in /Users/$/Library/Application Support/VMware Fusion/Virtual Machines)

Reply
0 Kudos
Talos2000
Contributor
Contributor

Thanks for this detailed set of instructions. The assumptions you listed in your introductory notes did indeed apply, and the process solved the problem immediately.

Thanks also to etung who also took time to post a solution.

Reply
0 Kudos