VMware

This Question is Answered

2 "helpful" answers available (6 pts)
9 Replies Last post: Nov 29, 2007 2:23 AM by uruiamme  

Fusion 1.1 DOESN'T SEE my BOOT CAMP partition posted: Nov 26, 2007 2:59 AM

Click to view uruiamme's profile Novice 24 posts since
Nov 26, 2007
I installed Fusion as a download trial for the first time. When I ran Fusion, it does not list my boot camp partition in the Virtual Machine Library, so I cannot use the program. My 30 day ticker is running with no way to evaluate it here.

VMware Fusion 1.1 (62573)
MacBook Pro 17" Core 2 Duo, 2GB RAM
OS X 10.4.11 (Just updated to this)
Windows XP SP2 running as a boot camp
Bootcamp beta 1.4

I have been using Boot Camp since I bought the Mac in December. Now, the beta version 1.4 is still installed, but obviously disabled now thanks to LOSERoBCLENSE (Leopard Operating SystEm revocation of Boot Camp LicENSEs). When I run Startup Disk in Mac OS X, it does NOT list the boot camp partition anymore. However, I have the Windows partition set to bootable (see my fdisk output below) and so I boot to my boot camp fine. I can also hit the Option key (formerly known as the ALT key) to choose my OS at boot time.

Here are a few caveats:
1. I installed Windows originally as FAT32. After languishing over the many crashes I had, I reluctantly converted it to NTFS so that Windows did not always boot up slow with the disk check after each crash. Well, it turned out that NTFS conversion is stupid, as Windows' partitioning utility uses 512 KB clusters... ouch. So now booting and the entire computer runs a little slower because of the overhead (NTFS should use 4KB clusters, IIRC, to be fast).
2. I don't use Mac a lot, so I am unfamiliar with it. However, I believe I installed everything correctly.
3. I was TRYING to avoid temporarily buying both Leopard and VMware. But now that I see that VMware doesn't detect my working boot camp, am I forced to upgrade the OS first?

computer:~ yourname$ sudo fdisk /dev/rdisk0
Password:
Disk: /dev/rdisk0 geometry: 19457/255/63 312581808 sectors
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec start - size

1: EE 0 0 2 - 25 127 14 1 - 409639 <Unknown ID>
2: AF 25 127 15 - 1023 223 5 409640 - 245366784 HFS+
*3: 07 1023 49 7 - 1023 80 23 246038568 - 66543200 HPFS/QNX/AUX
4: 00 0 0 0 - 0 0 0 0 - 0 unused

http://www.informit.com/articles/article.aspx?p=376123&rl=1 says that this "HPFS/QNX/AUX" type 7 is really NTFS. Not sure why Darwin is using such old code, probably from the early 90s before NTFS was around, I guess.

$ sudo gpt -r show disk0
gpt show: /dev/disk0: Suspicious MBR at sector 0
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 245366784 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
245776424 262144
246038568 66543200 3 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
312581768 7
312581775 32 Sec GPT table
312581807 1 Sec GPT header{bq}

*****************
$ sudo diskutil list
Password:
/dev/disk0
#: type name size identifier
0: GUID_partition_scheme *149.1 GB disk0
1: EFI 200.0 MB disk0s1
2: Apple_HFS Billy's MacBook 160 117.0 GB disk0s2
3: Microsoft Basic Data 31.7 GB disk0s3
/dev/disk1
#: type name size identifier
0: FDisk_partition_scheme *93.2 GB disk1
1: Windows_NTFS USB100 93.2 GB disk1s1
/dev/disk2
#: type name size identifier
0: Apple_partition_scheme *178.1 MB disk2
1: Apple_partition_map 31.5 KB disk2s1
2: Apple_HFS VMware Fusion 178.1 MB disk2s2{bq}

Re: Fusion 1.1 DOESN'T SEE my BOOT CAMP partition

1. Nov 26, 2007 5:24 AM in response to: uruiamme
Click to view rcardona2k's profile Champion 5,211 posts since
Oct 20, 2005
I have tes Mac running OS X 10.4.11 and I can still see my Boot Camp partition in Startup Disk, I can also select Windows at startup.

Have you tried to hold down the option key at startup to boot into Windows? If Windows is not booting try using the Windows install CD to repair the installation before attempting to run it under Fusion. Also you can try temporarily disconnecting your USB drives so Fusion only sees your MacBook Pro's internal drive, this temporary step might aid the initial Boot Camp partition detection.

Re: Fusion 1.1 DOESN'T SEE my BOOT CAMP partition

2. Nov 26, 2007 9:25 AM in response to: rcardona2k
Click to view BP9906's profile Expert 364 posts since
Jun 15, 2007
Fusion should create a VMDK that maps to your XP Partition.

You could always force it by using vmware-vdiskcreator. Its a command line utility (although Eric made a nice GUI for it - search forum). Even better would be to use that utility to see if it sees your bootcamp partition correctly. There's a command line option to check that. The utility is in /Library/Application Support/VMware/Fusion ...

Re: Fusion 1.1 DOESN'T SEE my BOOT CAMP partition

3. Nov 26, 2007 10:20 AM in response to: uruiamme
Click to view MandarMS's profile Master 731 posts since
Nov 12, 2007
Before proceeding with the steps suggested below, please backup all critical data which is there on your Mac system.

1. Quit all applications in Host Mac OS X
2. Open Terminal utility from Macintosh HD  Applications  Utilities folder.
3. Key-in the following command

$ sudo fdisk /dev/rdisk0

4. Preferably take the screenshot of the output or Note down the output (for restoring MBR).
5. Key-in the following command

$ sudo fdisk -e /dev/rdisk0
setpid 3
Choose 07 (as the partition type)
write
Y

Restart your Mac System

For more details please check the example shown below:

$ sudo fdisk -e /dev/rdisk0 (this will help to change the MBR)

$ fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory
Enter 'help' for information
fdisk: 1> setpid 3 (Enter “setpid 3” press enter key)

Starting Ending
#: id cyl hd sec - cyl hd sec start - size
*3: 0B 1023 254 63 - 1023 254 63 1127792680 - 337356448 Win95 FAT32L
Partition id ('0' to disable) 0 - FF: [C] (? for help) 07 (Enter 07 Partition table)
fdisk:*1> write (enter “write” press enter key, This will change the MBR)

Device could not be accessed exclusively.
A reboot will be needed for changes to take effect. OK? [n] Y (Press Y to modify changes)

Writing MBR at offset 0.
$ fdisk: 1> exit (enter “exit”, press enter key)

6. Restart your Mac System

Re: Fusion 1.1 DOESN'T SEE my BOOT CAMP partition

4. Nov 26, 2007 10:28 AM in response to: MandarMS
Click to view BP9906's profile Expert 364 posts since
Jun 15, 2007
From Mandar's response, seems like OSX still remembers your partition as Fat32 not NTFS, since you changed it to NTFS on the Windows side. Apparently Mandar's steps will straighten that out and hopefully Fusion will auto detect correctly.

Re: Next steps

8. Nov 29, 2007 3:44 AM in response to: uruiamme
Click to view rcardona2k's profile Champion 5,211 posts since
Oct 20, 2005
I'm not sure who you're referring to as MandarMS is a VMware employee. You are quite close to reproducing a VM similar to what VMware produces for the Boot Camp partition. I have tried these steps on my machine, so I know they work, with the caveat that my Boot Camp partition has already been prepared by VMware and it has the Tools installed. You're welcome to try it.

1. Go through the New Machine Wizard and make a new Windows XP VM named "BC". Accept the default to create a virtual disk-- this is a placeholder we will replace later. it will not take up much space (i.e. not 20GB). Please be careful to UNcheck "Windows Easy Install" and UNcheck "Start virtual machine and install operating system now" - we obviously won't be doing these.

2. Once you have this "Boot Camp" machine defined, open Terminal and cd to Documents/Virtual Machines/BC.vmwarevm

3. Delete the placeholder virtual disk you created in Step 1, rm BC.vmdk

4. Create a raw disk pointing to your Boot Camp partition, which from your output above is exactly: "/Library/Application Support/VMware Fusion/vmware-rawDiskCreator" create /dev/disk0 3 BC ide
(NOTE: The name is important to match what's in the .vmx file, which is BC.vmdk - the command above creates a replacement name for the file you deleted in Step 3)

5. Start the Virtual Machine. You will be asked to provide your system password to gain read/write access to the Boot Camp partition.

When you get this working, you will want to open the BC bundle and add these two lines to your BC.vmx file (otherwise you can damage your Boot Camp partition):

snapshot.disabled = "TRUE"
suspend.disabled = "TRUE"

Good luck

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities