Your message dated Thu, 17 Sep 2026 15:17:39 +0200
with message-id <[email protected]>
and subject line Closing bug: libvirt-daemon: Process libvirtd of user 0 dumped
core at system startup
has caused the Debian Bug report #1139684,
regarding libvirt-daemon: Process libvirtd of user 0 dumped core at system
startup
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.)
--
1139684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1139684
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libvirt-daemon
Version: 12.3.0-1
Severity: important
Dear Maintainer,
* What led up to the situation?
Upgrading Debian/testing
* What exactly did you do (or not do) that was effective (or
ineffective)?
# apt -u -V dist-upgrade
* What was the outcome of this action?
None of my auto-start VM's boot with the system comes up
* What outcome did you expect instead?
All of my auto-start VM's get executed while the system comes up
misabnormaly described above.
Here the problem that shows up with journalctl:
Jun 11 06:53:23 elitedesk.lan.dac systemd[1]: Starting libvirtd.service -
libvirt legacy monolithic daemon...
Jun 11 06:53:25 elitedesk.lan.dac systemd[1]: Started libvirtd.service -
libvirt legacy monolithic daemon.
Jun 11 06:53:28 elitedesk.lan.dac systemd-coredump[4510]: [🡕] Process 2952
(libvirtd) of user 0 dumped core.
Module
libnss_systemd.so.2 from deb systemd-260.1-1.amd64
Module libuuid.so.1
from deb util-linux-2.42.1-3.amd64
Module libudev.so.1
from deb systemd-260.1-1.amd64
Module
libsystemd.so.0 from deb systemd-260.1-1.amd64
Module libblkid.so.1
from deb util-linux-2.42.1-3.amd64
Module libzstd.so.1
from deb libzstd-1.5.7+dfsg-3+b2.amd64
Module libmount.so.1
from deb util-linux-2.42.1-3.amd64
Module libatomic.so.1
from deb gcc-16-16.1.0-1.amd64
Module libgcc_s.so.1
from deb gcc-16-16.1.0-1.amd64
Stack trace of thread
4254:
#0
0x00007f5b9c2eed15 n/a (libvirt_driver_qemu.so + 0xeed15)
#1
0x00007f5b9c2f7377 n/a (libvirt_driver_qemu.so + 0xf7377)
#2
0x00007f5b9c2f77f3 n/a (libvirt_driver_qemu.so + 0xf77f3)
#3
0x00007f5ba4056b65 n/a (libvirt.so.0 + 0x256b65)
#4
0x00007f5ba3fd3bde n/a (libvirt.so.0 + 0x1d3bde)
#5
0x00007f5ba3f0994d virHashForEachSafe (libvirt.so.0 + 0x10994d)
#6
0x00007f5ba3fd531b virDomainObjListForEach (libvirt.so.0 + 0x1d531b)
#7
0x00007f5ba40585c6 virDomainDriverAutoStart (libvirt.so.0 + 0x2585c6)
#8
0x00007f5b9c2ca46e n/a (libvirt_driver_qemu.so + 0xca46e)
#9
0x00007f5ba4145cd7 virStateInitialize (libvirt.so.0 + 0x345cd7)
#10
0x0000564fbdd33c99 n/a (/usr/sbin/libvirtd + 0x4bc99)
#11
0x00007f5ba3f52afa n/a (libvirt.so.0 + 0x152afa)
#12
0x00007f5ba38b4da9 start_thread (libc.so.6 + 0x95da9)
#13
0x00007f5ba3933e08 __clone3 (libc.so.6 + 0x114e08)
...
As you can see above, the libvirtd process from root while the system comes up
dumps core.
After the system enters login ready state, I can manually start my auto-start
VM's with virt-manger -- which works good.
Thank you for your attention.
Sincerely,
Adrian Kiess
-- System Information:
Debian Release: forky/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 7.0.10+deb14-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to fr_FR.UTF-8), LANGUAGE=fr:ru:en:de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libvirt-daemon depends on:
ii libc6 2.42-16
ii libgcc-s1 16.1.0-1
ii libglib2.0-0t64 2.88.1-2
ii libtirpc3t64 1.3.7+ds-1
ii libvirt-common 12.3.0-1
ii libvirt-daemon-common 12.3.0-1
ii libvirt-daemon-log 12.3.0-1
ii libvirt0 12.3.0-1
ii libxml2-16 2.15.3+dfsg-1
ii logrotate 3.22.0-1
Versions of packages libvirt-daemon recommends:
ii libvirt-daemon-driver-interface 12.3.0-1
ii libvirt-daemon-driver-network 12.3.0-1
ii libvirt-daemon-driver-nodedev 12.3.0-1
ii libvirt-daemon-driver-nwfilter 12.3.0-1
ii libvirt-daemon-driver-qemu 12.3.0-1
ii libvirt-daemon-driver-secret 12.3.0-1
ii libvirt-daemon-driver-storage 12.3.0-1
ii libvirt-daemon-driver-storage-disk 12.3.0-1
ii libvirt-daemon-driver-storage-iscsi 12.3.0-1
ii libvirt-daemon-driver-storage-logical 12.3.0-1
ii libvirt-daemon-driver-storage-mpath 12.3.0-1
ii libvirt-daemon-driver-storage-scsi 12.3.0-1
ii libvirt-daemon-lock 12.3.0-1
ii libvirt-daemon-plugin-lockd 12.3.0-1
Versions of packages libvirt-daemon suggests:
ii libvirt-daemon-driver-lxc 12.3.0-1
pn libvirt-daemon-driver-storage-gluster <none>
pn libvirt-daemon-driver-storage-iscsi-direct <none>
pn libvirt-daemon-driver-storage-rbd <none>
pn libvirt-daemon-driver-storage-zfs <none>
ii libvirt-daemon-driver-vbox 12.3.0-1
ii libvirt-daemon-driver-xen 12.3.0-1
ii libvirt-daemon-system 12.3.0-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Closing bug: libvirt-daemon: Process libvirtd of user 0 dumped core at
system startup
--- End Message ---
