#1039567 qemu source code in Bullseye contains a typo for the virtio-ballloon-device preventing live migrations

Package:
src:qemu
Source:
src:qemu
Submitter:
Thomas Goirand
Date:
2025-08-13 07:07:02 UTC
Severity:
normal
Tags:
#1039567#5
Date:
2023-06-27 09:40:41 UTC
From:
To:
Hi,

We have a few VMs that are refusing to live-migrate because of this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1984401#c34

I have checked the Debian package, and it does contain the typo.

Note that I have checked the backport version (7.x), and it doesn't
contain the issue (as it was fixed upstream in the 6.x series), however,
we cannot really use it in a Bullseye OpenStack environment (it has
other issues).

Please find, attached to this bug report, the debdiff for the fix.
We're currently testing this. I'll let you know very soon if this
really resolve our live migration issue, but I see no reason why
it would not.

Would you like to upload the fix to Bullseye for the next point
release, or alternatively, allow me to do so (and deal with the
stable release team...)?

Cheers,

Thomas Goirand (zigo)

#1039567#10
Date:
2023-06-27 12:59:33 UTC
From:
To:
Hi !

I can confirm that the attached patch fixes live-migration when
instances have page_poison activated! :)

Let's fix Bullseye ...

Cheers,

Thomas Goirand (zigo)

#1039567#15
Date:
2025-08-13 07:05:22 UTC
From:
To:
Control: severity -1 normal
Control: fixed -1 1:7.2+dfsg-1

bullseye is old.  I've seen this bug report 2 years ago, but hoped to
collect some more fixes for qemu in bullseye, besides this trivial
fix.  But obviously failed.

This particular bug wasn't present in bookworm version of qemu, so
technically, I can close it right away, but also technically, this
wont fix it in bullseye.

Overall, I think trying to fix anything in bullseye qemu at this point
is futile - it brings definitely false sense of security, because that
version of qemu has so many other bugs, including security ones, and
no one bothers to support it for a long time already.  To me, trying to
perform updates for that version is a dis-service for the users.

Just an opinion, nothing more.

Thanks,

/mjt