virt-manager error saving

gistfile1.txt

Error saving domain: operation failed: domain save job: unexpectedly failed

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/vmmenu.py", line 182, in cb
    vm.save(meter=asyncjob.get_meter())
  File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn
    ret = fn(self, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/object/domain.py", line 1377, in save
    self._backend.managedSave(0)
  File "/usr/lib/python3.9/site-packages/libvirt.py", line 1780, in managedSave
    raise libvirtError('virDomainManagedSave() failed')
libvirt.libvirtError: operation failed: domain save job: unexpectedly failed

i didn't manage fixing it yet, but apparently this is caused by a migration blocker when using QXL graphics.
This was reverted in this commit
the next qemu release should fix this, in theory compiling it yourself should too but i don't feel like bothering with that for now so i'll let one of you guys find out :^)

This gist and Qemu bug https://gitlab.com/libvirt/libvirt/-/issues/236 are of the same bug. @X41 could you pick that up as Qemu developer?

sorry about the confusion @Jiivee1 but i'm not a qemu dev 😅
and like i've said, this should be fixed already and rolled out in the next release (which should be mid december at the latest according to this)

EDIT: also i finally made myself compile things myself from git and saving with qxl works again!

Very nice to have found the actual issue, I did not think of looking in libvirt issue.

So what happened in my case was just that Void upgraded libvirt package underneat and I got the fix.

@X41 Thanks for clarification.

I can live by not using qxl for now and I can wait qemu 6.2.0 coming down to my distro. As being an ordinary user it is sometimes hard to figure out where the true bug is.