fpoa
-
Posts
16 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by fpoa
-
-
Haven't gotten a reply in the Nvidia plugin support thread, but recently saw a new error message which I do not think is related to the plugin, but am starting to get worried.
QuoteAug 29 19:42:15 SPAMFAM kernel: Modules linked in: nvidia_uvm(O) macvlan xt_CHECKSUM ipt_REJECT xt_nat ip6table_mangle ip6table_nat nf_nat_ipv6 iptable_mangle ip6table_filter ip6_tables vhost_net tun vhost tap veth ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs md_mod bonding rsnvme(PO) sr_mod cdrom nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) btusb btrtl btbcm btintel bluetooth ecdh_generic drm_kms_helper edac_mce_amd wmi_bmof mxm_wmi crc32_pclmul pcbc aesni_intel aes_x86_64 glue_helper crypto_simd ghash_clmulni_intel cryptd drm kvm_amd kvm syscopyarea sysfillrect sysimgblt fb_sys_fops igb(O) k10temp agpgart i2c_piix4 ahci ccp i2c_core nvme libahci usblp crct10dif_pclmul nvme_core crc32c_intel wmi button pcc_cpufreq acpi_cpufreq
Aug 29 19:42:15 SPAMFAM kernel: CPU: 2 PID: 31159 Comm: kworker/2:0 Tainted: P O 4.19.107-Unraid #1
Aug 29 19:42:15 SPAMFAM kernel: Hardware name: System manufacturer System Product Name/ROG STRIX B450-F GAMING, BIOS 2008 03/04/2019
Aug 29 19:42:15 SPAMFAM kernel: Workqueue: events macvlan_process_broadcast [macvlan]
Aug 29 19:42:15 SPAMFAM kernel: RIP: 0010:__nf_conntrack_confirm+0xa0/0x69e
Aug 29 19:42:15 SPAMFAM kernel: Code: 04 e8 56 fb ff ff 44 89 f2 44 89 ff 89 c6 41 89 c4 e8 7f f9 ff ff 48 8b 4c 24 08 84 c0 75 af 48 8b 85 80 00 00 00 a8 08 74 26 <0f> 0b 44 89 e6 44 89 ff 45 31 f6 e8 95 f1 ff ff be 00 02 00 00 48
Aug 29 19:42:15 SPAMFAM kernel: RSP: 0018:ffff88842e683d90 EFLAGS: 00010202
Aug 29 19:42:15 SPAMFAM kernel: RAX: 0000000000000188 RBX: ffff88842b6d0100 RCX: ffff888286597618
Aug 29 19:42:15 SPAMFAM kernel: RDX: 0000000000000001 RSI: 0000000000000081 RDI: ffffffff81e08b90
Aug 29 19:42:15 SPAMFAM kernel: RBP: ffff8882865975c0 R08: 00000000896aacaa R09: ffff8883531b31c0
Aug 29 19:42:15 SPAMFAM kernel: R10: 0000000000000000 R11: ffff8883532c8000 R12: 0000000000008481
Aug 29 19:42:15 SPAMFAM kernel: R13: ffffffff81e91080 R14: 0000000000000000 R15: 000000000000f964
Aug 29 19:42:15 SPAMFAM kernel: FS: 0000000000000000(0000) GS:ffff88842e680000(0000) knlGS:0000000000000000
Aug 29 19:42:15 SPAMFAM kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 29 19:42:15 SPAMFAM kernel: CR2: 00005621bb0b1018 CR3: 0000000001e0a000 CR4: 00000000003406e0
Aug 29 19:42:15 SPAMFAM kernel: Call Trace:
Aug 29 19:42:15 SPAMFAM kernel: <IRQ>
Aug 29 19:42:15 SPAMFAM kernel: ipv4_confirm+0xaf/0xb9
Aug 29 19:42:15 SPAMFAM kernel: nf_hook_slow+0x3a/0x90
Aug 29 19:42:15 SPAMFAM kernel: ip_local_deliver+0xad/0xdc
Aug 29 19:42:15 SPAMFAM kernel: ? ip_sublist_rcv_finish+0x54/0x54
Aug 29 19:42:15 SPAMFAM kernel: ip_rcv+0xa0/0xbe
Aug 29 19:42:15 SPAMFAM kernel: ? ip_rcv_finish_core.isra.0+0x2e1/0x2e1
Aug 29 19:42:15 SPAMFAM kernel: __netif_receive_skb_one_core+0x53/0x6f
Aug 29 19:42:15 SPAMFAM kernel: process_backlog+0x77/0x10e
Aug 29 19:42:15 SPAMFAM kernel: net_rx_action+0x107/0x26c
Aug 29 19:42:15 SPAMFAM kernel: __do_softirq+0xc9/0x1d7
Aug 29 19:42:15 SPAMFAM kernel: do_softirq_own_stack+0x2a/0x40
Aug 29 19:42:15 SPAMFAM kernel: </IRQ>
Aug 29 19:42:15 SPAMFAM kernel: do_softirq+0x4d/0x5a
Aug 29 19:42:15 SPAMFAM kernel: netif_rx_ni+0x1c/0x22
Aug 29 19:42:15 SPAMFAM kernel: macvlan_broadcast+0x111/0x156 [macvlan]
Aug 29 19:42:15 SPAMFAM kernel: ? __switch_to_asm+0x41/0x70
Aug 29 19:42:15 SPAMFAM kernel: macvlan_process_broadcast+0xea/0x128 [macvlan]
Aug 29 19:42:15 SPAMFAM kernel: process_one_work+0x16e/0x24f
Aug 29 19:42:15 SPAMFAM kernel: worker_thread+0x1e2/0x2b8
Aug 29 19:42:15 SPAMFAM kernel: ? rescuer_thread+0x2a7/0x2a7
Aug 29 19:42:15 SPAMFAM kernel: kthread+0x10c/0x114
Aug 29 19:42:15 SPAMFAM kernel: ? kthread_park+0x89/0x89
Aug 29 19:42:15 SPAMFAM kernel: ret_from_fork+0x22/0x40
Aug 29 19:42:15 SPAMFAM kernel: ---[ end trace 4067e0319717aeb0 ]---
Aug 29 19:56:05 SPAMFAM kernel: NVRM: GPU 0000:09:00.0: RmInitAdapter failed! (0x23:0x56:515)
Aug 29 19:56:05 SPAMFAM kernel: NVRM: GPU 0000:09:00.0: rm_init_adapter failed, device minor number 0 -
On 8/23/2020 at 12:18 AM, fpoa said:
Hi community,
I was having some crashing issues so had the server powered off for a few days while I was doing some research. Since powering it back on I've been keeping log viewer open to keep an eye on things. The last several days I have noticed weird messages in the logs.
First, my system:
CPU: Amd Ryzen 7 2700 8 cores
Mobo: Asus ROG Strix B450-F Gaming
16 GB
Asus Radeon HD6450 1gb (passthrough to VM)
GTX 1080 TI (used for plex transcoding)
Running on Unraid 6.8.3 and linuxserver.io's Unraid Nvidia plugin version 2019-06-23.
At first, log was getting spammed with the same error message every 10 seconds or so (flooded past what my syslog viewer could show at a time so no idea how long it went on for). I unfortunately did not save diagnostics or take a screenshot, but it was:
"NVRM: GPU RmInitAdapter failed!
NVRM: rm_init_adapter failed for device bearing minor number 0."
Rebooting the server seemed to fix things at least temporarily. I could watch things on plex and it would use hardware transcoding just fine and no errors in log. However, the next day syslog would be flooded with the above messages again. I saw a post on reddit recommending going back to stock 6.8.3 on the Unraid Nvidia plugin and then redo the Nvidia 6.8.3 build. This seemed to work and there were no errors when I woke up this morning. However, tonight when I checked logs before bed I saw this:
Aug 21 20:34:12 SPAMFAM kernel: NVRM: Xid (PCI:0000:09:00): 79, pid=17083, GPU has fallen off the bus.
Aug 21 20:34:12 SPAMFAM kernel: NVRM: GPU 0000:09:00.0: GPU has fallen off the bus.
Aug 21 20:34:12 SPAMFAM kernel: NVRM: GPU 0000:09:00.0: GPU is on Board .
Aug 21 20:34:12 SPAMFAM kernel: NVRM: A GPU crash dump has been created. If possible, please run
Aug 21 20:34:12 SPAMFAM kernel: NVRM: nvidia-bug-report.sh as root to collect this data before
Aug 21 20:34:12 SPAMFAM kernel: NVRM: the NVIDIA kernel module is unloaded.This time I have the diagnostics file saved if its needed. If any other information is needed, please let me know.
Not sure if this is related to the above issue, but just saw some new errors:
QuoteAug 29 19:42:15 SPAMFAM kernel: Modules linked in: nvidia_uvm(O) macvlan xt_CHECKSUM ipt_REJECT xt_nat ip6table_mangle ip6table_nat nf_nat_ipv6 iptable_mangle ip6table_filter ip6_tables vhost_net tun vhost tap veth ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs md_mod bonding rsnvme(PO) sr_mod cdrom nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) btusb btrtl btbcm btintel bluetooth ecdh_generic drm_kms_helper edac_mce_amd wmi_bmof mxm_wmi crc32_pclmul pcbc aesni_intel aes_x86_64 glue_helper crypto_simd ghash_clmulni_intel cryptd drm kvm_amd kvm syscopyarea sysfillrect sysimgblt fb_sys_fops igb(O) k10temp agpgart i2c_piix4 ahci ccp i2c_core nvme libahci usblp crct10dif_pclmul nvme_core crc32c_intel wmi button pcc_cpufreq acpi_cpufreq
Aug 29 19:42:15 SPAMFAM kernel: CPU: 2 PID: 31159 Comm: kworker/2:0 Tainted: P O 4.19.107-Unraid #1
Aug 29 19:42:15 SPAMFAM kernel: Hardware name: System manufacturer System Product Name/ROG STRIX B450-F GAMING, BIOS 2008 03/04/2019
Aug 29 19:42:15 SPAMFAM kernel: Workqueue: events macvlan_process_broadcast [macvlan]
Aug 29 19:42:15 SPAMFAM kernel: RIP: 0010:__nf_conntrack_confirm+0xa0/0x69e
Aug 29 19:42:15 SPAMFAM kernel: Code: 04 e8 56 fb ff ff 44 89 f2 44 89 ff 89 c6 41 89 c4 e8 7f f9 ff ff 48 8b 4c 24 08 84 c0 75 af 48 8b 85 80 00 00 00 a8 08 74 26 <0f> 0b 44 89 e6 44 89 ff 45 31 f6 e8 95 f1 ff ff be 00 02 00 00 48
Aug 29 19:42:15 SPAMFAM kernel: RSP: 0018:ffff88842e683d90 EFLAGS: 00010202
Aug 29 19:42:15 SPAMFAM kernel: RAX: 0000000000000188 RBX: ffff88842b6d0100 RCX: ffff888286597618
Aug 29 19:42:15 SPAMFAM kernel: RDX: 0000000000000001 RSI: 0000000000000081 RDI: ffffffff81e08b90
Aug 29 19:42:15 SPAMFAM kernel: RBP: ffff8882865975c0 R08: 00000000896aacaa R09: ffff8883531b31c0
Aug 29 19:42:15 SPAMFAM kernel: R10: 0000000000000000 R11: ffff8883532c8000 R12: 0000000000008481
Aug 29 19:42:15 SPAMFAM kernel: R13: ffffffff81e91080 R14: 0000000000000000 R15: 000000000000f964
Aug 29 19:42:15 SPAMFAM kernel: FS: 0000000000000000(0000) GS:ffff88842e680000(0000) knlGS:0000000000000000
Aug 29 19:42:15 SPAMFAM kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 29 19:42:15 SPAMFAM kernel: CR2: 00005621bb0b1018 CR3: 0000000001e0a000 CR4: 00000000003406e0
Aug 29 19:42:15 SPAMFAM kernel: Call Trace:
Aug 29 19:42:15 SPAMFAM kernel: <IRQ>
Aug 29 19:42:15 SPAMFAM kernel: ipv4_confirm+0xaf/0xb9
Aug 29 19:42:15 SPAMFAM kernel: nf_hook_slow+0x3a/0x90
Aug 29 19:42:15 SPAMFAM kernel: ip_local_deliver+0xad/0xdc
Aug 29 19:42:15 SPAMFAM kernel: ? ip_sublist_rcv_finish+0x54/0x54
Aug 29 19:42:15 SPAMFAM kernel: ip_rcv+0xa0/0xbe
Aug 29 19:42:15 SPAMFAM kernel: ? ip_rcv_finish_core.isra.0+0x2e1/0x2e1
Aug 29 19:42:15 SPAMFAM kernel: __netif_receive_skb_one_core+0x53/0x6f
Aug 29 19:42:15 SPAMFAM kernel: process_backlog+0x77/0x10e
Aug 29 19:42:15 SPAMFAM kernel: net_rx_action+0x107/0x26c
Aug 29 19:42:15 SPAMFAM kernel: __do_softirq+0xc9/0x1d7
Aug 29 19:42:15 SPAMFAM kernel: do_softirq_own_stack+0x2a/0x40
Aug 29 19:42:15 SPAMFAM kernel: </IRQ>
Aug 29 19:42:15 SPAMFAM kernel: do_softirq+0x4d/0x5a
Aug 29 19:42:15 SPAMFAM kernel: netif_rx_ni+0x1c/0x22
Aug 29 19:42:15 SPAMFAM kernel: macvlan_broadcast+0x111/0x156 [macvlan]
Aug 29 19:42:15 SPAMFAM kernel: ? __switch_to_asm+0x41/0x70
Aug 29 19:42:15 SPAMFAM kernel: macvlan_process_broadcast+0xea/0x128 [macvlan]
Aug 29 19:42:15 SPAMFAM kernel: process_one_work+0x16e/0x24f
Aug 29 19:42:15 SPAMFAM kernel: worker_thread+0x1e2/0x2b8
Aug 29 19:42:15 SPAMFAM kernel: ? rescuer_thread+0x2a7/0x2a7
Aug 29 19:42:15 SPAMFAM kernel: kthread+0x10c/0x114
Aug 29 19:42:15 SPAMFAM kernel: ? kthread_park+0x89/0x89
Aug 29 19:42:15 SPAMFAM kernel: ret_from_fork+0x22/0x40
Aug 29 19:42:15 SPAMFAM kernel: ---[ end trace 4067e0319717aeb0 ]---
Aug 29 19:56:05 SPAMFAM kernel: NVRM: GPU 0000:09:00.0: RmInitAdapter failed! (0x23:0x56:515)
Aug 29 19:56:05 SPAMFAM kernel: NVRM: GPU 0000:09:00.0: rm_init_adapter failed, device minor number 0 -
Hi community,
I was having some crashing issues so had the server powered off for a few days while I was doing some research. Since powering it back on I've been keeping log viewer open to keep an eye on things. The last several days I have noticed weird messages in the logs.
First, my system:
CPU: Amd Ryzen 7 2700 8 cores
Mobo: Asus ROG Strix B450-F Gaming
16 GB
Asus Radeon HD6450 1gb (passthrough to VM)
GTX 1080 TI (used for plex transcoding)
Running on Unraid 6.8.3 and linuxserver.io's Unraid Nvidia plugin version 2019-06-23.
At first, log was getting spammed with the same error message every 10 seconds or so (flooded past what my syslog viewer could show at a time so no idea how long it went on for). I unfortunately did not save diagnostics or take a screenshot, but it was:
"NVRM: GPU RmInitAdapter failed!
NVRM: rm_init_adapter failed for device bearing minor number 0."
Rebooting the server seemed to fix things at least temporarily. I could watch things on plex and it would use hardware transcoding just fine and no errors in log. However, the next day syslog would be flooded with the above messages again. I saw a post on reddit recommending going back to stock 6.8.3 on the Unraid Nvidia plugin and then redo the Nvidia 6.8.3 build. This seemed to work and there were no errors when I woke up this morning. However, tonight when I checked logs before bed I saw this:
Aug 21 20:34:12 SPAMFAM kernel: NVRM: Xid (PCI:0000:09:00): 79, pid=17083, GPU has fallen off the bus.
Aug 21 20:34:12 SPAMFAM kernel: NVRM: GPU 0000:09:00.0: GPU has fallen off the bus.
Aug 21 20:34:12 SPAMFAM kernel: NVRM: GPU 0000:09:00.0: GPU is on Board .
Aug 21 20:34:12 SPAMFAM kernel: NVRM: A GPU crash dump has been created. If possible, please run
Aug 21 20:34:12 SPAMFAM kernel: NVRM: nvidia-bug-report.sh as root to collect this data before
Aug 21 20:34:12 SPAMFAM kernel: NVRM: the NVIDIA kernel module is unloaded.This time I have the diagnostics file saved if its needed. If any other information is needed, please let me know.
-
10 minutes ago, johnnie.black said:
You should post this on the Nvidia plugin support thread:
Will do, thanks!
-
Hi community,
I was having some crashing issues so had the server powered off for a few days while I was doing some research. Since powering it back on I've been keeping log viewer open to keep an eye on things. The last several days I have noticed weird messages in the logs.
First, my system:
CPU: Amd Ryzen 7 2700 8 cores
Mobo: Asus ROG Strix B450-F Gaming
16 GB
Asus Radeon HD6450 1gb (passthrough to VM)
GTX 1080 TI (used for plex transcoding)
Running on Unraid 6.8.3 and linuxserver.io's Unraid Nvidia plugin version 2019-06-23.
At first, log was getting spammed with the same error message every 10 seconds or so (flooded past what my syslog viewer could show at a time so no idea how long it went on for). I unfortunately did not save diagnostics or take a screenshot, but it was:
"NVRM: GPU RmInitAdapter failed!
NVRM: rm_init_adapter failed for device bearing minor number 0."
Rebooting the server seemed to fix things at least temporarily. I could watch things on plex and it would use hardware transcoding just fine and no errors in log. However, the next day syslog would be flooded with the above messages again. I saw a post on reddit recommending going back to stock 6.8.3 on the Unraid Nvidia plugin and then redo the Nvidia 6.8.3 build. This seemed to work and there were no errors when I woke up this morning. However, tonight when I checked logs before bed I saw this:
Aug 21 20:34:12 SPAMFAM kernel: NVRM: Xid (PCI:0000:09:00): 79, pid=17083, GPU has fallen off the bus.
Aug 21 20:34:12 SPAMFAM kernel: NVRM: GPU 0000:09:00.0: GPU has fallen off the bus.
Aug 21 20:34:12 SPAMFAM kernel: NVRM: GPU 0000:09:00.0: GPU is on Board .
Aug 21 20:34:12 SPAMFAM kernel: NVRM: A GPU crash dump has been created. If possible, please run
Aug 21 20:34:12 SPAMFAM kernel: NVRM: nvidia-bug-report.sh as root to collect this data before
Aug 21 20:34:12 SPAMFAM kernel: NVRM: the NVIDIA kernel module is unloaded.This time I have the diagnostics file saved if its needed. If any other information is needed, please let me know. I am heading to bed now but hopefully someone can help and I'll check this thread when I wake up.
-
25 minutes ago, testdasi said:
Retry the xml in this post. It has all 3 devices. If the sound doesn't work with that xml then the onboard soundcard can't be reset which means you have to reboot the whole server to reboot Windows.
Hi testdasi,
Tried that one again and it doesn't show up in device manager. Your previous XML with just 1 of the 3 devices was the only one so far where onboard audio did show up.
-
4 hours ago, testdasi said:
Try this one and see if it works. If it still doesn't then could just be that it can't be passed through.
Your other issue should be a different topic. Remember to attach diagnostics (Tools -> Diagnostics -> attach zip file).
But before posting, if the xml below doesn't work then make sure to remove the onboard sound card, save and see if the 99% idling still persists. Having devices that aren't kosher can cause strange CPU load (as the driver load hangs).
There's no need to close this topic. It's not solved so just leave it open so people know it isn't resolved.
Progress! I tried your XML and a new audio controller showed up in device manager in windows! It had an exclamation mark so I tried to install the driver. Full driver/software bundle from Asus didn't work. Manually selecting just the driver (not the whole install packet) didn't work. And trying to install through windows update didn't work. However, I think you were right on the CPU issue as with Windows up, all hyperthreads were at minimal usage on the dashboard.
New screenshot of device manager:
I checked the VM logs and saw this:
I noticed your XML took out IOMMU groups 21 and 22. As the log said it needed group 21, I tried adding just that back in but VM doesn't fully boot - black screen and saw this in the log:
Added group 22 back in from basic mode, but that just puts us back where we started. Except now that I edited it in basic mode, I know that messes up whatever you changed in advanced mode/XML.
For reference, here is what the XML now looks like:
<?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10 test</name> <uuid>0ee115c5-e58e-0dcf-b624-04d9f5f62185</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'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='12'/> <vcpupin vcpu='2' cpuset='5'/> <vcpupin vcpu='3' cpuset='13'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='14'/> <vcpupin vcpu='6' cpuset='7'/> <vcpupin vcpu='7' cpuset='15'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-4.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/0ee115c5-e58e-0dcf-b624-04d9f5f62185_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <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'> <topology sockets='1' cores='4' threads='2'/> <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/cache/Vdisks/Windows 10/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.173-2.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <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='0x9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0x15'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='9' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='9' port='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='10' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='10' port='0xc'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='11' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='11' 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='0x03' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <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> <interface type='bridge'> <mac address='52:54:00:44:11:6f'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' 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='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0b' slot='0x00' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0c' slot='0x00' function='0x2'/> </source> <address type='pci' domain='0x0000' bus='0x0b' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x045e'/> <product id='0x0023'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x045e'/> <product id='0x0048'/> </source> <address type='usb' bus='0' port='3'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'/> </domain>
-
50 minutes ago, testdasi said:
Next time you copy-paste XML, please use the forum code functionality (the </> button next to the smiley button) so the code is formatted correctly.
Try this new xml and report back.
Apologies for not formatting correctly. Tried your xml and no change. Booted up just fine, but integrated sound still not getting passed through. Thank you for your time and assistance, I know you weren't confident we could get it to work to begin with. I guess its time for me to give up on the integrated sound and start researching a pci-e sound card that can be passed through.
I have a separate issue I've been trying to figure out (on the dashboard, one of the hyperthreads is pushing 80-99% while windows VM is open and idle). Should I start a new thread for that?
What's the proper etiquette on closing this thread out?
Thanks again testdasi! Both with helping me learn the ropes of Unraid and the forums.
-
I'm not sure. I'm new around here myself. I didn't pick my parts with virtualizing in mind or I'd have done a lot more research and would have gone with different options. You might search on this site, reddit, and review sites to see if anyone mentions it.
-
You can run Unraid headless and pass through your one and only graphics card. I am doing so (technically 2 graphic cards, but 1 is purely for transcoding and the other boots with Unraid and gets passed through to VM). However, it is an AMD card and suffers from the AMD reset bug, but you can definitely run without an integrated GPU if your mobo allows you to do so.
-
Hi,
I found myself in this problem as well. I am also running a Ryzen on a mobo with no integrated gpu and paired with an AMD graphics card. I'm trying to scroll through my browser history with over 100 pages of reddit and unraid.net forum posts. But the solution for me was to roll back my motherboard's bios. Something about recent releases "to prepare for upcoming processors" messed with virtualization. I rolled back to bios dated March 2019 and VM finally booted the next attempt. I had to use a 3rd party app as Asus' system doesn't allow rolling back bios with their built in flasher. However, I'm running a Ryzen 7 2700, not sure if your 3700 changes things. If I can find the exact link I'll edit it in.
-
7 hours ago, testdasi said:
Hmm, copy-paste your latest xml on here please.
<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' id='8'>
<name>Windows 10 test</name>
<uuid>0ee115c5-e58e-0dcf-b624-04d9f5f62185</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'>8</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='4'/>
<vcpupin vcpu='1' cpuset='12'/>
<vcpupin vcpu='2' cpuset='5'/>
<vcpupin vcpu='3' cpuset='13'/>
<vcpupin vcpu='4' cpuset='6'/>
<vcpupin vcpu='5' cpuset='14'/>
<vcpupin vcpu='6' cpuset='7'/>
<vcpupin vcpu='7' cpuset='15'/>
</cputune>
<resource>
<partition>/machine</partition>
</resource>
<os>
<type arch='x86_64' machine='pc-q35-4.2'>hvm</type>
<loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
<nvram>/etc/libvirt/qemu/nvram/0ee115c5-e58e-0dcf-b624-04d9f5f62185_VARS-pure-efi.fd</nvram>
</os>
<features>
<acpi/>
<apic/>
<hyperv>
<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'>
<topology sockets='1' cores='4' threads='2'/>
<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/cache/Vdisks/Windows 10/vdisk1.img' index='2'/>
<backingStore/>
<target dev='hdc' bus='virtio'/>
<boot order='1'/>
<alias name='virtio-disk2'/>
<address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/mnt/user/isos/virtio-win-0.1.173-2.iso' index='1'/>
<backingStore/>
<target dev='hdb' bus='sata'/>
<readonly/>
<alias name='sata0-0-1'/>
<address type='drive' controller='0' bus='0' target='0' unit='1'/>
</disk>
<controller type='sata' index='0'>
<alias name='ide'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
</controller>
<controller type='pci' index='0' model='pcie-root'>
<alias name='pcie.0'/>
</controller>
<controller type='pci' index='1' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='1' port='0x10'/>
<alias name='pci.1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
</controller>
<controller type='pci' index='2' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='2' port='0x11'/>
<alias name='pci.2'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
</controller>
<controller type='pci' index='3' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='3' port='0x12'/>
<alias name='pci.3'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
</controller>
<controller type='pci' index='4' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='4' port='0x13'/>
<alias name='pci.4'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
</controller>
<controller type='pci' index='5' model='pcie-to-pci-bridge'>
<model name='pcie-pci-bridge'/>
<alias name='pci.5'/>
<address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
</controller>
<controller type='pci' index='6' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='6' port='0x14'/>
<alias name='pci.6'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/>
</controller>
<controller type='pci' index='7' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='7' port='0x15'/>
<alias name='pci.7'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/>
</controller>
<controller type='pci' index='8' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='8' port='0x8'/>
<alias name='pci.8'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
</controller>
<controller type='virtio-serial' index='0'>
<alias name='virtio-serial0'/>
<address type='pci' domain='0x0000' bus='0x03' slot='0x00' 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:44:11:6f'/>
<source bridge='br0'/>
<target dev='vnet0'/>
<model type='virtio'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
</interface>
<serial type='pty'>
<source path='/dev/pts/0'/>
<target type='isa-serial' port='0'>
<model name='isa-serial'/>
</target>
<alias name='serial0'/>
</serial>
<console type='pty' tty='/dev/pts/0'>
<source path='/dev/pts/0'/>
<target type='serial' port='0'/>
<alias name='serial0'/>
</console>
<channel type='unix'>
<source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-8-Windows 10 test/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>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/>
</source>
<alias name='hostdev0'/>
<address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0' multifunction='on'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x08' slot='0x00' function='0x1'/>
</source>
<alias name='hostdev1'/>
<address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x1'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x0c' slot='0x00' function='0x0'/>
</source>
<alias name='hostdev2'/>
<address type='pci' domain='0x0000' bus='0x05' slot='0x01' function='0x0' multifunction='on'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x0c' slot='0x00' function='0x2'/>
</source>
<alias name='hostdev3'/>
<address type='pci' domain='0x0000' bus='0x05' slot='0x01' function='0x1'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x0c' slot='0x00' function='0x3'/>
</source>
<alias name='hostdev4'/>
<address type='pci' domain='0x0000' bus='0x05' slot='0x01' function='0x2'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x0b' slot='0x00' function='0x3'/>
</source>
<alias name='hostdev5'/>
<address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x045e'/>
<product id='0x0023'/>
<address bus='1' device='2'/>
</source>
<alias name='hostdev6'/>
<address type='usb' bus='0' port='2'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x045e'/>
<product id='0x0048'/>
<address bus='1' device='3'/>
</source>
<alias name='hostdev7'/>
<address type='usb' bus='0' port='3'/>
</hostdev>
<memballoon model='none'/>
</devices>
<seclabel type='dynamic' model='dac' relabel='yes'>
<label>+0:+100</label>
<imagelabel>+0:+100</imagelabel>
</seclabel>
</domain> -
34 minutes ago, testdasi said:
First try changing slot='0x01' to slot='0x00' for the 3 hostdev blocks you posted (i.e. the 3 0c devices)
It's rather unusual to have slot 01 in a pass through (those slots are typically only non-zero for the PCIe slots config up top of the xml).
That is the most likely cause for their not showing up in Windows Device Manager because there's no possible config for 2nd slot of a single-slot device (Linux counts from zero, slot='0x01' means the 2nd slot).
I'm not too optimistic with your passing through the onboard audio though since I have noticed unsuccessful attempts on here with the X4xx chipsets.
PS: There's no need to obscure the MAC Address on the vm template screenshot. 😅 52:54 MACs are custom addresses (not dissimilar to 192.168.x.x custom IP addresses) so it doesn't actually point to any of your physical device. It's just used as a virtual address for your virtual network adapter. And you already have revealed it in your xml copy-paste so your obscuring it on the screenshot was to no avail.
Thanks again testdasi. Facepalm on the MAC!
Changing all 3 slots to slot='0x00' did not work. Got the following error:
XML error: Invalid PCI address 0000:05:00.0. slot must be >= 1
So I changed all 3 slots to '0x01' with multifunction='on' . I tried with both functions functions = 0x0, 0x1, 0x2 and also functions = 0x0, 0x2, 0x3 to match the functions in the address domain. None of the above worked.
I know you weren't optimistic, but any other suggestions? Is my only other option to find a cheap pci-e sound card to passthrough? Any recommendations if so?
-
33 minutes ago, testdasi said:
What do you mean by "does not show up in Device Manager in Windows"? Screenshot would be helpful.
Also in your template, you are passing through the multi-function stack 0c in multiple slots instead of multiple function.
Is there any particular reason for that?
If you want to match the physical arrangement then you need to match by having multiple function and not having multiple slots.
Could be the reason for your issue.
Hi testdasi and thank you for responding!
Screenshots:
screenshot of template in basic mode - shows where I selected the onboard audio in addition to audio portion of Asus graphics card.
screenshot of device manager - shows both audio and display portion of graphics card, but onboard audio does not show up (I believe it should say Realtek audio adapter)
Regarding the multi-function stack, are you referring to IOMMU groups 21, 22, and 23? Am I supposed to treat it how spaceinvader one instructed to treat both audio and graphic portion of the graphics card?
I assumed since they were all split into 3 separate IOMMU groups, that I should just include them in the syslinux config file and that would be enough.
If I am understanding you correctly, should I change those 3 to be like the following?:
Quote<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x0c' slot='0x00' function='0x3'/>
</source>
<alias name='hostdev2'/>
<address type='pci' domain='0x0000' bus='0x05' slot='0x01' function='0x0' multifunction='on'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x0c' slot='0x00' function='0x0'/>
</source>
<alias name='hostdev4'/>
<address type='pci' domain='0x0000' bus='0x05' slot='0x01' function='0x1'/>
</hostdev><hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x0c' slot='0x00' function='0x2'/>
</source>
<alias name='hostdev5'/>
<address type='pci' domain='0x0000' bus='0x05' slot='0x01' function='0x2'/>
</hostdev>Something like that? Should they all be "bus='0x05' slot='0x01' " in the <address type> portions?
Does it matter that they have different functions in the <address domain> portions? (function='0x3' in first, function='0x0' in second, function='0x2' in third)
And I assume I keep their corresponding entries in the syslinux config? (1022:1455, 1022:7901, 1022:1457)
Hope I'm understanding you correctly. This is all new to me and I appreciate the help!
-
Hi everyone,
New user here and and after watching as many of spaceinvader one's tutorials as were relevant, I'm finding myself still stuck. I originally built this rig as a windows 10 daily driver that would also host a plex server. It wasn't intended to be a gaming rig, so I just put in a cheap graphics card since the motherboard did not have integrated graphics. After the fact, my brother gave me a used 1080 TI which I thought would be great for hardware transcoding.
I spent 3 days initially getting the VM to work at all, having problems with both i440fx-4.2 and Q35-4.2 machine type. I discovered that it was a bios issue with recent AM4 based motherboards and reverted back to bios version 2008 from March 2019 and VM booted the next attempt. IOMMU groups are good, everything I want passed through are isolated. The integrated sound shows up as a soundcard option in the VM template, but does not show up in Device Manager in Windows.Any help would be greatly appreciated.
Here are the necessary pieces of information:
Here's the hardware:
CPU: Amd Ryzen 7 2700 8 cores, (4 cores = 8 threads dedicated to VM)
Mobo: Asus ROG Strix B450-F Gaming
--- onboard Realtek audio (having problems passingthrough to VM)
16 GB (4 gb's dedicated to VM)
Asus Radeon HD6450 1gb (passthrough to VM)
GTX 1080 TI (passthrough to plex)
HVM and IOMMU are enabled
Syslinux config:
Quotedefault menu.c32
menu title Lime Technology, Inc.
prompt 0
timeout 50
label Unraid OS
menu default
kernel /bzimage
append vfio-pci.ids=1002:6779,1002:aa98,1022:145f,1022:1455,1022:7901,1022:1457 isolcpus=4,12,5,13,6,14,7,15 initrd=/bzroot
label Unraid OS GUI Mode
kernel /bzimage
append initrd=/bzroot,/bzroot-gui
label Unraid OS Safe Mode (no plugins, no GUI)
kernel /bzimage
append initrd=/bzroot unraidsafemode
label Unraid OS GUI Safe Mode (no plugins)
kernel /bzimage
append initrd=/bzroot,/bzroot-gui unraidsafemode
label Memtest86+
kernel /memtestIOMMU Groupings:
QuoteIOMMU group 0:[1022:1452] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
IOMMU group 1:[1022:1453] 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
IOMMU group 2:[1022:1452] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
IOMMU group 3:[1022:1452] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
IOMMU group 4:[1022:1453] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
IOMMU group 5:[1022:1453] 00:03.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
IOMMU group 6:[1022:1453] 00:03.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
IOMMU group 7:[1022:1452] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
IOMMU group 8:[1022:1452] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
IOMMU group 9:[1022:1454] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
IOMMU group 10:[1022:1452] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
IOMMU group 11:[1022:1454] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
IOMMU group 12:[1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59)
[1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
IOMMU group 13:[1022:1460] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0
[1022:1461] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1
[1022:1462] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2
[1022:1463] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3
[1022:1464] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4
[1022:1465] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5
[1022:1466] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6
[1022:1467] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7
IOMMU group 14:[1022:43d5] 01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 XHCI Controller (rev 01)
[1022:43c8] 01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller (rev 01)
[1022:43c6] 01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Bridge (rev 01)
[1022:43c7] 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
[1022:43c7] 02:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
[1022:43c7] 02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
[1022:43c7] 02:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
[1022:43c7] 02:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
[8086:1539] 03:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
IOMMU group 15:[1002:6779] 08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]
[1002:aa98] 08:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI Audio [Radeon HD 6450 / 7450/8450/8490 OEM / R5 230/235/235X OEM]
IOMMU group 16:[10de:1b06] 09:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1)
[10de:10ef] 09:00.1 Audio device: NVIDIA Corporation GP102 HDMI Audio Controller (rev a1)
IOMMU group 17:[8086:f1a8] 0a:00.0 Non-Volatile memory controller: Intel Corporation SSD 660P Series (rev 03)
IOMMU group 18:[1022:145a] 0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function
IOMMU group 19:[1022:1456] 0b:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor
IOMMU group 20:[1022:145f] 0b:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 Host controller
IOMMU group 21:[1022:1455] 0c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function (rev ff)
IOMMU group 22:[1022:7901] 0c:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev ff)
IOMMU group 23:[1022:1457] 0c:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller (rev ff)
VM XML:
Quote<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' id='6'>
<name>Windows 10 test</name>
<uuid>0ee115c5-e58e-0dcf-b624-04d9f5f62185</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'>8</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='4'/>
<vcpupin vcpu='1' cpuset='12'/>
<vcpupin vcpu='2' cpuset='5'/>
<vcpupin vcpu='3' cpuset='13'/>
<vcpupin vcpu='4' cpuset='6'/>
<vcpupin vcpu='5' cpuset='14'/>
<vcpupin vcpu='6' cpuset='7'/>
<vcpupin vcpu='7' cpuset='15'/>
</cputune>
<resource>
<partition>/machine</partition>
</resource>
<os>
<type arch='x86_64' machine='pc-q35-4.2'>hvm</type>
<loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
<nvram>/etc/libvirt/qemu/nvram/0ee115c5-e58e-0dcf-b624-04d9f5f62185_VARS-pure-efi.fd</nvram>
</os>
<features>
<acpi/>
<apic/>
<hyperv>
<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'>
<topology sockets='1' cores='4' threads='2'/>
<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/cache/Vdisks/Windows 10/vdisk1.img' index='2'/>
<backingStore/>
<target dev='hdc' bus='virtio'/>
<boot order='1'/>
<alias name='virtio-disk2'/>
<address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/mnt/user/isos/virtio-win-0.1.173-2.iso' index='1'/>
<backingStore/>
<target dev='hdb' bus='sata'/>
<readonly/>
<alias name='sata0-0-1'/>
<address type='drive' controller='0' bus='0' target='0' unit='1'/>
</disk>
<controller type='sata' index='0'>
<alias name='ide'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
</controller>
<controller type='pci' index='0' model='pcie-root'>
<alias name='pcie.0'/>
</controller>
<controller type='pci' index='1' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='1' port='0x10'/>
<alias name='pci.1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
</controller>
<controller type='pci' index='2' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='2' port='0x11'/>
<alias name='pci.2'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
</controller>
<controller type='pci' index='3' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='3' port='0x12'/>
<alias name='pci.3'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
</controller>
<controller type='pci' index='4' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='4' port='0x13'/>
<alias name='pci.4'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
</controller>
<controller type='pci' index='5' model='pcie-to-pci-bridge'>
<model name='pcie-pci-bridge'/>
<alias name='pci.5'/>
<address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
</controller>
<controller type='pci' index='6' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='6' port='0x14'/>
<alias name='pci.6'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/>
</controller>
<controller type='pci' index='7' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='7' port='0x15'/>
<alias name='pci.7'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/>
</controller>
<controller type='pci' index='8' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='8' port='0x8'/>
<alias name='pci.8'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
</controller>
<controller type='virtio-serial' index='0'>
<alias name='virtio-serial0'/>
<address type='pci' domain='0x0000' bus='0x03' slot='0x00' 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:44:11:6f'/>
<source bridge='br0'/>
<target dev='vnet0'/>
<model type='virtio'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
</interface>
<serial type='pty'>
<source path='/dev/pts/0'/>
<target type='isa-serial' port='0'>
<model name='isa-serial'/>
</target>
<alias name='serial0'/>
</serial>
<console type='pty' tty='/dev/pts/0'>
<source path='/dev/pts/0'/>
<target type='serial' port='0'/>
<alias name='serial0'/>
</console>
<channel type='unix'>
<source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-6-Windows 10 test/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>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/>
</source>
<alias name='hostdev0'/>
<address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0' multifunction='on'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x08' slot='0x00' function='0x1'/>
</source>
<alias name='hostdev1'/>
<address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x1'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x0c' slot='0x00' function='0x3'/>
</source>
<alias name='hostdev2'/>
<address type='pci' domain='0x0000' bus='0x05' slot='0x01' function='0x0'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x0b' slot='0x00' function='0x3'/>
</source>
<alias name='hostdev3'/>
<address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x0c' slot='0x00' function='0x0'/>
</source>
<alias name='hostdev4'/>
<address type='pci' domain='0x0000' bus='0x05' slot='0x02' function='0x0'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x0c' slot='0x00' function='0x2'/>
</source>
<alias name='hostdev5'/>
<address type='pci' domain='0x0000' bus='0x05' slot='0x03' function='0x0'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x045e'/>
<product id='0x0023'/>
<address bus='1' device='2'/>
</source>
<alias name='hostdev6'/>
<address type='usb' bus='0' port='2'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x045e'/>
<product id='0x0048'/>
<address bus='1' device='3'/>
</source>
<alias name='hostdev7'/>
<address type='usb' bus='0' port='3'/>
</hostdev>
<memballoon model='none'/>
</devices>
<seclabel type='dynamic' model='dac' relabel='yes'>
<label>+0:+100</label>
<imagelabel>+0:+100</imagelabel>
</seclabel>
</domain>
GPU issue, "GPU has fallen off the bus"
in General Support
Posted
Like others in that thread, I had followed spaceinvader one's video on setting up pihole. It is the only docker I have with a custom IP. I've had it setup for almost 4 months now and don't think I've ever seen that macvlan trace error before, but perhaps I missed it. Of note, according to that thread multiple macvlan trace errors can result in Unraid crashing - perhaps I have missed a bunch and that is causing my hard reboots.
I'm not very network savvy, but it looks like I'll need to learn how to setup vlan's. Thank you johnnie.black!