rug

Following, having the same issue and this is the only thread on the topic.

The VBIOS listed in the first post link indeed reports UEFI NO but the GPU works fine without VBIOS specified after the SeaBios change. I mean it works as far as getting an output on the HDMI output to see the VM on my TV.

Recreating the VM wigh SeaBios allowed me to boot with the GPU passed through, thanks.

I haven't but now that I tried, SeaBios does show up in the webui menu but I can't select it.

I've initially setup a Win 10 VM with a virtual GPU and then configured the virtio drivers for networking from VNC, mapped some drives and minor personalization to prepare the VM. Then I decided to pass through my R9 270 GPU which I previously isolated in the Unraid System Devices settings, I've tried to pass it as first and only GPU and as second GPU (primary Virtual). In both scenarios I've tried with and without VBIOS files download from htechpowerup.com (tried all 3 versions), when a VBIOS is provided I am presented with a win 10 recovery screen while if no VBIOS is selected the booting hangs. Scenario 1 GPU passthrough no VBIOS The HDMI output gives no signal, not even a black screen, the attached HDMI screen actually reports "no signal" Logs from the unraid webui are empty If VBIOS is provided recovery screen is shown (see below) Scenario 2 GPU 1 Virtual - GPU 2 passthrough no VBIOS HDMI output gives no signal VNC shows a stalled loading (first screenshot) If VBIOS is provided reocvery screen is shown (second screenshot) IOMMU isolation active on the GPU. There are no other items its group. VM XML <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='24'> <name>Windows 10 2</name> <uuid>48e8c818-3188-ec8e-2e1a-3f8f3677b41a</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>3</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='3'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-7.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/48e8c818-3188-ec8e-2e1a-3f8f3677b41a_VARS-pure-efi.fd</nvram> </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='3' threads='1'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </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='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10 2/vdisk1.img' index='4'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10 2/vdisk2.img' index='3'/> <backingStore/> <target dev='hdd' bus='virtio'/> <alias name='virtio-disk3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows.iso' index='2'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <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.229-1.iso' index='1'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <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'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:77:dd:59'/> <source bridge='br0'/> <target dev='vnet22'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/6'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/6'> <source path='/dev/pts/6'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-24-Windows 10 2/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <audio id='1' type='none'/> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc063'/> <address bus='1' device='3'/> </source> <alias name='hostdev0'/> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x04d9'/> <product id='0x1702'/> <address bus='1' device='4'/> </source> <alias name='hostdev1'/> <address type='usb' bus='0' port='3'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> tower-diagnostics-20230319-1721.zip

I feared to break something by rebooting in the middle of an array rebuild but it went fine! 😃 Thanks!

I've followed the manual's procedure to upgrade a disk but the array rebuilding is stuck. The disk has been pre-cleared before adding it to the array. After re-starting the array Unraid started the rebuilding process as expected, however, this afternoon after a whole day it didn't progress a bit. I've tried to browse the forum for similar issues and they somewhat all point the finger to something writing on the disks and thus slowing down the process. All docker services are stopped and no VM is running. tower-diagnostics-20221227-1624.zip Diagnostics attached.

I have a KINGSTON SA2000M8250G NVMe disk that I want to use as a cache (single disk pool). However, after assigning it to the cache it shows a wrong size. The disk has 250GB but unraid reports only 273 MB of it. I've tried to remove it from the array and re-add it without success. I'm familiar with the console but I'm unfamiliar with the unraid OS so I haven't been able to manually format the drive with tools like parted or fdisk because they are missing and it seems to me that there is no package manager like apt or pkg? The NVMe previously had few partitions, it was the base installation drive of a Proxmox build, I believe all it needs is a proper formatting and repartition to a single partition (allocating the whole disk). lsblk nvme0n1 259:0 0 232.9G 0 disk ├─nvme0n1p1 259:1 0 260M 0 part /mnt/cache ├─nvme0n1p2 259:2 0 216.6G 0 part └─nvme0n1p3 259:3 0 16G 0 part The partition 2 of the nvme was formatted with a zfs_member label which I was able to remove with fdisk. I now have the full 250GB to use.