I wanted my (NTFS) data disk to be accessible from my boot camp Parallels VM. Parallels provides no support for this, so I tried it myself.
I duplicated the disk file that Parallels created and started poking around, and after half an hour or so, had success. This is what you need to do.
My boot camp disk is at /dev/disk0. My data disk is at /dev/disk1.
You'll need to start by changing DiskDescriptor.xml.
My original Boot Camp `DiskDescriptor.xml`
``` 976773168 969021 512 512 16 63 0 {00000000-0000-0000-0000-000000000000} {631365f5-35af-43ae-a911-aeddf03d7444} Samsung SSD 970 EVO 500GB Media (disk0).hdd level2 1 0 0 0 0 0 0 0 0 1 2048sudo dd if=/dev/disk1 bs=512 count=1 of=./PhysicalMbr.hds
sudo dd if=/dev/disk1 bs=512 count=33 skip=1 of=./PhysicalGpt.hds
sudo dd if=/dev/disk1 bs=512 count=33 skip=976773135 of=./PhysicalGptCopy.hds
To determine gpt copy offset:
sudo gpt -r show /dev/disk1
Sample output for this case:
$ sudo gpt -r show /dev/disk1
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 32 Pri GPT table
34 32734 1 GPT part - E3C9E316-0B5C-4DB8-817D-F92DF00215AE
32768 976738304 2 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
976771072 2063
976773135 32 Sec GPT table
976773167 1 Sec GPT header
Hello! This really works, thank you very much! As for me, i needed this knowledge to connect to the Bootcamp OS my third hard disk with НFS+ partition as physical disk and it worked using your guide and after doing a couple of days of testing. Now, my guest Windows 7 can see and do read-write to connected HFS+ with very fast Paragon HFS+ windows driver inside it. I will post some key info here, maybe someone with my case will find it usefull.
Firstly of all, this is my setup from
diskutil listlisting to be at least understandable:/dev/disk0 (internal, physical):#: TYPE NAME SIZE IDENTIFIER0: GUID_partition_scheme *240.1 GB disk01: EFI EFI 209.7 MB disk0s12: Apple_HFS MacOSX 239.2 GB disk0s23: Apple_Boot Recovery HD 650.0 MB disk0s3/dev/disk1 (internal, physical):#: TYPE NAME SIZE IDENTIFIER0: GUID_partition_scheme *499.3 GB disk11: EFI EFI 209.7 MB disk1s12: Apple_HFS DATA 498.9 GB disk1s2/dev/disk2 (internal, physical):#: TYPE NAME SIZE IDENTIFIER0: FDisk_partition_scheme *120.0 GB disk21: Windows_NTFS 120.0 GB disk2s1disk0is my macOS main SSD,disk2is second SSD with so called "Bootcamp" with Windows7.disk1is my usual HDD storage, partitioned as GUID to be available to get thatDisk / Partition UUID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXXas the target for desired partition/dev/disk1s2.Using all that your tricks Obbut, i was able to get physical access to
/dev/disk1s2, but Parallels Desktop 14 immediately after starting wrote an error with something like "Cannot load from Bootcamp cause /dev/disk1s2 is unsupported type". So, after few days of investigation i found a problem in mainconfig.pvsfile. In the config's section for my second HDD for guestOS there was property<EmulatedType>3</EmulatedType>. As understood 3 goes for NTFS or FAT32 file systems. After changing in to 2, Parallels was finally able to start normally and Paragon HFS+ in guestOS could successfully mount that partition. Now, when i go into guestOS, my/dev/disk1s2automatically unmounts, and when i quit Windows, it mounts back for macOS. Also i've changed<Connected>from 1 to 0 and<AutoCompressEnabled>from 1 to 0. And it is better to remove write access fromconfig.pvs, cause sometimes Parallels fully rewrites it with kind of wrong information. I have Parallels Desktop Version 14.1.2 (45479).