diff options
Diffstat (limited to 'results/classifier/118/unknown/1305402')
| -rw-r--r-- | results/classifier/118/unknown/1305402 | 129 |
1 files changed, 129 insertions, 0 deletions
diff --git a/results/classifier/118/unknown/1305402 b/results/classifier/118/unknown/1305402 new file mode 100644 index 000000000..306161cb8 --- /dev/null +++ b/results/classifier/118/unknown/1305402 @@ -0,0 +1,129 @@ +user-level: 0.926 +mistranslation: 0.883 +peripherals: 0.868 +KVM: 0.865 +network: 0.852 +hypervisor: 0.851 +risc-v: 0.848 +graphic: 0.840 +debug: 0.833 +permissions: 0.826 +TCG: 0.826 +x86: 0.822 +vnc: 0.821 +semantic: 0.813 +files: 0.813 +virtual: 0.810 +VMM: 0.808 +performance: 0.801 +ppc: 0.798 +assembly: 0.795 +socket: 0.794 +register: 0.790 +device: 0.789 +architecture: 0.784 +PID: 0.777 +arm: 0.769 +kernel: 0.768 +boot: 0.744 +i386: 0.731 + +libvirt fails to start VirtualMachines + +I've created several kvm based machines with the 'trusty' designation using virtual machine manager. They have operated well over the last 4 days without issue. I did an apt-get upgrade, and qemu was in the list of updates. + +After upgrading, I am unable to start any of the provisioned virtual machines with the following error output + +virsh # start node2 +error: Failed to start domain node2 +error: internal error: process exited while connecting to monitor: qemu-system-x86_64: -machine trusty,accel=kvm,usb=off: Unsupported machine type +Use -machine help to list supported machines! + + +virsh # start node3 +error: Failed to start domain node3 +error: internal error: process exited while connecting to monitor: qemu-system-x86_64: -machine trusty,accel=kvm,usb=off: Unsupported machine type +Use -machine help to list supported machines! + + + +$ dpkg -l | grep kvm +ii qemu-kvm 2.0.0~rc1+dfsg-0ubuntu3 amd64 QEMU Full virtualization on x86 hardware (transitional package) + +Log snippet from vm 'media' that was verified working, and fails to start after the upgrade. + +LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm-spice -name media -S -machine trusty,accel=kvm,usb=off -m 1548 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 60b20f7b-6d20-bcb3-f4fc-808a9b2fe0d0 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/media.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot menu=off,strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/libvirt/images/media.img,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/home/charles/iso/ubuntu-desktop-12.04.4-amd64.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:a0:69:d9,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:1 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 +char device redirected to /dev/pts/13 (label charserial0) +qemu: terminating on signal 15 from pid 31688 +2014-04-10 03:36:54.593+0000: shutting down +2014-04-10 03:59:25.487+0000: starting up +LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm-spice -name media -S -machine trusty,accel=kvm,usb=off -m 1548 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 60b20f7b-6d20-bcb3-f4fc-808a9b2fe0d0 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/media.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot menu=off,strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/libvirt/images/media.img,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/home/charles/iso/ubuntu-desktop-12.04.4-amd64.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=25 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:a0:69:d9,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 +qemu-system-x86_64: -machine trusty,accel=kvm,usb=off: Unsupported machine type +Use -machine help to list supported machines! +2014-04-10 03:59:25.696+0000: shutting down + +After some additional investigating it looks like the XML format for the trusty machine has changed. I created a new VM and got it to boot off my MAAS cluster, The immediate change I see is: + +new: + <type arch='x86_64' machine='pc-i440fx-trusty'>hvm</type> + +old: + <type arch='x86_64' machine='trusty'>hvm</type> + +None of the old XML machines were updated with this new machine flag. + +Thanks for reporting this bug. We briefly had a 'trusty' machine type, with a corresponding libvirt patch to handle it. When we renamed the trusty machine type we dropped the libvirt patch to handle it. + +We should either re-introduce the libvirt patch to handle the trusty machine type for those who have stale VM definitions, or mention this in the release notes. In either case we should keep this bug open to guide others who run into this problem. + +This has just happened to me. For some reason, all my machines had machine='pc-i440fx-wily'. +After an update in yakkety, they stopped working. + +$ qemu-system-x86_64 -enable-kvm -machine help | grep wily + +So I updated the machine xml to a supported machine as Charles suggested, and they work again. + +Here's the note for my future self about how to do the update: + +$ virsh dumpxml $machine-name > /tmp/machine.xml +Edit the xml. +$ virsh define /tmp/machine.xml + +Machine type changes may be related to: + +https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1626070 + +There's a PPA in the bug with a fix for at least the wily machine type. + +On Thu, Sep 22, 2016 at 6:05 PM, Leo Arias <email address hidden> wrote: + +> This has just happened to me. For some reason, all my machines had +> machine='pc-i440fx-wily'. +> After an update in yakkety, they stopped working. +> +> $ qemu-system-x86_64 -enable-kvm -machine help | grep wily +> +> So I updated the machine xml to a supported machine as Charles +> suggested, and they work again. +> +> Here's the note for my future self about how to do the update: +> +> $ virsh dumpxml $machine-name > /tmp/machine.xml +> Edit the xml. +> $ virsh define /tmp/machine.xml +> +> -- +> You received this bug notification because you are subscribed to qemu in +> Ubuntu. +> https://bugs.launchpad.net/bugs/1305402 +> +> Title: +> libvirt fails to start VirtualMachines +> +> To manage notifications about this bug go to: +> https://bugs.launchpad.net/qemu/+bug/1305402/+subscriptions +> + + +Yeah I'm pretty sure this is a dupe of bug 1626070. + |