Mount Win10 raw "partition" in Linux VM

[imWACC0]

I need to dual boot my system SSD, of Lubuntu and Win10. But I want to run the install of Win10(sda1) in the VM of Lubuntu(sda2).

I find some stuff for whole disk, but not for partition:

Code: Select all

sudo VBoxManage internalcommands createrawvmdk -filename "</path/to/file>.vmdk" -rawdisk /dev/yourWindowsDisk(e.g sdb)

I found something, but I don't know how to translate it:

Code: Select all

VBoxManage internalcommands createrawvmdk -filename /path/to/file.vmdk -rawdisk /dev/sda -partitions 1,5

This example would create the image /path/to/file.vmdk (which, again, must be absolute), and partitions 1 and 5 of /dev/sda would be made accessible to the guest.

How do I say sda1 instead of "1,5"? Do I just say "-partitions 1"?

I have my Program File as a (NTFS) Junction Link to sdc1, do I need to make a VM disk/partition for that also? If so, how?
Also, my page file is on sdb1.... Dose that matter?

[socratis]

See ch. 9.9.1 Using a raw host hard disk from a guest of the User Manual. See sub-chapter 9.9.1.2...

And you'd better backup the backup of your backup...

[imWACC0]

Thank you for your time. I've read some Ch 9.9.1 I guess I need to read more, and get help with some of the concepts.

I'm good with most versions of Winblows, but only so-so with Linux. I think I can get the Win10 mount, but 9.9.1.2 was talking about MBR and bootloaders... Don't I just need to follow the instructions for adding Lubuntu as the second of a dual boot?

Can I get a hint about adding the other two drives? Do I need to? Is the command:

Code: Select all

VBoxManage internalcommands createrawvmdk -filename /path/to/file.vmdk -rawdisk /dev/sdc -partitions 1

or were you talking about:

Code: Select all

VBoxManage internalcommands createrawvmdk -filename /path/to/file.vmdk -rawdisk /dev/sdc -partitions 1 -relative

P.S. Yes, .img file on second system, off site and on sdd1

[socratis]

My experience with raw disks has been limited to complete disk access, not partitions. Due to the inherent danger of data loss, I'm not going to risk giving you the wrong advice on this one...