Last time I wiped my machine I decided to install Windows first, as this allowed me to ensure it installed on a "pure" GPT disk with full UEFI support, rather than hybrid MBR/GPT scheme that the Bootcamp Assistant creates. This has a few advantages when booting directly into Windows.
Anyway, I'm historically a VMWare Fusion user, and this recognises my "proper" dual-boot setup and runs it just fine. However, Parallels only seems to recognise Windows partitions setup by the Bootcamp Assistant itself.
Is there any workaround to this? For example, for VirtualBox I can create a raw-disk .vmdk including my EFI partition and the Windows-specific partitions of my disk*.
To give you a better idea, here's my disk layout, it includes partitions for Mac OS itself and a separate one for users (to make wiping OS X easier if I need to do it) plus the partitions that Windows created and a shared ExFAT partition for games (this lets me play the same copy of a game under both Windows and WINE):
Code:
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk0
1: EFI EFI 209.7 MB disk0s1
2: Microsoft Reserved 134.2 MB disk0s2
3: Microsoft Basic Data 149.3 GB disk0s3
4: Windows Recovery 471.9 MB disk0s4
5: Apple_HFS Mac OS 200.0 GB disk0s5
6: Apple_Boot Recovery HD 650.0 MB disk0s6
7: Apple_CoreStorage Users 400.0 GB disk0s7
8: Apple_Boot Boot OS X 134.2 MB disk0s8
9: Microsoft Basic Data Games 249.2 GB disk0s9
*I should clarify that while I can create the disks for VirtualBox, its inability to ask for root access when opening them means they currently can't be used with SIP enabled (as this prevents changing permissions on /dev/disk0), in short, it's also a no-go when loading my Windows partition.
