I can confirm that this bug has been fixed (zapped). Thank you all for your hard work and determination. A job well done indeed! As a former programmer I love you all's zeal for attacking this bug.
As a side note, knowing what you all go through, I always look things up, walk through at least level 1 stuff and provide logfiles. I hope what little I did, help you all resolve this. Again my thanks, and I believe is this is where we say, "Please close the bug marked SOLVED". -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1866870 Title: KVM Guest pauses after upgrade to Ubuntu 20.04 Status in QEMU: Invalid Status in qemu package in Ubuntu: Invalid Status in seabios package in Ubuntu: Fix Released Bug description: Symptom: Error unpausing domain: internal error: unable to execute QEMU command 'cont': Resetting the Virtual Machine is required Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 66, in newfn ret = fn(self, *args, **kwargs) File "/usr/share/virt-manager/virtManager/object/domain.py", line 1311, in resume self._backend.resume() File "/usr/lib/python3/dist-packages/libvirt.py", line 2174, in resume if ret == -1: raise libvirtError ('virDomainResume() failed', dom=self) libvirt.libvirtError: internal error: unable to execute QEMU command 'cont': Resetting the Virtual Machine is required --- As outlined here: https://bugs.launchpad.net/qemu/+bug/1813165/comments/15 After upgrade, all KVM guests are in a default pause state. Even after forcing them off via virsh, and restarting them the guests are paused. These Guests are not nested. A lot of diganostic information are outlined in the previous bug report link provided. The solution mentioned in previous report had been allegedly integrated into the downstream updates. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1866870/+subscriptions
