This bug was fixed in the package qemu - 1:4.2-3ubuntu6.7
---
qemu (1:4.2-3ubuntu6.7) focal; urgency=medium
* d/p/ubuntu/lp-1882774-*: add newer EPYC processor types (LP: #1887490)
* d/p/u/lp-1896751-exec-rom_reset-Free-rom-data-during-inmigrate-skip.patch:
fix reboot after
Migrated bionic to focal
$ virsh migrate --live testguest3 qemu+ssh://10.102.141.223/system
Then on Focal rebooting from "inside" the guest
$ virsh console testguest3
login and issue "sudo reboot"
1. hanging without the fix
2. upgraded to -proposed
This was actually harder than it should
Hello Markus, or anyone else affected,
Accepted qemu into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:4.2-3ubuntu6.7
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
SRU Template for qemu added and MP linked to fix this in Ubuntu 20.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896751
Title:
Guest hang on reboot after migration from bionic to focal
To
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/391348
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896751
Title:
Guest hang on reboot after
** Changed in: qemu (Ubuntu Focal)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896751
Title:
Guest hang on reboot after migration from bionic to focal
To
** Description changed:
- When migrating a guest from a bionic host to a focal host, the guest may
- hang during reboot. This is due to an upstream optimization that skips
- ROM reset on incoming migrations.
+ [Impact]
+
+ * Upstream skipped rom resets which turned out to affect the
+
Without the fix:
1. spawn guest on bionic
$ uvt-kvm create --password ubuntu testguest arch=amd64 release=bionic
label=daily
2. migrate it over to a focal system
$ virsh migrate --live testguest qemu+ssh://10.102.141.223/system
3. check on focal if the guest arrived e.g. log in
$ virsh console
That's pretty much it. We triggered this fairly reliable as the qemu
versions in bionic and focal pretty much match the ones in the original
bug report. They were gone after we added the mentioned patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is in v5.0.0 so fixed in Groovy.
But the offending patch is in Focal so there we need a fix.
@Markus - is there anything needed to reproduce (particular guest
config) other than migrating from B->F and then rebooting?
** Also affects: qemu (Ubuntu Focal)
Importance: Undecided
10 matches
Mail list logo
