FS#72115 - [qemu] 6.1.0 socket_sockaddr_to_address_unix: assertion error from virt-manager and Gnome Boxes

Attached to Project: Arch Linux
Opened by Albert Ferrero (aferrero) - Monday, 13 September 2021, 06:31 GMT
Last edited by Anatol Pomozov (anatolik) - Thursday, 23 September 2021, 14:57 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Anatol Pomozov (anatolik)
David Runge (dvzrv)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

After upgrading package qemu from 6.0.0-3 to 6.1.0-1, all pre-existing images fail to start throwing an error "Assertion `salen >= sizeof(su->sun_family) + 1 && salen <= sizeof(struct sockaddr_un)' failed." when using virt-manager (libvirt) or Gnome Boxes. The same occurs if I try to build a new image using either virt-manager or Gnome Boxes after the qemu upgrade. Only solution is to downgrade qemu back to 6.0.0-3, or completely remove all network interfaces from the image configuration (which I cannot operate with, unfortunately).

Additional info:
* package version(s): 6.1.0-1
* config and/or log files etc.
* link to upstream bug report, if any
It appears that upstream is aware of the issue and has corrected it, and applied it to the main repository, but there is no official patch that I can see:
https://gitlab.com/qemu-project/qemu/-/issues/607

I imagine that this will be fixed officially once the next version of qemu is released sometime in December according to their roadmap.

Steps to reproduce:
Using either virt-manager or Gnome Boxes, build a brand new image of any kind, it will fail to start. I can recreate the issue 100% on my system, but I'm not sure if there is something special about my configuration otherwise, I haven't been able to track anything down.

I did take the change reported as the fix from upstream and created a patch, then applied it to the official qemu package, installed it on my computer and confirmed that, with the patch, the images work again. I'm attaching them for reference, I'm not sure if we would be willing to modify the official qemu package to include the patch (which would also need to be applied to the qemu-arch-extra package to). This would be temporary until upstream releases their next published release.

I'm more than happy to provide any additional information if required.

My intent in logging this ticket is to bring visibility to this problem from upstream.
This task depends upon

Closed by  Anatol Pomozov (anatolik)
Thursday, 23 September 2021, 14:57 GMT
Reason for closing:  Fixed
Additional comments about closing:  qemu-6.1.0-2
Comment by Anatol Pomozov (anatolik) - Sunday, 19 September 2021, 20:19 GMT
Thank you for reporting about this bug. I pulled the upstream fix and it is published as a part of qemu-6.1.0-2 (currently in [testing]). Please take a look and let me know if you still see any issues.
Comment by Albert Ferrero (aferrero) - Thursday, 23 September 2021, 04:08 GMT
Thank you, I installed qemu-6.1.0-2 and confirm that with the patch I'm not getting the socket error.

Loading...