Re: [libvirt] [PATCH] AppArmor: Allow libvirtd to kill unconfined processes

Hi, On Mon, Jan 15, 2018 at 07:43:56AM +0100, intrigeri wrote: > Christian Ehrhardt: > > I recently had spotted this issue and discussed on IRC but couldn't > > recreate after a while when I wanted to debug. > > I've seen it the last few times I've started libvirtd.service on two > different

Re: [libvirt] [PATCH] AppArmor: Allow libvirtd to kill unconfined processes

Christian Ehrhardt: > I recently had spotted this issue and discussed on IRC but couldn't > recreate after a while when I wanted to debug. I've seen it the last few times I've started libvirtd.service on two different Debian sid ("unstable") systems. > But the reason and the rule totally make

Re: [libvirt] [PATCH] AppArmor: Allow libvirtd to kill unconfined processes

On Sat, Jan 13, 2018 at 9:54 AM, wrote: > From: intrigeri > > On startup libvirtd runs a number of QEMU processes unconfined such as: > > /usr/bin/qemu-system-x86_64 -S -no-user-config -nodefaults -nographic > -machine

[libvirt] [PATCH] AppArmor: Allow libvirtd to kill unconfined processes

From: intrigeri On startup libvirtd runs a number of QEMU processes unconfined such as: /usr/bin/qemu-system-x86_64 -S -no-user-config -nodefaults -nographic -machine none,accel=kvm:tcg -qmp unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait