January 4, 20251 yr I'm using GPU Passthrough, so I have a separate monitor keyboard and mouse. I've used Primary vDisk Type: Raw or Qcow2, with same results. I've tried Primary vDisk Bus: VirtIO and SATA, still the same. When it hangs, even Unraid webUI hangs, and needs to be hard reset. After booting up, I go to edit config of vm, putting all settings back to when I started the vm, upon starting the VM, it seems there was totally no installation of Windows done. Any ideas?
January 5, 20251 yr Author I'm wondering if it's because I refer to the nvme I'm installing Windows 10 to as /dev1/vdisk1.img? Does it have to be anything like /dev1/nvme1on1/vdisk...?
January 5, 20251 yr 8 hours ago, jang430 said: /dev1/vdisk1.img? Where do you see this, it should either be a mount point if using a vdisk, or the device if being passed through.
January 5, 20251 yr Author The device is being passed through. What's the proper way to call it? If it's passed through, it doesn't require mounting right? Edited January 5, 20251 yr by jang430
January 5, 20251 yr That's the historical devices view from the UD plugin and irrelevant to the VM settings, post a screenshot from the VM form page.
January 6, 20251 yr Author <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10</name> <uuid>6c267a1e-2b6a-7533-bc5e-94e5b2bf1736</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='8'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='10'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-7.2'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='2' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/dev1/nvme1n1/vdisk1.qcow2'/> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows.iso'/> <target dev='hda' bus='sata'/> <readonly/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.262-2.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:49:51:50'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x03f0'/> <product id='0x0024'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc077'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='none'/> </devices> </domain>
January 6, 20251 yr 1 hour ago, jang430 said: <source file='/dev1/nvme1n1/vdisk1.qcow2'/> This is not typically how you set this, but not sure if it's valid, @SimonFmay know.
January 6, 20251 yr Community Expert 6 hours ago, jang430 said: <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/dev1/nvme1n1/vdisk1.qcow2'/> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> Can you provide a view of the template gui options as that path does not look correct to me
January 9, 20251 yr Author The option is not available for choosing. The SSD is m.2 Adata 1 TB. Edited January 9, 20251 yr by jang430
January 9, 20251 yr 1 hour ago, jang430 said: The option is not available for choosing. Assign the SSD to a pool, and it will be.
January 12, 20251 yr Author I intend to use this SSD for gaming, therefore, I prefer passthrough to get the most out of the performance.
January 12, 20251 yr In that case, you pass through the NVMe device on the VM, assuming it's on its own IOMMU group, bind the device to vfio-pci (Tools - System Devices) and then select it in the VM form, e.g.: And remove the vdisk entry, you just select the device here.
January 13, 20251 yr Author I believe that's what I did, not removing the vdisk entry though. I will do it again and try save some screenshots while I am at it. This time, will try without vdisk entry. Edited January 13, 20251 yr by jang430
January 14, 20251 yr 10 hours ago, jang430 said: I believe that's what I did, not removing the vdisk entry though Remove it and try, or at last without inserting the path you were using, that doesn't look valid to me.
January 26, 20251 yr I passed through my SSD a different than most suggest. I followed SpaceInvader Guide but I had to use the midnight command to find the actual location and name of my drive. 1. open up terminal of the top right hand side of the Unraid GUI. 2. type MC Once you're in midnight command locate your NVME drive by going to /dev/disk/by-id/ 3. take that disk id and plug it into the primary vDisk location as I've attached in my photo.
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.