Package: libvirt-daemon-system
Version: 5.0.0-4
Followup-For: Bug #890084
Dear Maintainer,
this happened yesterday again. It is most likely related to a restart
of the host system.
After removing the apparmor.d profiles with zero length, the vm started as
expected.
The bug report asks about th
Control: tag -1 + unreproducible
Hi Craig,
did this problem happen again? If it ever does, please share the
output of "sudo journalctl -u libvirtd.service" and the relevant
file timestamps.
I'm using libvirt + AppArmor heavily and have never seen it myself :/
Cheers,
--
intrigeri
I am currently running 4.0.0-2 but I'm not sure if that was the version
that created the file.
The strange thing is I have had apparmor running for months and that
virtual host for a year or more, so I'm not sure why it happened now.
- Craig
On Sun, 11 Feb 2018 at 18:00 intrigeri wrote:
> Co
Control: reassign -1 libvirt-daemon-system
Control: tag -1 + moreinfo
Hi!
Craig Small:
> apparmor is basically stopping libvirt hosts from running.
> The reporting is pretty terrible, I'm not sure what file it is trying to
> find. The only thing in the logs is the audit lines.
Ouch.
> Removing
Package: apparmor
Version: 2.12-2
apparmor is basically stopping libvirt hosts from running.
The reporting is pretty terrible, I'm not sure what file it is trying to
find. The only thing in the logs is the audit lines.
Removing those /etc/apparmor.d/libvirt/libvirt* files fixed the problem
I susp
5 matches
Mail list logo
