On Fri, Jan 31, 2025 at 03:17:08PM -0500, Kevin Otte wrote:
> 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.Okay, that tracks. It's surprising that you were able to start VMs at all after that point though, I would have expected trouble to have begun back then. Can you please provide the full log for the relevant apt transaction? > $ sudo find /etc/libvirt/ -name '*dpkg*' > /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 Thanks. Can you please provide the output of $ sudo find /etc/libvirt/ -ls | grep -i conf $ sudo find /etc/apparmor.d/ -ls | grep -i virt so that I can get a clearer picture? I should have asked for this to begin with, sorry :) > 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. It's weird that you got the prompt at all: if I'm reading the code correctly, that shouldn't have happened. Of course that's arguably in itself a problem... -- Andrea Bolognani <[email protected]> Resistance is futile, you will be garbage collected.
signature.asc
Description: PGP signature
