May 10, 20179 yr I just added a HBA to my system that was running a Windows 10 VM perfectly fine for a long time, now I get an error when I try to start the VM. I believe its because the HBA I added is using resources the VM uses to use or at least its causing a conflict, just not sure how to sort it out. Here is the error message.
May 10, 20179 yr check your iommu groupings. I assume the win 10 vm had a GPU? probably not isolated anymore in iommu.
May 10, 20179 yr Author Here is my XML not sure where the problem lies. <domain type='kvm'> <name>Windows 10</name> <uuid>2d78105a-93c9-9428-1e35-4a04eb1b0e73</uuid> <description>Unraid Windows 10 VM</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> <vcpupin vcpu='2' cpuset='6'/> <vcpupin vcpu='3' cpuset='7'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='2' threads='2'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <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/WindowsVM/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/SW_DVD5_NTRL_Win_10_1607_64Bit_English_Home_Pro_X21-05999.ISO'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <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.112-1.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='nec-xhci'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:83:43:84'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </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'/> <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x17ef'/> <product id='0x6019'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x413c'/> <product id='0x2105'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> </domain>
May 10, 20179 yr it's an iommu error. Post the following under tools>System devices: PCI devices IOMMU groups
May 10, 20179 yr Your GPU is in a group with many other devices (including your new HBA, group 1.) It needs to be on its own (with the audio component, 1:00:0 & 1:00:1) to be passed through to the vm successfully. Simplest fix is either try enabling acs override and rebooting or moving cards to different slots and rechecking their iommu grouping. If that doesn't work, then you'll have to modifying your syslinux.cfg with the following and see how it goes: append vfio-pci.ids=8086:0155,10de:0fba initrd=/bzroot
May 10, 20179 yr Author Ok I do have another slot I can try first, thank for the help, appreciate it.
May 10, 20179 yr 2 hours ago, ashman70 said: Ok I do have another slot I can try first, thank for the help, appreciate it. no problem. let me know if it gets sorted out.
May 10, 20179 yr Author Will do, that server is just about finished doing a parity check so if I had time tonight I'll move the card to the other slot.
Archived
This topic is now archived and is closed to further replies.