VMware Communities
CWasko
Contributor
Contributor

Boot Camp not recognized

I've got a Mac Mini with three partitions. Two Mac partitions and one windows partition. Fusion does not recognize that there is a windows partition. Apple's Startup Disk control panel sees it just fine, and I can boot to it no problems. Also, Parallels sees the windows partition and can utilize it as well.

What do I need to do to get Fusion to recognize it?

Reply
0 Kudos
37 Replies
Pat_Lee
Virtuoso
Virtuoso

With beta 3, only the default setup will auto detect and offer the Boot Camp option. We are working on improving this algorithm in a future release.

Thanks for the information, it will help us make VMware Fusion even better.

Best,

Pat Lee

Senior Product Manager - Mac Products

VMware

Reply
0 Kudos
samkane
Contributor
Contributor

OK, I've got nothing fancy going at all and VMWare still won't start the Bootcamp winXP partition!

Disk: /dev/rdisk0 geometry: 14593/255/63 \[234441648 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec \[ start - size]

\----


1: EE 0 0 2 - 25 127 14 \[ 1 - 409639]

2: AF 25 127 15 - 1023 53 3 \[ 409640 - 211812352] HFS+

*3: 0C 1023 134 5 - 1023 80 23 \[ 212484136 - 21957472] Win95 FAT32L

4: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

Only thing worth mentioning might be that Bootcamp was already installed before i upgraded to Beta 3!

I'm running:

VMWare Version 1.0b3 (43733)

on a:

Apple MacBook (2 Ghz Core Duo, 1GB 667 Mhz DDR2 SDRAM)

Mac OSX 10.4.9

I get the following error in "Console" when trying to boot my Bootcamp(Win XP) partition:

Unable to create the source raw disk: Resource busy (1048585).

Raw disk creation failed.

I tried this launch under both the regular User account as well root but no joy!

PS- VMWare also seems to be realting the following error when runningh other functional virtual machines:

Failed to acquire super user privileges.

Thanks, hope this helps and u fix it soon!

Reply
0 Kudos
wdeboer
Contributor
Contributor

I want a 250-500GB harddisk in my MBP!! Probably buying a MacBook for this would be cheaper, though Smiley Wink

Reply
0 Kudos
EMR
Enthusiast
Enthusiast

Pat and the rest of the Fusion development team,

Please, consider MBR-partitioned hard disks, even with multiple partitions (NTFS/FAT32) as candidates for Boot Camp detection.

Thank you.

Reply
0 Kudos
Pat_Lee
Virtuoso
Virtuoso

The development team is looking into the Boot Camp issues people are reporting. In the cases where we can provide a quick workaround like a Windows registry key to avoid bluescreens, we will post them when we have them.

With regards to detecting Boot Camp partitions and various issues, we are looking into those further and they will have to wait until we release new software for which I cannot discuss any dates at this time.

Thanks for all the information and your patience, we will work to improve our Boot Camp support soon.

Best,

Pat Lee

Senior Product Manager - Mac Products

VMware

Reply
0 Kudos
999
Contributor
Contributor

Not recognised on my iMac either, I used Winclone (http://www.twocanoes.com/winclone/) to create the partition and to install windows from a backup of a previous bootcamp partition. Parallels can boot from the partition no problem and so can my computer.

Disk: /dev/rdisk0 geometry: 30401/255/63 \[488397168 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec \[ start - size]

\----


1: EE 1023 254 63 - 1023 254 63 \[ 1 - 409639]

2: AF 1023 254 63 - 1023 254 63 \[ 409640 - 461091512] HFS+

*3: 0B 1023 254 63 - 1023 254 63 \[ 461763296 - 26633832] Win95 FAT-32

4: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

Reply
0 Kudos
CarlosMS
Contributor
Contributor

Hello, similar to other users on this thread, beta 3 of Fusion is unable to recognize my Boot Camp setup. Boot Camp is installed in its own, separate drive fully formatted with a single NTFS partition out of a total of 3 internal SATA drives in a quad-Mac Pro rig. Running MacOS 10.4.9 + all available OS patches to date + Boot Camp 1.2 beta.

If possible/practical, it may be beneficial if beta 3 of Fusion could be re-built with the tweaks to the BC recognition algorithm if the post-beta 3 release is unknown because this issue hinders some of us from providing additional feedback on Fusion. Smiley Sad

-


8< cut here \----


diskutil list

/dev/disk0

#: type name size identifier

0: GUID_partition_scheme *465.8 GB disk0

1: EFI 200.0 MB disk0s1

2: Apple_HFS Mac Data HD 2 465.4 GB disk0s2

/dev/disk1

#: type name size identifier

0: GUID_partition_scheme *232.9 GB disk1

1: EFI 200.0 MB disk1s1

2: Microsoft Basic Data Win Boot HD 3 232.7 GB disk1s2

/dev/disk2

#: type name size identifier

0: GUID_partition_scheme *465.8 GB disk2

1: EFI 200.0 MB disk2s1

2: Apple_HFS Mac Boot HD 1 465.4 GB disk2s2

Reply
0 Kudos
udecker
Contributor
Contributor

Having similar problems where my Boot Camp partition is not being recognized:

diskutil list

/dev/disk0

#: type name size identifier

0: GUID_partition_scheme *149.1 GB disk0

1: EFI 200.0 MB disk0s1

2: Apple_HFS Poet 60.0 GB disk0s2

3: Microsoft Basic Data RED 15.0 GB disk0s3

4: Apple_HFS udecker 59.9 GB disk0s4

5: Apple_HFS Prose 13.6 GB disk0s5

fdisk /dev/rdisk0

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]

2: AF 25 127 15 - 1023 254 53 \[ 409640 - 125829120] HFS+

*3: 0C 1023 80 55 - 1023 112 48 \[ 126500904 - 31457280] Win95 FAT32L

4: AF 1023 112 49 - 1023 159 23 \[ 157958184 - 125566976] HFS+

Reply
0 Kudos
tba03_m4m
Contributor
Contributor

same issue here, 3 partition ( 1commen FAT32, 1 xp, 1 osx, manually aprtitioned in terminal)

With parallels I had to esdit a config file but I can't find one for Fusion

MacBookPro 2,16 2 GB, OsX10.4.9, Fusion Beta3

Reply
0 Kudos
mail64565465
Contributor
Contributor

Beta 4 not recognized on my macpro system.. it is on partition 3 disk0

tests-computer:~ $ sudo fdisk /dev/rdisk0

Disk: /dev/rdisk0 geometry: 38913/255/63 \[625142448 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec \[ start - size]

\----


1: EE 1023 254 63 - 1023 254 63 \[ 1 - 409639]

2: AF 1023 254 63 - 1023 254 63 \[ 409640 - 413138944] HFS+

*3: 0B 1023 254 63 - 1023 254 63 \[ 413810728 - 211331680] Win95 FAT-32

4: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

tests-computer:~ $ sudo fdisk /dev/rdisk1

Disk: /dev/rdisk1 geometry: 60801/255/63 \[976773168 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec \[ start - size]

\----


1: EE 1023 254 63 - 1023 254 63 \[ 1 - 976773160]

2: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

3: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

4: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

tests-computer:~ $ sudo fdisk /dev/rdisk2

Disk: /dev/rdisk2 geometry: 38913/255/63 \[625142448 sectors]

\^[[A^[Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec \[ start - size]

\----


1: EE 1023 255 63 - 1023 255 63 \[ 1 - 625142447]

2: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

3: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

4: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

tests-computer:~ $ sudo fdisk /dev/rdisk3

Disk: /dev/rdisk3 geometry: 48641/255/63 \[781422768 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec \[ start - size]

\----


1: EE 1023 255 63 - 1023 255 63 \[ 1 - 781422767]

2: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

3: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

4: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

tests-computer:~ $

tests-computer:~ $

tests-computer:~ $ diskutil list

/dev/disk0

#: type name size identifier

0: GUID_partition_scheme *298.1 GB disk0

1: EFI 200.0 MB disk0s1

2: Apple_HFS Scratch_200 197.0 GB disk0s2

3: Microsoft Basic Data BootCamp 100.8 GB disk0s3

/dev/disk1

#: type name size identifier

0: GUID_partition_scheme *465.8 GB disk1

1: EFI 200.0 MB disk1s1

2: Apple_HFS OSX 150.6 GB disk1s2

3: Apple_HFS MP3 200.6 GB disk1s3

4: Apple_HFS scratch 114.0 GB disk1s4

/dev/disk2

#: type name size identifier

0: GUID_partition_scheme *298.1 GB disk2

1: EFI 200.0 MB disk2s1

2: Apple_HFS AppleTV 50.0 GB disk2s2

3: Apple_HFS Video 247.6 GB disk2s3

/dev/disk3

#: type name size identifier

0: GUID_partition_scheme *372.6 GB disk3

1: EFI 200.0 MB disk3s1

2: Apple_HFS OSX_Backup 150.0 GB disk3s2

3: Apple_HFS Downloads 200.0 GB disk3s3

4: Apple_HFS OSX_Setup 22.0 GB disk3s4

/dev/disk4

#: type name size identifier

0: Apple_partition_scheme *171.4 MB disk4

1: Apple_partition_map 31.5 KB disk4s1

2: Apple_HFS VMware Fusion 171.4 MB disk4s2

/dev/disk5

#: type name size identifier

0: FDisk_partition_scheme *967.5 MB disk5

1: DOS_FAT_16 USB DISK 967.2 MB disk5s1

/dev/disk6

#: type name size identifier

0: FDisk_partition_scheme *232.9 GB disk6

1: Apple_HFS MAC 232.9 GB disk6s1

tests-computer:~ $

Reply
0 Kudos
mail64565465
Contributor
Contributor

I'd like to try to figure out how to manually get my bootcamp partiion to get read, which is not being auto-detected. I can then post my results.

~/Library/Application Support/VMware Fusion/Virtual Machines/Boot Camp

Can anyone upload or zip the files from the following path and e-mail them to coreduo0099@yahoo.com ?

Thanks

Reply
0 Kudos
etchak
Contributor
Contributor

I'm also have problems with the boot camp partition

Paralles was also not working...after rename of the driver.cab file to sp2.cab was the problem solved.

Disk: /dev/rdisk0 geometry: 30401/255/63 \[488397168 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec \[ start - size]

\----


1: EE 0 0 2 - 25 127 14 \[ 1 - 409639]

2: AF 25 127 15 - 1023 95 47 \[ 409640 - 421527552] HFS+

*3: 07 1023 176 49 - 1023 80 23 \[ 422199336 - 66197792] HPFS/QNX/AUX

4: 00 0 0 0 - 0 0 0 \[ 0 - 0] unused

Reply
0 Kudos
lmbebo
Contributor
Contributor

Hello

I saw this and noticed a similar problem.

I am running a mac mini core solo with boot camp version 1.3 on a single sata 60g hard drive. I just recently reinstalled both osx and windows. Prior to this I was running 10.4.9 with bootcamp 1.2 and Fusion b3. But with the reinstall and the updated bootcamp drivers and the fusion beta I am unable to boot off of my boot camp partition.

Other issue I'll throw out is that I unable to use any usb connected device within vmware. Windows will recognize it as a flash drive or something, but is unable to make it work.

Reply
0 Kudos
admin
Immortal
Immortal

with the reinstall and the updated bootcamp drivers and the fusion beta I am unable to boot off of my boot camp partition

What happens if you try? Is the partition not bootable period? Does it blue screen? Something else?

Other issue I'll throw out is that I unable to use any usb connected device within vmware. Windows will recognize it as a flash drive or something, but is unable to make it work.

What version and patch level of Windows?

Reply
0 Kudos
lmbebo
Contributor
Contributor

it does not show up on my list of virtual machines. Its not given as an option.

The machine has automatic updates, so when they're available, I install it.

its windows xp professional sp2

Reply
0 Kudos
admin
Immortal
Immortal

So Beta 3 recognized your old BootCamp install, but you reinstalled both OS X and Windows, and Beta 4 isn't recognizing your new BootCamp install? Can you think of any differences between the way you set up the BC partition?

You should probably file a bug with the output of 'sudo fdisk /dev/rdisk0'.

Reply
0 Kudos
lmbebo
Contributor
Contributor

The only thing I did differently was make the partition bigger than the previous one.

I also did this when reinstalling. 1 reinstalled windows on the BC partition then, then used driveimage XML to restore my previous install.

For osx, I restored some files via iBackup. But I've tried to locate any previous vmware file to delete them (as shown in other posts). I have not found any files to delete. I know in my old install I had files in ~/Library/Application Support/Vmware directory. There is nothing there.

I created a new account and only really copied over my Mailbox.

Disk: /dev/rdisk0 geometry: 7296/255/63 \[117210240 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec \[ start - size]

\----


1: EE 0 0 2 - 25 127 14 \[ 1 - 409639]

2: AF 25 127 15 - 1023 63 35 \[ 409640 - 88080384] HFS+

*3: 0B 1023 144 37 - 1023 254 23 \[ 88752168 - 28458032] Win95 FAT-32

4: 00 0 0 0 - 0 0 0 \[ 0 - 0] unus

Message was edited by:

lmbebo

Reply
0 Kudos
admin
Immortal
Immortal

Sorry for the delay in replying, I finally got around to looking up what partition types we want. If it's NTFS, we check for 07, if it's FAT we check for 0C. See incognegro[/url]'s post in this thread[/url] for details about how to change it.

Reply
0 Kudos