On Sun, Mar 02, 2025 at 01:00:52PM -0500, Kevin Otte wrote:
> On 2/22/25 15:20, Andrea Bolognani wrote:
> > I was hoping that recreating your setup as closely as possible would
> > allow me to reproduce the issue locally, but I have been completely
> > unsuccessful despite several attempts.
>
> I
On 2/22/25 15:20, Andrea Bolognani wrote:
Apologies for taking a while to get back to you.
No worries. The world does seem to be a bit hectic of late.
I was hoping that recreating your setup as closely as possible would
allow me to reproduce the issue locally, but I have been completely
unsuc
Apologies for taking a while to get back to you.
I was hoping that recreating your setup as closely as possible would
allow me to reproduce the issue locally, but I have been completely
unsuccessful despite several attempts.
In the end, I just cheated by adding:
Package: libvirt-daemon-system
On 2/2/25 16:24, Andrea Bolognani wrote:
Going by the logs, you seem to have Xfce installed on your test
environment. Anything notable about the setup? I'm hoping that by
creating an installation as similar as possible to yours I will be
able to trigger the same upgrade failure... That'd make fix
I think I'm starting to figure out what went wrong.
Looking at the log you shared, we can see this sequence of events:
Removing libvirt-daemon-system (9.0.0-4+deb12u1) ...
Preparing to unpack .../libvirt-daemon-driver-qemu_10.7.0-3_amd64.deb ...
Unpacking libvirt-daemon-driver-qemu (10.7.0
Control: severity -1 important
On Sat, Feb 01, 2025 at 01:24:37PM -0500, Kevin Otte wrote:
> On 2/1/25 10:43, Andrea Bolognani wrote:
> > 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
Sorry, working through the brain fog a bit: I was able to start an
existing VM, probably because the apparmor profile with its UUID still
existed. I noticed the issue because I deleted the VM to try and
recreate it, which failed because the template didn't exist.
On 2/1/25 10:43, Andrea Bologn
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
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
> 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-qe
I didn't make any changes to the file. I didn't even know of its
existence until I was trying to troubleshoot why I couldn't create VMs.
This seems to be my week for finding oddball edge cases. Given I've got
the config files back and was able to deploy a VM, I guess you can close
this out as
Le mardi 28 janvier 2025 à 21:20 -0500, Kevin Otte a écrit :
> I had tried doing an "apt --reinstall install ..." of the package to
> get
> the configuration to no avail. Ultimately I had to do a "dpkg
> --force-confmiss -i ..." to get the files.
>
> This was an upgrade from the previous version
I had tried doing an "apt --reinstall install ..." of the package to get
the configuration to no avail. Ultimately I had to do a "dpkg
--force-confmiss -i ..." to get the files.
This was an upgrade from the previous version in testing, so it may be
something to be aware of in the upgrade proce
On Tue, 28 Jan 2025 19:28:24 -0500 Kevin Otte <[ni...@nivex.net](mailto:ni...@nivex.net)> wrote:
> Package: libvirt-daemon-driver-qemu
> Version: 11.0.0-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> The package manifest includes an AppArmor t
Package: libvirt-daemon-driver-qemu
Version: 11.0.0-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The package manifest includes an AppArmor template, but it is not seen on the
filesystem after the package is installed:
root@saratoga:/tmp# dpkg -L libvirt-daemon-driv
15 matches
Mail list logo
