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 <serge.hal...@ubuntu.com> Wed, 23 Jan 2013 13:24:30 -0600
** Changed in: libvirt (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1102487
Title:
VM won't boot after recent qemu upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1102487/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
