bally12345

I am having a bit of an issue with using a windows 11 vm with gt 710 passthrough and a HDMI via cat6 KVM. It gets to the windows login page but then once I enter password I just get a blank screen. Cant figure out if its the template or something else. Seemed to be working before I added the USB keyboard / mouse to usb devices <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 11 GFX</name> <uuid>e4c032e9-3fb9-e6e6-4146-ac0ecd1ceb34</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="Windows_11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>33030144</memory> <currentMemory unit='KiB'>33030144</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='6'/> <vcpupin vcpu='1' cpuset='18'/> <vcpupin vcpu='2' cpuset='7'/> <vcpupin vcpu='3' cpuset='19'/> <vcpupin vcpu='4' cpuset='8'/> <vcpupin vcpu='5' cpuset='20'/> <vcpupin vcpu='6' cpuset='9'/> <vcpupin vcpu='7' cpuset='21'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-7.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/e4c032e9-3fb9-e6e6-4146-ac0ecd1ceb34_VARS-pure-efi-tpm.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='4' 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='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <serial>vdisk1</serial> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/iso/virtio-win-0.1.229-1.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:46:cd:2e'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' 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'/> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> </tpm> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/vbios/GT710-mod.rom'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x03f0'/> <product id='0x2b4a'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='none'/> </devices> </domain> Also getting the following in the vm log 2023-05-27T18:32:05.741034Z qemu-system-x86_64: vfio: Cannot reset device 0000:03:00.1, depends on group 38 which is not owned. 2023-05-27T18:32:05.741883Z qemu-system-x86_64: vfio: Cannot reset device 0000:05:00.0, depends on group 37 which is not owned. 2023-05-27T18:32:05.747006Z qemu-system-x86_64: vfio: Cannot reset device 0000:03:00.1, depends on group 38 which is not owned. 2023-05-27T18:32:05.747776Z qemu-system-x86_64: vfio: Cannot reset device 0000:05:00.0, depends on group 37 which is not owned. 2023-05-27T18:34:19.708208Z qemu-system-x86_64: vfio: Cannot reset device 0000:03:00.1, depends on group 38 which is not owned. 2023-05-27T18:34:19.720776Z qemu-system-x86_64: vfio: Cannot reset device 0000:05:00.0, depends on group 37 which is not owned. 2023-05-27T18:34:19.725943Z qemu-system-x86_64: vfio: Cannot reset device 0000:03:00.1, depends on group 38 which is not owned. 2023-05-27T18:34:19.730047Z qemu-system-x86_64: vfio: Cannot reset device 0000:05:00.0, depends on group 37 which is not owned.

Switched back to Virtual due seeing all cores assigned to VM hitting 100% for some reason.

The reason I ask, is I finally after tried GPU passthrough on a WIN11 VM using a old GT710 I had laying around. Did a VBIOS dump, removed the headers passed it through, no code 43 error, latest drivers installed. All good I thought BUT I could swear the VM was better if not the exactly the same! Appreciate its an older card and I use a GTX1650 low profile for Plex but was expecting it to better. Youtube streams on my VM still judder and Core usage on unraid dashboard seems to go up a lot more. This was just a pre-test to make sure everything works but now I am thinking do I need to even bother. Baring in mind I dont game, use a bit of photoshop now and then and have managed for years with just using Virtual GFX. CPU is dual xeon X5690 with no igpu

Happened again overnight Apr 24 04:08:52 Server avahi-daemon[14073]: Registering new address record for fe80::44c7:feff:fed6:5844 on vethdbe9494.*. Apr 24 04:08:52 Server kernel: mediasrv[28110]: segfault at 4 ip 0000000000418457 sp 00001536ad31d0f8 error 4 in mediasrv[405000+3c000] likely on CPU 11 (core 10, socket 1) Apr 24 04:08:52 Server kernel: Code: 00 00 00 e9 61 ff ff ff 48 89 df 89 44 24 0c e8 4f d4 fe ff 8b 44 24 0c eb 83 66 0f 1f 84 00 00 00 00 00 48 8b 87 c0 c5 00 00 <8b> 40 04 c3 0f 1f 44 00 00 48 8b 87 c0 c5 00 00 8b 00 c3 66 0f 1f Apr 24 04:08:53 Server sSMTP[28140]: Creating SSL connection to host server-diagnostics-20230424-0932.zip Diagnostics attached

and if my magic its working again, not sure if its because I still had binhex container and I had the same settings in there but that was stopped. Either way now have my sundtek showing up as freeview and my old vu+ zero for freesat in plex

Yes same adapter and using lsio. I will give it a try again and share diagnostics. Sent from my SM-G991B using Tapatalk

I had a little play around but for some reason the adapter is detected in unraid but the blue activity light does come on. Tried the same adapter in my Vu+ Zero enigma2 box and the blue light comes on fine. Sent from my SM-G991B using Tapatalk

Unable to plugin directly due to size and vga plug next to it. Tried another shorter extension cable but same. Anyone able to recommend a dual or greater pci card for dvbt2 but must be low profile to fit in 2u chassis Sent from my SM-G991B using Tapatalk

Yep I am using one! You might be right... Will try plugging directly into back of server.

Hi it was showing as connected but after reboot it disappeared. Then after another reboot came back. I think it is a faulty device now. It is probably about 8years old and happen to find it again last week so thought I would try it.

Quick one from me, all of a sudden the lsio tvheadend container refuses to connect and I get the following in my logs Apr 19 17:36:54 Server kernel: mediasrv[26610]: segfault at 4 ip 0000000000418457 sp 0000146db352f0f8 error 4 in mediasrv[405000+3c000] likely on CPU 0 (core 0, socket 0) is this driver related or container issue? Tried again with binhex container and same Apr 19 17:56:29 Server emhttpd: cmd: /usr/local/emhttp/plugins/sundtek-driver/include/install.sh binhex-tvheadend Apr 19 17:56:30 Server kernel: process 'e72a9e0ac073aef54ee2c88eb355e1f7bed5fc3aa8941b46831b1b2445b34d97/tmp/.sundtek/chk64bit' started with executable stack Apr 19 17:56:34 Server kernel: docker0: port 9(vethac0d4c3) entered disabled state Apr 19 17:56:34 Server kernel: vethfa70f9d: renamed from eth0 Apr 19 17:56:34 Server avahi-daemon[10418]: Interface vethac0d4c3.IPv6 no longer relevant for mDNS. Apr 19 17:56:34 Server avahi-daemon[10418]: Leaving mDNS multicast group on interface vethac0d4c3.IPv6 with address fe80::9488:3cff:fe05:b643. Apr 19 17:56:34 Server kernel: docker0: port 9(vethac0d4c3) entered disabled state Apr 19 17:56:34 Server kernel: device vethac0d4c3 left promiscuous mode Apr 19 17:56:34 Server kernel: docker0: port 9(vethac0d4c3) entered disabled state Apr 19 17:56:34 Server avahi-daemon[10418]: Withdrawing address record for fe80::9488:3cff:fe05:b643 on vethac0d4c3. Apr 19 17:56:34 Server kernel: docker0: port 9(veth60ddc49) entered blocking state Apr 19 17:56:34 Server kernel: docker0: port 9(veth60ddc49) entered disabled state Apr 19 17:56:34 Server kernel: device veth60ddc49 entered promiscuous mode Apr 19 17:56:34 Server kernel: docker0: port 9(veth60ddc49) entered blocking state Apr 19 17:56:34 Server kernel: docker0: port 9(veth60ddc49) entered forwarding state Apr 19 17:56:35 Server kernel: eth0: renamed from vethb74e2d7 Apr 19 17:56:35 Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth60ddc49: link becomes ready Apr 19 17:56:36 Server avahi-daemon[10418]: Joining mDNS multicast group on interface veth60ddc49.IPv6 with address fe80::6cf1:a5ff:fe73:2a6a. Apr 19 17:56:36 Server avahi-daemon[10418]: New relevant interface veth60ddc49.IPv6 for mDNS. Apr 19 17:56:36 Server avahi-daemon[10418]: Registering new address record for fe80::6cf1:a5ff:fe73:2a6a on veth60ddc49.*. Apr 19 17:56:37 Server kernel: mediasrv[11875]: segfault at 4 ip 0000000000413bd7 sp 000014c46bdfcc88 error 4 in mediasrv[400000+69000] likely on CPU 11 (core 10, socket 1) Apr 19 17:56:37 Server kernel: Code: 89 70 20 48 89 50 28 31 c0 c3 48 89 70 30 48 89 50 38 31 c0 c3 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 48 8b 87 c0 c5 00 00 <8b> 40 04 c3 0f 1f 44 00 00 48 8b 87 c0 c5 00 00 8b 00 c3 66 0f 1f

Hi started again from fresh it is now working!! Many thanks

Unfortunately it didnt work, just tried with LSIO too but same. Nothing showing. Tried adding adapter0 too which is showed on the driver plugin page

No in fact I read you need to have that but not sure how you have both if im honest

Hi I am using Sundtek usb dvbt/c dongle single tuner and seem to have some issues with getting it detected. I have installed both dvb-drvers and sundtek-driver plugins and the adapter is detected and showing as Detected Adapters: adapter0 Set Extra Parameters: to "--device=/dev/bus/usb" and added extra path as suggested However it is still not showing up in binhex-tvheadend as a tuner. Do I need to delete one of the driver plugins or am I missing another step? Have rebooted server after driver install. server-diagnostics-20230419-1135.zip lsusb.txt dmesg.txt