Hallo everybody. As the title suggests, I'm trying to boot my already installed Windows 10, occupying a single SSD, using it as a drive in a Unraid VM.

I'm trying to follow those instructions, very useful so far:

 

On this menu, however, I have a couple of settings that in the video are missing:

 

Of course, they scares me out of my pants! What I should choose? In the primary Vdisk Size MAYBE I could put the actual size of my SSD (as in the picture I did), but I don't know what that Type means (raw/qcow2).

I don't want to go on, 'cause I'm scared of Unraid erase the SSD when I create the VM.

Can you help me with those settings?

Thanks in advance, and have a great new year!

 

Edited January 1, 20224 yr by Andrea P.
Changed the title to Solved

18 minutes ago, Andrea P. said:

On this menu, however, I have a couple of settings that in the video are missing:

Just not fill that fields.

Leave the vdisk size blank.

vDisk is a virtual disk (a file), that it could be created in the path of primary vdisk location; in this case you are not going to use any vdisk, so fill only the path of primary vdisk location, set it to manual and point the path to the id of the real disk.

 

After you complete the settings, you can double check that the xml is saved correctly, switch to advanced xml view and check the disk block, it should look something like this:

    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/YOURDISKID'/>
      <target dev='hda' bus='virtio'/>
    </disk>

 

If you don't add any other disk, check that there are no other disk blocks apart that.

By doing this you are going to attach a real disk to a virtual controller, in the example above, a virtio controller; if you want you can change that value according to your needs, for example you may want to change it to sata:

      <target dev='hda' bus='sata'/>

 

Edited January 1, 20224 yr by ghost82

I noticed you have a '@' in your by-id path: are you sure the path is correct?

You need to delete the '@'

Edited January 1, 20224 yr by ghost82

17 minutes ago, ghost82 said:

You need to delete the '@'

Yeah, I inadvertently copypasted from the bash terminal, along with the disk ID. 

Also, when I removed that @, Unraid removed those two options I was baffled with. However, it was interesting to know what are used for.

PS: incidentally, I can't boot the VM. I'll try to understand if the problem is the type of Bios, or maybe the Vdisk Bus choice.

Also, it's weird the Capacity / Allocation shown in the VM summary screen:

That's a 480GB SSD, indeed.

 

Edited January 1, 20224 yr by Andrea P.

For an existing installation use 'sata' as the virtual controller, it's easier, since virtio drivers aren't included in windows and you need to inject them; sata drivers are already included.

Check the partitions on your disk or boot an uefi shell from ovmf bios and map the partitions to understand if your windows installation is legacy or uefi.

On 1/1/2022 at 6:12 AM, ghost82 said:

Just not fill that fields.

Leave the vdisk size blank.

vDisk is a virtual disk (a file), that it could be created in the path of primary vdisk location; in this case you are not going to use any vdisk, so fill only the path of primary vdisk location, set it to manual and point the path to the id of the real disk.

 

After you complete the settings, you can double check that the xml is saved correctly, switch to advanced xml view and check the disk block, it should look something like this:

    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source dev='/dev/disk/by-id/YOURDISKID'/>
      <target dev='hda' bus='virtio'/>
    </disk>

 

If you don't add any other disk, check that there are no other disk blocks apart that.

By doing this you are going to attach a real disk to a virtual controller, in the example above, a virtio controller; if you want you can change that value according to your needs, for example you may want to change it to sata:

      <target dev='hda' bus='sata'/>

 

This worked great for me. One caveat, is I did have to boot a freshly cloned drive on a bare metal PC one time before it would boot in Unraid as a VM. So if you are getting 'BOOT DEVICE INACESSIBLE" blue screen. Try booting the guest VM on bare metal one time first