Hi again Richud,
the non LTS releases are on a 9 month period until EOL - that is what I
followed.
Anyway we are not here to discuss support times but trying to help you.
Unfortunately in libvirt/qemu there are so many things called snapshots
that I can't help right away, would you mind opening
Hi Christian,
Thank you for replying so quickly.
The 'old type' is only a year old which seems a bit early to be deprecated?
Sorry if I am missing something, but I see no way to fix all my broken
snapshots without the previous machine type existing? (FAQ doesn't mention
snapshots)
Perhaps
Hi Richud,
while the bug here was a special case with the wily type being used in Xenial
and therefore to be retained until the EOL of xenial has passed.
It is different for other machine types like the ones you see issues with atm.
Keeping the old types "almost forever" is a common habit as
recurrence of bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626070
Title:
Removal of former release machine types breaks VMs using them
To manage notifications about this bug go to:
This bug has re-appeared as pc-i440fx-zesty (17.04) is not in the qemu
machine types in cosmic (18.10) - I can now no longer run any snapshots
I made when I was running 17.04.
error: unsupported configuration: Target domain machine type pc-i440fx-cosmic
does not match source pc-i440fx-zesty
$
This bug was fixed in the package qemu - 1:2.6.1+dfsg-0ubuntu4
---
qemu (1:2.6.1+dfsg-0ubuntu4) yakkety; urgency=medium
* retain older xenial machine type to avoid issues starting guests
created on xenial prior to the SRU for bug 1621042. In that regard the old
broken
Yeah Lain Lane just reported the same, thanks smoser for the extra check
- uploading ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626070
Title:
Removal of former release machine types breaks
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626070
Title:
Removal of former release machine types breaks VMs using them
To manage notifications about this bug go to:
Christian, I just verified that adding your ppa and upgrading qemu and
libvirt-bin fixes the problem.
I reproduced the original reported issue simply with:
uvt-kvm create sm1 release=yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
ppa now built and published, ready for verification
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626070
Title:
Removal of former release machine types breaks VMs using them
To manage
Did a local Test until launchpad builds and publishes:
1. create KVM capable xenial container
2. in the Xenial container create a guest
KVM has default to wily (was one part of the old bug)
$ KVM -M | grep wily
pc-i440fx-wily Ubuntu 15.04 PC (i440FX + PIIX, 1996) (default)
3. create
Still building, but for what it is worth the test suite to check
proposed/ppa's now got an "upgrade test" that would have covered this.
Learn from your mistakes ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Things look good to me now packages to verify are currently build at
https://launchpad.net/~paelzer/+archive/ubuntu/qemu-machine-type-dev
While this is urgent and I expect over the day more might show up to be
affected there is no reason to rush more and make it worse - so testing
again ...
add the broken wily type that xenial used as default.
Drop the default and alias, but keep everything else as-is to avoid issues with
upgrades with VMs created on earlier Xenial systems.
** Patch added: "add wily type as it has to be kept being considered as valid
xenial type"
Debdiff ready and currently building for a local test - here attached
for review and later reference.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626070
Title:
Removal of former release machine
Yes I see on your qemu that you are on yakkety - ok good.
Not SRU broken Xenial but "only" certain cases of Yakkety.
thinking ...
So while anything you'd start as soon as the Xenial SRU lands will work
in yakkety you are right and identified a gap where things can break.
That is older (pre SRU)
Well actually on checking to prep something - we didn't remove the
pc-i440fx-wily type.
Just to avoid this issue ...
It was only removed in Yakkety, as migrations have to go "through"
Xenial.
So to confirm - you are likely on a Yakkety system and currently
struggle to get this done for machines
We knew it would happen for migrations, but you are right it is critical if
people just start old (wrong) defines.
We certainly fixed the right issue, but yes the (correct) removal of the wily
type which was the (wrong) default of xenial before can break new starts of
former machines.
Damn -
Christian - thoughts? :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626070
Title:
Removal of former release machine types breaks VMs using them
To manage notifications about this bug go to:
19 matches
Mail list logo