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.
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu
Status: New => Invalid
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
** Changed in: qemu (Ubuntu)
Importance: Undecided => Medium
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu)
Status: New => Confirmed
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
