Control: severity -1 normal

08.05.2022 02:18, Thorsten Glaser wrote:
..
In this bugreport, I see it is/was broken with -machine pc-1.1.
There's no indication if it is broken with other machine types.  As
of qemu 5.2 (bullseye) machine types below pc-1.3 are deprecated, and
in 7.0 (current bookworm) they're removed.

This is rather bad, this will break existing VMs on upgrade
with almost certainly zero clues why.

these machine definitions are more than 10 years old. qemu can not keep them 
the way
it were 10 years ago (and as we observed in this bugreport, this makes it 
bitrot).
That wasn't an easy decision but the line must be drawn somewhere, we can't 
support
really old stuff forever.

Please note that in qemu, these machine types are kept mostly in order to make 
the
VMs migratable from one version of qemu to another (which in practice quite 
often
does not work anyway).  During reboot it is possible to switch to a more recent
machine. I know some operating systems can not tolerate hardware changes 
though, -
at least linux is not one of them.

Do you agree with this assessment of the bug you reported? If so,
let's tag this bug with buster and bullseye as indeed I conclude it's
not a bug in bookworm then.

I'd rather consider this a second RC bug in bookworm, if so.

I don't see why it is marked with this severity.  To me it definitely is a
"normal" bug (if not "minor" due to too old hw definitions). It works by
default, and even in rare situations when it doesn't, there are easy
workarounds (switch to another NIC for example).

Or do you refer to the qemu dropping ancient machine types instead of this
netbooting thing?  If that's the case, such bug will be "wontfix" for sure.

I'm lowering severity of this bug to "normal" now.  Please feel free to
set it to other value and provide the reasons why do you think this way.

I'm currently in a really bad situation to look at anything in
detail (waiting for my brain to remember the luks password of
my work laptop), please excuse brevity.

I hope you'll succeed there. It's sad when this happen.

Thanks!

/mjt

Reply via email to