Thanks for the pointer to /var/log/apt/term.log*
On a previous upgrade to 10.7.0-3 from 9.0.0-4+deb12u1, I see a bunch of
messages about "Preparing transfer of config file ... (from
libvirt-daemon-system to X)" where X included libvirt-daemon-common,
libvirt-daemon-driver-{xen,lxx,qemu,network}.
It looks like that transfer failed somehow because there are a bunch of
{conffile}.dpkg-transfer files on the filesystem.
As requested:
kjotte@saratoga:~$ sudo find /etc/libvirt/ -name '*dpkg*'
[sudo] password for kjotte:
/etc/libvirt/qemu-lockd.conf.dpkg-transfer
/etc/libvirt/qemu.conf.dpkg-old
/etc/libvirt/libvirtd.conf.dpkg-transfer
/etc/libvirt/network.conf.dpkg-transfer
/etc/libvirt/qemu.conf.dpkg-transfer
/etc/libvirt/qemu-sanlock.conf.dpkg-transfer
/etc/libvirt/lxc.conf.dpkg-transfer
/etc/libvirt/libxl-sanlock.conf.dpkg-transfer
/etc/libvirt/libxl-lockd.conf.dpkg-transfer
/etc/libvirt/virtlogd.conf.dpkg-transfer
/etc/libvirt/virtlockd.conf.dpkg-transfer
/etc/libvirt/libxl.conf.dpkg-transfer
I wonder if the transfer was impacted by /etc/libvirt/qemu.conf having
been modified. At the prompt I chose "Y: install the package
maintainer's version" to ease the upgrade with the intent to go back
re-modify it later.
On 1/30/25 18:48, Andrea Bolognani wrote:
On Tue, Jan 28, 2025 at 09:20:38PM -0500, Kevin Otte wrote:
On Tue, 28 Jan 2025 19:28:24 -0500 Kevin Otte wrote:
The package manifest includes an AppArmor template, but it is
not seen on the filesystem after the package is installed:
# dpkg -L libvirt-daemon-driver-qemu | grep -i template
/etc/apparmor.d/libvirt/TEMPLATE.qemu
# ls -l /etc/apparmor.d/libvirt/
total 0
Hey Kevin,
I notice that a few other conffiles are missing:
-- Configuration Files:
/etc/apparmor.d/libvirt/TEMPLATE.qemu [file not found]
/etc/libvirt/qemu-lockd.conf [file not found]
/etc/libvirt/qemu-sanlock.conf [file not found]
/etc/libvirt/qemu.conf [Errno 13] Permission denied: '/etc/libvirt/qemu.conf'
/etc/logrotate.d/libvirtd.qemu [file not found]
That's very interesting because that almost completely overlaps with
the list of conffiles that have been moved from the
libvirt-daemon-system package, where they historically lived, to the
libvirt-daemon-driver-qemu package.
We have special handling in maintainer scripts for those, and though
it should be fairly battle-tested by now it's not impossible that we
would have some lingering bugs.
However...
This was an upgrade from the previous version in testing, so it may be
something to be aware of in the upgrade process.
... this is surprising, since the files were moved in 10.6.0-2. If
you were upgrading from the previous version in testing (10.10.0-3),
that special handling shouldn't have been triggered.
I'll ask you to please verify a few things for me. You should be able
to gather all the information by looking at /var/log/apt/term.log*.
What version of libvirt did you have installed before the upgrade?
Do you have the libvirt-daemon-system package installed? And was it
installed before the upgrade?
Was any message containing the string "transfer of config file" shown
during the upgrade?
What does the output of
$ sudo find /etc/libvirt/ -name '*dpkg*'
look like?
Thanks in advance!
