Yeah, machine types the most common place for mistakes if you ask me.
Good: For noble this is a no-op - the offending change was in 9.0
(oracular) so noble is not affected in the first place.
Good: Plucky is not yet released, this change looks fine, and we'll try
to fix it asap before release to not come into similar troubles as with
Oracular.
Orcular is a bit in-between....:
- In theory you could have used it on oracular, said you want a qemu8.2
or earlier machine type and would have gotten a power10 cpu type instead
of a power9 cpu type.
- To be clear, if you just used it on oracular in the default way, you'd
have gotten a qemu9.0 machine with a power10 cpu and that will stay that
way after the change.
- We need to ask ourself in the SRU context, do we willingly change
behavior on oracular to fix it. It would fix noble->oracular
migrations/saverestore but break oracular pre/post update
migration/saferestore.
- No matter which way we go we will break someone, of admittedly a
relatively small population and in that an edge case.
=> I'm tempted to say not touching oracular (less effort, soon EOL anyway,
fixed we break about as many as are broken unfixed) is the better path here.
Happy to be convinced otherwise if someone objects.
** Changed in: qemu (Ubuntu Plucky)
Status: New => In Progress
** Changed in: qemu (Ubuntu Noble)
Status: New => Invalid
** Changed in: qemu (Ubuntu Oracular)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106092
Title:
ppc/spapr: fix default cpu for pre-9.0 machines (Backport)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2106092/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
