*** This bug is a duplicate of bug 1626070 ***
https://bugs.launchpad.net/bugs/1626070
Yeah I'm pretty sure this is a dupe of bug 1626070.
** This bug has been marked a duplicate of bug 1626070
Removal of former release machine types breaks VMs using them
--
You received this bug notific
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.
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
wrote:
> This has just happened to me. For some reason, all my machines had
> m
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:
hvm
old:
hvm
None of the old XML machines were updated with this new machine flag.
--
You
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 w
