@tstrike - can you trigger the same issue with all your guests?
You list Windows and Centos guests, does it triggers with Centos as well or
only the Windows guests?
Also if you have a chance (just to be sure) does it trigger with an Ubuntu
guest as well? This would help for people retrying not using a case that
doesn't even trigger in your setup.
@tstrike - you seem to hit this while starting your guest through libvirt.
Could you please attach your guest XML so that we can try to recreate this case?
$ virsh dumpxml <guestname>
That will help when trying to recreate your case.
@tstrike
It would also be helpful to get your qemu commandline as well as any further
messages qemu might have reported.
You'll find that in the per guest log file at:
$ cat /var/log/libvirt/qemu/<guestname>.log
If you could report all that here that should be useful for everyone
tracking this bug.
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
--
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:
New
Status in qemu package in Ubuntu:
Incomplete
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
