The question I have: I want to find out if there is a updated method (video) of passing a already running win10 nvme to a newly created unraid vm.

And I am using the Kernel helper docker (ich777) that recompiles the kernel to include the reset patch for amd gpu - which works awesomely well.
 

Unraid setup I want to run - Unraid with Gaming VM (gpu & nvme pass through as bare metal) + VMs to play with for fun and some work poc's

and....able to boot from nvme win10 directly if chosen in boot selection of bios.

 

The config I have is as follow:

Unraid 6.9.0 rc2

Cache drive - 1 x 2TB nvme - appdata, domains, system etc

Array drives - 2 x 1TB mech drives - odds and stuff I dont need speed for

Unassigned drive - 1 x 2TB nvme that holds gaming win10 native boot partition

GPU - AMD RX5700XT OC - for gaming VM pass through

CPU - AMD AM4 Ryzen 7 3700x

Mobo - Gigabyte Aorus x570 Ultra

 

All other VMs will be RDP/SSH to from laptop.

 

Unraid Flash config (adv view)

Inside the Unraid OS section

append initrd=/bzroot video=efifb:off

 

Win10 Gaming VM xml config (example of one of the pci items passed to show in Other PCI Devices)

    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x08' slot='0x00' function='0x3'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x0b' slot='0x00' function='0x0'/>
    </hostdev>

VM Machine: Q35-5.1

Bios: OVMF

 

I have looked at loads of Videos regarding the subject - just want to know if there is a updated method out or is this the guide to follow.

 

 

That guide is still relevant outside of not needing the VFIO-PCI config plug-in to stub your NVMe controller. This functionality is built into 6.9 rc2 under Tools => System Devices.

Ok followed the guide....It did not work. And after investigating I see that Win10 was installed Legacy mode. (facepalm) 

I am wondering how this would have happened as I had this working beginning of 2020. Did a reinstall of windows about 2months ago.

Not sure why it would have changed to Legacy as I never changed the BIOS.

I am going to try converting Legacy to UEFI by following this https://www.maketecheasier.com/convert-legacy-bios-uefi-windows10/

Otherwise reinstall..... (double facepalm)

If Windiws install in legacy, then use SEABIOS in VM should be fine.

Not if you do nvme pass through according to SI1 guide. I did the upgrade to gpt with mbr2gpt and all successful.
NVME boots now hardware passed to vm and baremetal.