Thanks for trying, I agree it is a bug/regression - but I'm not yet sure where exactly to point it to. Of the many involved components the two most involved here are libvirt and the kernel.
Would you be able to try this with either: 1. an older libvirt (hard to get onto the new system) 2. a newer libvirt on the old system (if you have a second comparable one you can use https://launchpad.net/~canonical-server/+archive/ubuntu/server-backports) 3. Trying an older kernel matching what 20.04 had - I assume you had the default being 5.4.0-26.30 (you might use https://kernel.ubuntu.com/~kernel-ppa/mainline/ to pick a 5.4 kernel) 4. On said olders system from #2 if you have it try a newer kernel through the HWE stack (https://wiki.ubuntu.com/Kernel/LTSEnablementStack)
Thanks for trying, I agree it is a bug/regression - but I'm not yet sure where exactly to point it to. Of the many involved components the two most involved here are libvirt and the kernel.
Would you be able to try this with either: /launchpad. net/~canonical- server/ +archive/ ubuntu/ server- backports) /kernel. ubuntu. com/~kernel- ppa/mainline/ to pick a 5.4 kernel) /wiki.ubuntu. com/Kernel/ LTSEnablementSt ack)
1. an older libvirt (hard to get onto the new system)
2. a newer libvirt on the old system (if you have a second comparable one you can use https:/
3. Trying an older kernel matching what 20.04 had - I assume you had the default being 5.4.0-26.30 (you might use https:/
4. On said olders system from #2 if you have it try a newer kernel through the HWE stack (https:/