This bug was fixed in the package libvirt - 0.8.8-1ubuntu1
---
libvirt (0.8.8-1ubuntu1) natty; urgency=low
* Resynchronize and merge from Debian unstable. Remaining changes:
- debian/patches:
* 9000-delayed_iff_up_bridge.patch
* 9001-dont_clobber_existing_bridges.pat
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launchpad.net/bugs/720426
Title:
libvirt fails to run vm's with virtio disks and a kernel
--
Ubuntu-server-bugs mailing list
Ubunt
** Patch added: "Patch from upstream"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/720426/+attachment/1857835/+files/libvirt-booton.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.laun
Incidentally, that temporary state switch to Won'tFix was a GUI misfire.
I'd intended confirmed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launchpad.net/bugs/720426
Title:
libvirt fails to run vm
No, I was thinking that thread was a week ago. I'll take the final
upstream patch when it is decided upon.
** Changed in: libvirt (Ubuntu)
Status: Won't Fix => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in
Thanks, Soren. It sounds like just jumping to the just-released 0.8.8
might be the least painful solution.
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Medium
** Changed in: libvirt (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
https://bugs.launchpad.net/bugs/720426
Title:
libvirt fails to run vm's with virtio disks and a kernel
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.
