Control: tag -1 + upstream patch
04.07.2021 16:33, Michael Ablassmeier wrote:
Package: qemu
Version: 1:5.2+dfsg-10
hi,
recently i migrated a windows virtual machine from debian buster to
debian bullseye. Libvirt configuration was exactly the same but the
booted windows system lost its network connectivity and also deactivated
a second attached virtual disk because of policy reasons.
The problem would have also appeared if i simply updated the host system
from buster to bullseye. Chances are high that this also results in an
unbootable virtual machine.
Investigation has shown that the following commit in qemu causing the
issue is most likely:
Commit af1b80ae56c9 ("i386/acpi: fix inconsistent QEMU/OVMF device paths")
And here's the fix:
https://git.qemu.org/?p=qemu.git;a=commit;h=0a343a5add75f9f90c65e932863d57ddbcb28f5c
Now I wonder if this is something which should be fixed... the problem
here is that with this patch applied, machines created with the buggy
qemu will show the behavior you describe, *after* this patch... :)
Okay, it looks like we should keep upgrade from stable to stable working,
not upgrade from testing to stable.. Oh well.. :)
Thank you for the bugreport!
/mjt
