Rich Posted May 29, 2015 Share Posted May 29, 2015 Hi All, I'm not sure if this is just me, or a fault, but i've just upgraded from beta15 to RC3 and passthrough no longer works. I decided to rebuild my VM at the same time (after migrating primary functions to Docker) and when it comes to editing the XML i now get the following error... Error creating VM: (domain_definition):98: attributes construct error <address domain='0x0000' bus='0x05’ slot='0x00’ function='0x0'/> ----------------------------------------------------^ The pic-stub entry is still in my syslinux.cfg and is correct. I have rebooted the server and VM and tried again, but the same error still pops up. The VM, other than this, is working perfectly though. Any thoughts? Thank you, Rich My xml is, <domain type='kvm' id='2'> <name>Windows7</name> <uuid>f5e24f09-9368-4f38-0799-15f418716cf7</uuid> <metadata> <vmtemplate name="Custom" icon="windows7.png" os="windows7"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='2' threads='1'/> </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/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none' io='native'/> <source file='/mnt/disk/VMs/Windows7/vdisk1.img'/> <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> <controller type='usb' index='0'> <alias name='usb0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:1e:f3:a1'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <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/Windows7.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-gb'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='vmvga' vram='16384' heads='1'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x050d'/> <product id='0x0912'/> <address bus='1' device='2'/> </source> <alias name='hostdev0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain> Quote Link to comment
jonp Posted May 29, 2015 Share Posted May 29, 2015 I don't see anywhere in the xml where you're passing through the NIC. Quote Link to comment
Rich Posted May 30, 2015 Author Share Posted May 30, 2015 I can't enter it to the xml, because i get the error in the opening post. Quote Link to comment
jonp Posted May 30, 2015 Share Posted May 30, 2015 Ok, remove the second <address> block from the xml you're trying to add. Quote Link to comment
Rich Posted May 30, 2015 Author Share Posted May 30, 2015 Sorry, could you be a bit more specific, I'm not sure which part you mean? Quote Link to comment
jonp Posted May 30, 2015 Share Posted May 30, 2015 Sorry, could you be a bit more specific, I'm not sure which part you mean? Let's say this is the XML for the NIC you want to add: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> <alias name='hostdev4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </hostdev> Remove the bolded line from that Quote Link to comment
Rich Posted May 30, 2015 Author Share Posted May 30, 2015 This is what i'm trying to add to the xml, for passthrough, so if i've understood you correctly, there isn't a second <address> line to remove. Apologies if i've got the wrong end of the stick, VMs and xml's are very new to me. <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </source> </hostdev> Quote Link to comment
jonp Posted May 30, 2015 Share Posted May 30, 2015 This is what i'm trying to add to the xml, for passthrough, so if i've understood you correctly, there isn't a second <address> line to remove. Apologies if i've got the wrong end of the stick, VMs and xml's are very new to me. <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </source> </hostdev> Hmm, that's really odd. Maybe try changing the driver name from vfio to kvm? Let me know if that works. Quote Link to comment
Rich Posted June 6, 2015 Author Share Posted June 6, 2015 RC4 seems to have sorted the problem, without me changing anything Quote Link to comment
Recommended Posts
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.