CHBMB Posted May 30, 2015 Share Posted May 30, 2015 Running RC3, have run VMs successfully before but not on this release. Trying to create a VM and seeing this error. I don't have a bridge setup in network settings as I was intending to use virbr0. Here is my xml <domain type='kvm' id='2'> <name>Windows 7</name> <uuid>770cd46f-f29a-d5b2-2074-1d2c692a6dd8</uuid> <metadata> <vmtemplate name="Custom" icon="windows7.png" os="windows7"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>1</vcpu> <cputune> <vcpupin vcpu='0' cpuset='3'/> </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='1' 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/disks/virtualisation/VirtualMachines/Windows 7/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> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/disks/virtualisation/Media/Win7AIO.iso'/> <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/disks/virtualisation/Media/virtio-win-0.1-100.iso'/> <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='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='ide' index='0'> <alias name='ide0'/> <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> <interface type='bridge'> <mac address='52:54:00:ec:ca:f7'/> <source bridge='virbr0'/> <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/Windows 7.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> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain> And here is the error I am seeing 2015-05-30 12:35:41.307+0000: 8820: info : libvirt version: 1.2.15 2015-05-30 12:35:41.307+0000: 8820: error : virNetDevFeatureAvailable:2968 : ethtool ioctl error: No such device 2015-05-30 12:35:41.316+0000: 8820: error : virNetDevFeatureAvailable:2968 : ethtool ioctl error: No such device 2015-05-30 12:35:41.318+0000: 8820: error : virNetDevFeatureAvailable:2968 : ethtool ioctl error: No such device 2015-05-30 12:35:41.320+0000: 8820: error : virNetDevFeatureAvailable:2968 : ethtool ioctl error: No such device 2015-05-30 12:35:41.321+0000: 8820: error : virNetDevFeatureAvailable:2968 : ethtool ioctl error: No such device 2015-05-30 12:35:41.324+0000: 8820: error : virNetDevFeatureAvailable:2968 : ethtool ioctl error: No such device 2015-05-30 12:35:41.326+0000: 8820: error : virNetDevFeatureAvailable:2968 : ethtool ioctl error: No such device 2015-05-30 22:24:31.693+0000: 8825: warning : qemuDomainObjTaint:1959 : Domain id=2 name='Windows 7' uuid=770cd46f-f29a-d5b2-2074-1d2c692a6dd8 is tainted: high-privileges 2015-05-30 22:24:31.693+0000: 8825: warning : qemuDomainObjTaint:1959 : Domain id=2 name='Windows 7' uuid=770cd46f-f29a-d5b2-2074-1d2c692a6dd8 is tainted: host-cpu And brctl show bridge name bridge id STP enabled interfaces docker0 8000.02fb46eedd39 no veth067cc5f veth1f2a730 veth2085b19 veth29d1551 veth5d10a63 veth612cb50 veth7213dd1 veth74584de veth916c102 vetha8dd261 vethb42853d vethba4507a vethcc613e0 vethec87599 virbr0 8000.525400b64869 yes virbr0-nic vnet0 Any ideas where to go from here? Quote Link to comment
jonp Posted May 31, 2015 Share Posted May 31, 2015 Running RC3, have run VMs successfully before but not on this release. Trying to create a VM and seeing this error. I don't have a bridge setup in network settings as I was intending to use virbr0. Here is my xml <domain type='kvm' id='2'> <name>Windows 7</name> <uuid>770cd46f-f29a-d5b2-2074-1d2c692a6dd8</uuid> <metadata> <vmtemplate name="Custom" icon="windows7.png" os="windows7"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>1</vcpu> <cputune> <vcpupin vcpu='0' cpuset='3'/> </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='1' 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/disks/virtualisation/VirtualMachines/Windows 7/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> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/disks/virtualisation/Media/Win7AIO.iso'/> <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/disks/virtualisation/Media/virtio-win-0.1-100.iso'/> <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='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='ide' index='0'> <alias name='ide0'/> <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> <interface type='bridge'> <mac address='52:54:00:ec:ca:f7'/> <source bridge='virbr0'/> <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/Windows 7.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> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain> And here is the error I am seeing 2015-05-30 12:35:41.307+0000: 8820: info : libvirt version: 1.2.15 2015-05-30 12:35:41.307+0000: 8820: error : virNetDevFeatureAvailable:2968 : ethtool ioctl error: No such device 2015-05-30 12:35:41.316+0000: 8820: error : virNetDevFeatureAvailable:2968 : ethtool ioctl error: No such device 2015-05-30 12:35:41.318+0000: 8820: error : virNetDevFeatureAvailable:2968 : ethtool ioctl error: No such device 2015-05-30 12:35:41.320+0000: 8820: error : virNetDevFeatureAvailable:2968 : ethtool ioctl error: No such device 2015-05-30 12:35:41.321+0000: 8820: error : virNetDevFeatureAvailable:2968 : ethtool ioctl error: No such device 2015-05-30 12:35:41.324+0000: 8820: error : virNetDevFeatureAvailable:2968 : ethtool ioctl error: No such device 2015-05-30 12:35:41.326+0000: 8820: error : virNetDevFeatureAvailable:2968 : ethtool ioctl error: No such device 2015-05-30 22:24:31.693+0000: 8825: warning : qemuDomainObjTaint:1959 : Domain id=2 name='Windows 7' uuid=770cd46f-f29a-d5b2-2074-1d2c692a6dd8 is tainted: high-privileges 2015-05-30 22:24:31.693+0000: 8825: warning : qemuDomainObjTaint:1959 : Domain id=2 name='Windows 7' uuid=770cd46f-f29a-d5b2-2074-1d2c692a6dd8 is tainted: host-cpu And brctl show bridge name bridge id STP enabled interfaces docker0 8000.02fb46eedd39 no veth067cc5f veth1f2a730 veth2085b19 veth29d1551 veth5d10a63 veth612cb50 veth7213dd1 veth74584de veth916c102 vetha8dd261 vethb42853d vethba4507a vethcc613e0 vethec87599 virbr0 8000.525400b64869 yes virbr0-nic vnet0 Any ideas where to go from here? huh, that's the first time I've ever seen this error message. So are your previous VMs working fine or did everything hit a stand still with RC3 for you? Anything unique about this VM you're creating? Quote Link to comment
CHBMB Posted May 31, 2015 Author Share Posted May 31, 2015 Started with a fresh config, only had pfsense and hadn't got around to getting it set up, so no VMs on the RCs. I should say that I've got my syslinux edited to try and passthrough my dual nic card and I'm running a media build. I'll try running vanilla and rolling back to beta 15. Thought I was doing something stupid wrong, maybe not this time then. Quote Link to comment
CHBMB Posted May 31, 2015 Author Share Posted May 31, 2015 So decided to install a completely fresh copy of RC3 from a formatted USB 1. No bridge setup in network settings 2. VM setup as before 3. virbr0 selected as network bridge Same problem. Are there any BIOS settings or anything else I'm missing jon? EDIT: SO have rebooted a number of times and although I couldn't connect to the VM with the VNC Remote, I'm not sure I actually saw any more ioctl errors. Then strangely I could connect with TightVNC client from my Windows machine. Rebooted once more and can now connect with VNC Remote and my web browser. Strange - Think we can mark this solved - sort of! Quote Link to comment
jonp Posted May 31, 2015 Share Posted May 31, 2015 I wouldn't say solved, but at least your back to operational! Quote Link to comment
CHBMB Posted May 31, 2015 Author Share Posted May 31, 2015 I wouldn't say solved, but at least your back to operational! I agree, haven't tried a reboot yet.. Quote Link to comment
CHBMB Posted June 1, 2015 Author Share Posted June 1, 2015 OK, so a reboot worked fine. Went back to Beta 15 again with my original config, and had a look around. I had manually added in virbr0 into the network bridge entry and I suspect that was what confused the whole system, reckon this could be it jon? I'm back on RC3 and everything is working as it should. Quote Link to comment
jonp Posted June 1, 2015 Share Posted June 1, 2015 OK, so a reboot worked fine. Went back to Beta 15 again with my original config, and had a look around. I had manually added in virbr0 into the network bridge entry and I suspect that was what confused the whole system, reckon this could be it jon? I'm back on RC3 and everything is working as it should. Hmm, maybe... 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.