March 31, 20215 yr hello on 6.9 jst go to tools ----> system devices ---> stub your NVME here and add in the VM onfigurator at primary VDISK Manual /dev/nvme***** what ever your nvmes name is <---- seeable with unassined devices.
April 7, 20215 yr Author @domrockt, Sorry missed your reply earlier. Not yet familiar how stubbing goes. I see the following on my system devices page- Do I just tick on IOMMU group 43, and click on "BIND SELECTED TO VFIO AT BOOT?" Will this achieve my goal to pass through NVME to VM directly? Anything I should be checking in syslinux.cfg? What exactly does stubbing do? EDIT: After doing above, I can now see in my VM page: shall I tick this? Furthermore, changing Primary Vdisk location to /dev/nvme0n1/vdisk1.img and saving leaves it in updating, but nothing is being saved. Lastly, the nvme disk is no longer in my unassigned disks, and it says it's missing. Edited April 7, 20215 yr by jang430 added info
August 18, 20223 yr Hi @jang430did you ever figure this out? I'm in the same boat as you. I'd like to install Windows 11 directly on my NVME but I'm a bit lost. Would love if you could update us on your results.
August 30, 20223 yr @venicenerdgo to tools > system devices > select your nvme and click on "Bind selected to vfio at boot". Restart your server. then go to VM, create VM select primary device "NONE" and add your NVME at the botton by "Other PCI Devices". That's it.
March 24, 20233 yr This thread helped me to set up a Server 2019 that was still on the former boot nvme drive of the unraid box. Worked nicely, thank you. Amazing what software can do these days.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.