I think I've figured some stuff out regarding this.
Before I continue, I'll state some relevant configuration. Only ONE disk in my system right now, MBR partitioned into 2 partitions, OS X and Windows XP. The OS X partition is the first on the disk, the XP one second. Both are obviously primary partitions.
The latest version of Parallels has always let me select the boot camp option (build 3170 and now 3186), but when trying to boot it would give me the "Unable to open disk image Boot Camp" error message.
I tried to specify the partition using the instructions here:
http://forums.parallels.com/showthread.php...ustom+boot+campNo dice, still wouldn't boot.
I then tried to see whether I could use my Windows partition as a secondary partition while booting from my normal image file. Parallels didn't fuss at all, and it showed up as the F drive.
That was kinda weird, what could possibly be different. Parallels was able to use the partition as a secondary one in the virtual machine, and the only difference between that and using it as the main boot partition was the ability to actually boot it. This made me think .. Parallels basically connects to the entire disk, not just the partition. Of course the stupid thing wouldn't boot right, the OS X partition is the active partition, not the Windows one!
So I used fdisk in OS X (the OS X one), to manually make the Windows partition active while OS X was running. Ding ding! Parallels didn't give the error anymore, and started booting from the Windows "boot camp" partition!
Now mind you, I got a BSOD shortly after this, but this seemed like an issue that happened on regular Macs too depending on your method of Windows installation, etc: See here, 4th post down:
http://forums.parallels.com/showthread.php...ghlight=mup.sysJust right now I booted the XP CD in Parallels with the "boot camp" partition enabled, and repaired the installation. It rebooted and I'm running the 2nd part of the repair right now in Parallels booted off the "boot camp" partition! Lets see if we can make it to the end of the repair and still have it booting!
Anyways, on to the technical details of how I did this:
My MBR is a standard MBR, no special bootloaders installed. I could not get this to work with SmartBootManager installed no matter what.
1. Make sure the Windows/"Boot Camp" partition is unmounted at all times when you go to use Parallels. Since I don't use that partition in the Finder/OS X anyways, I just set OS X to not automount it on boot anyways. Instructions how to do that here:
http://forums.macosxhints.com/showthread.php?p=3536152. Start Terminal. Either su, or sudo fdisk -e /dev/rdisk0 <--- Depending on your actual disk with Windows partition. I'd imagine that this "active partition" issue only applies to those with a single disk with both OS X and Windows.
Once in fdisk, type in "print", minus the quotes. See which one is your Windows partition.
Next you want to do "flag x" .. "x" being the number of your Windows partition. For instance, my Windows partition is 2, so I'd type "flag 2". Type in "write", then "quit".
3. Make sure your Parallels .pvs file is set to use bootcamp and specify the Windows partition /dev/ entry. Eg. Disk 0:0 image = Boot Camp;disk0s2. See this thread here for how to do this:
http://forums.parallels.com/showthread.php...ustom+boot+camp4. Again, make sure your Windows disk is unmounted from Finder. Start parallels. If you're lucky, Windows will boot up!
5. Don't forget to set your OS X partition as active again before you reboot your computer, or else you'll be booting into Windows. I'm sure there is a way that we can automate/script the fdisk stuff I did above so that it will set the Windows partition as active after OSX is booted up, and then set the OS X partition back as active when you go to shut down/restart.
I'll check in again after my "repair" is done!
It's working!!!!!!!!