Ubuntu
libvirt package

VM won't boot after recent qemu upgrade

Bug #1102487 reported by Stéphane Graber on 2013-01-21

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	libvirt (Ubuntu)	Fix Released	High	Unassigned

Bug Description

As discussed on IRC, I'm attaching the .xml of one of my VMs which stopped working after the recent qemu upgrade.

Apparrently the new qemu doesn't like me using "SandyBridge" as CPU type, it doesn't also like those "<feature>" tags that libvirt added for me at some point and once those issues are cleared, I've seen problems with usb devices and sound cards too.

I can't provide a comprehensive list of the problems I've seen as I directly modified the .xml of my most affected VMs yesterday and got them working by essentially resetting everything to default values.

Related branches

lp:ubuntu/saucy/libvirt

lp:ubuntu/saucy/qemu

Revision history for this message

Stéphane Graber (stgraber) wrote on 2013-01-21:

qemu Edit (3.6 KiB, text/plain)

Revision history for this message

Iain Lane (laney) wrote on 2013-01-21:

fedora.xml Edit (2.4 KiB, text/xml)

My 2¢

With "Device model: ich6" in sound (the default by virt-manager?) I get "Error starting domain: unsupported configuration: hda-duplex not supported in this QEMU binary"

https://ubuntuone.com/27Vn82hay9zqxyL3O98V1k

Changing that to 'ac97' gets the VM to boot.

Serge suggested changing the CPU type to 'kvm64' on IRC and I did that. It fails to boot with "Error starting domain: internal error Cannot find suitable CPU model for given data".

Attaching an XML file.

Revision history for this message

James Hunt (jamesodhunt) wrote on 2013-01-21:

Manually removing the kernel modules and re-loading shows the following in dmesg:

[32444.994884] kvm: VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work properly. Using workaround

Revision history for this message

James Hunt (jamesodhunt) wrote on 2013-01-21:

sorry - wrong bug. Might be related, but #3 was meant for bug 1102488.

Revision history for this message

Serge Hallyn (serge-hallyn) wrote on 2013-01-21: Re: [Bug 1102487] Re: VM won't boot after recent qemu upgrade

Could you please also add the /var/log/libvirt/qemu/*.log file for the
failed VMs?

Revision history for this message

Serge Hallyn (serge-hallyn) wrote on 2013-01-21:

Thanks for reporting this bug.

The audio card not being recognized is a packaging bug, and should be fixed (soon) by an upload with

--audio-card-list="ac97 es1370 sb16 cs4231a adlib gus hda

added to configure.

Serge Hallyn (serge-hallyn) on 2013-01-21

Changed in libvirt (Ubuntu):
status:	New → Confirmed
importance:	Undecided → High
assignee:	nobody → Serge Hallyn (serge-hallyn)
status:	Confirmed → In Progress

Revision history for this message

Serge Hallyn (serge-hallyn) wrote on 2013-01-22:

This appears to be due to an incompatibility (in QMP parsing I assume) between libvirt and the newer 1.3.0 qemu.

I've just tested a custom libvirt 1.0.1 package, which fixed the issue.

We'll need to merge the newest upstream libvirt to fix this.

no longer affects:	qemu (Ubuntu)
Changed in libvirt (Ubuntu):
assignee:	Serge Hallyn (serge-hallyn) → nobody

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-01-23:

This bug was fixed in the package libvirt - 1.0.1-0ubuntu1

---------------
libvirt (1.0.1-0ubuntu1) raring; urgency=low

  * New upstream version. (LP: #1102487)
    + Dropped apparmor-allow-hugepages
    + update dnsmasq-as-priv-user, upstream now uses a configuration file.
    + swap Add_RESUME_event_listener_to_qemu_monitor.patch from git tree for
      the backported handle_resume_1.0.0-0ubuntu4.patch.
    + rebuild debian/patches/build-work-around-broken-kernel-header
    + add bridge-fix-persistent-networks.patch from upstream to fix bug
      where new networks are not marked persistent.
-- Serge Hallyn <email address hidden> Wed, 23 Jan 2013 13:24:30 -0600