Your message dated Sun, 30 Aug 2026 19:21:20 +0200
with message-id
<dmxu5wuxi4xxcdjazovkhjzphcnwq7pof2sqmorkzvx5224t6y@ueo2htdqll6x>
and subject line Re: [Pkg-libvirt-maintainers] Bug#1112273: qemu-system:
rpc-libvirtd segfaults in combination with qemu 10.1.0+ds-1
has caused the Debian Bug report #1112273,
regarding qemu-system: rpc-libvirtd segfaults in combination with qemu
10.1.0+ds-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1112273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1112273
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
amd64
qemu-system-modules-opengl 1:10.1.0+ds-1
amd64
qemu-system-modules-spice 1:10.1.0+ds-1
amd64
qemu-system-ppc 1:10.1.0+ds-1
amd64
qemu-system-riscv 1:10.1.0+ds-1
amd64
qemu-system-s390x 1:10.1.0+ds-1
amd64
qemu-system-sparc 1:10.1.0+ds-1
amd64
qemu-system-x86 1:10.1.0+ds-1
amd64
qemu-utils 1:10.1.0+ds-1
amd64
qemu-system-data 1:10.1.0+ds-1
all
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'.
Aug 28 08:23:21 hostname systemd[1]: libvirtd.service: Unit process 3237 (qemu-
system-alp) remains running after unit stopped.
Aug 28 08:23:21 hostname systemd[1]: libvirtd.service: Unit process 3279 (qemu-
system-alp) remains running after unit stopped.
Aug 28 08:23:21 hostname systemd[1]: libvirtd.service: Unit process 3382 (qemu-
system-alp) remains running after unit stopped.
Aug 28 08:23:21 hostname systemd[1]: libvirtd.service: Consumed 601ms CPU time,
182.4M memory peak.
Aug 28 08:23:21 hostname systemd[1]: libvirtd.service: Scheduled restart job,
restart counter is at 3.
Aug 28 08:23:21 hostname systemd[1]: libvirtd.service: Found left-over process
3237 (qemu-system-alp) in control group while starting unit. Ignoring.
Aug 28 08:23:21 hostname systemd[1]: libvirtd.service: This usually indicates
unclean termination of a previous run, or service implementation deficiencies.
Aug 28 08:23:21 hostname systemd[1]: libvirtd.service: Found left-over process
3279 (qemu-system-alp) in control group while starting unit. Ignoring.
Aug 28 08:23:21 hostname systemd[1]: libvirtd.service: This usually indicates
unclean termination of a previous run, or service implementation deficiencies.
Aug 28 08:23:21 hostname systemd[1]: libvirtd.service: Found left-over process
3382 (qemu-system-alp) in control group while starting unit. Ignoring.
Aug 28 08:23:21 hostname systemd[1]: libvirtd.service: This usually indicates
unclean termination of a previous run, or service implementation deficiencies.
Aug 28 08:23:21 hostname systemd[1]: Starting libvirtd.service - libvirt legacy
monolithic daemon...
Aug 28 08:23:22 hostname systemd[1]: Started libvirtd.service - libvirt legacy
monolithic daemon.
Restarting the system did not solve the problem. Downgrading to the previous
qemu-* package versions as follows fixed the
problem and I am able to connect to the daemon again:
# Download previous packages versions
wget
https://snapshot.debian.org/archive/debian/20250821T204848Z/pool/main/q/qemu/qemu-
block-extra_10.0.3+ds-4_amd64.deb
wget
https://snapshot.debian.org/archive/debian/20250821T204848Z/pool/main/q/qemu/qemu-
system_10.0.3+ds-4_amd64.deb
wget
https://snapshot.debian.org/archive/debian/20250821T204848Z/pool/main/q/qemu/qemu-
system-arm_10.0.3+ds-4_amd64.deb
wget
https://snapshot.debian.org/archive/debian/20250821T204848Z/pool/main/q/qemu/qemu-
system-common_10.0.3+ds-4_amd64.deb
wget
https://snapshot.debian.org/archive/debian/20250821T204848Z/pool/main/q/qemu/qemu-
system-gui_10.0.3+ds-4_amd64.deb
wget
https://snapshot.debian.org/archive/debian/20250821T204848Z/pool/main/q/qemu/qemu-
system-mips_10.0.3+ds-4_amd64.deb
wget
https://snapshot.debian.org/archive/debian/20250821T204848Z/pool/main/q/qemu/qemu-
system-misc_10.0.3+ds-4_amd64.deb
wget
https://snapshot.debian.org/archive/debian/20250821T204848Z/pool/main/q/qemu/qemu-
system-modules-opengl_10.0.3+ds-4_amd64.deb
wget
https://snapshot.debian.org/archive/debian/20250821T204848Z/pool/main/q/qemu/qemu-
system-modules-spice_10.0.3+ds-4_amd64.deb
wget
https://snapshot.debian.org/archive/debian/20250821T204848Z/pool/main/q/qemu/qemu-
system-ppc_10.0.3+ds-4_amd64.deb
wget
https://snapshot.debian.org/archive/debian/20250821T204848Z/pool/main/q/qemu/qemu-
system-riscv_10.0.3+ds-4_amd64.deb
wget
https://snapshot.debian.org/archive/debian/20250821T204848Z/pool/main/q/qemu/qemu-
system-s390x_10.0.3+ds-4_amd64.deb
wget
https://snapshot.debian.org/archive/debian/20250821T204848Z/pool/main/q/qemu/qemu-
system-sparc_10.0.3+ds-4_amd64.deb
wget
https://snapshot.debian.org/archive/debian/20250821T204848Z/pool/main/q/qemu/qemu-
system-x86_10.0.3+ds-4_amd64.deb
wget
https://snapshot.debian.org/archive/debian/20250821T204848Z/pool/main/q/qemu/qemu-
utils_10.0.3+ds-4_amd64.deb
wget
https://snapshot.debian.org/archive/debian/20250821T204848Z/pool/main/q/qemu/qemu-
system-data_10.0.3+ds-4_all.deb
# Perform downgrade
sudo apt install ./qemu-*
Kind regards and thanks for your time,
David
-- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.16.3+deb14-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages qemu-system depends on:
ii qemu-system-arm 1:10.1.0+ds-1
ii qemu-system-mips 1:10.1.0+ds-1
ii qemu-system-misc 1:10.1.0+ds-1
ii qemu-system-ppc 1:10.1.0+ds-1
ii qemu-system-riscv 1:10.1.0+ds-1
ii qemu-system-s390x 1:10.1.0+ds-1
ii qemu-system-sparc 1:10.1.0+ds-1
ii qemu-system-x86 1:10.1.0+ds-1
qemu-system recommends no packages.
qemu-system suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: fixed -1 libvirt/11.7.0-1
On Mon, Sep 08, 2025 at 07:38:23AM +0200, David Brown wrote:
> On 9/7/25 9:21 PM, Andrea Bolognani wrote:
> > On Thu, Aug 28, 2025 at 09:42:22PM +0200, Andrea Bolognani wrote:
> > > On Thu, Aug 28, 2025 at 09:48:45AM +0200, David Brown wrote:
> > > > On 8/28/25 9:39 AM, Michael Tokarev wrote:
> > > > > This is an issue in libvirt, not qemu, - it is the one who segfaults,
> > > > > and it definitely should not crash.
> > >
> > > Agreed. Can you try installing libvirt 11.6.0-1 from experimental and
> > > see whether the issue still reproduces? Alternatively, 11.7.0-1
> > > should come to unstable in a week or so. Since there's a non-zero
> > > chance that the issue has already been identified and addressed
> > > upstream, I'm not too eager to start debugging this very second :)
> >
> > 11.7.0-1 is available from unstable and testing now. Can you please
> > verify wether the issue still shows up there?
>
> The issues does also not manifest itself anymore with 11.7.0-1.
Closing accordingly.
--
Andrea Bolognani <[email protected]>
Resistance is futile, you will be garbage collected.
signature.asc
Description: PGP signature
--- End Message ---
