Control: reassign -1 src:libvirt Control: affects -1 src:qemu
On 28.08.2025 09:46, Anonymous wrote:
Package: qemu-system Version: 1:10.1.0+ds-1 Severity: important X-Debbugs-Cc: [email protected] Dear Maintainer, after upgrading today I received the following qemu-* packages: qemu-block-extra 1:10.1.0+ds-1 amd64 qemu-system 1:10.1.0+ds-1 amd64 qemu-system-arm 1:10.1.0+ds-1 amd64 qemu-system-common 1:10.1.0+ds-1 amd64 qemu-system-gui 1:10.1.0+ds-1 amd64 qemu-system-mips 1:10.1.0+ds-1 amd64 qemu-system-misc 1:10.1.0+ds-1
... You most likely don't need all these packages, as you seems to only using x86 version. It should be enough to install just qemu-system-x86, and maybe qemu-utils. But this is unrelated to your bug report.
With these versions of qemu and its auxiliary packages I am unable to connect to my local libvirtd daemon (qemu://system). I see the following segfault in the journal: Aug 28 08:23:21 hostname kernel: rpc-libvirtd[3284]: segfault at 0 ip 00007f0fe3c8123a sp 00007f100d3fe470 error 4 in libvirt_driver_qemu.so[8123a,7f0fe3c4b000+135000] likely on CPU 0 (core 0, socket 0) Aug 28 08:23:21 hostname kernel: Code: 0f 31 c0 48 83 c4 08 5b 5d 41 5c 41 5d c3 66 90 41 8b 74 24 78 48 8d 53 38 48 89 ef e8 0f fd ff ff 83 f8 ff 74 dd 4c 8b 6b 38 <49> 83 7d 00 00 74 d0 31 db 48 8d 2d 62 af 10 00 eb 0e 0f 1f 40 00 Aug 28 08:23:21 hostname systemd[1]: libvirtd.service: Main process exited, code=killed, status=11/SEGV Aug 28 08:23:21 hostname systemd[1]: libvirtd.service: Failed with result 'signal'.
... This is an issue in libvirt, not qemu, - it is the one who segfaults, and it definitely should not crash. Reassigning this bug to libvirt. Unfortunately there's no indication which version of libvirt you're using, hopefully it's the one in sid? Thanks, /mjt
