Comment # 6 on bug 1069562 from Giuseppe Gorgoglione

(In reply to Jiri Slaby from comment #5)
> Yes, that might be it. But the original bug is now fixed.
> 

Actually today, after rebooting, I forgot to stop apparmor service before
starting a virtual machine and I got back a kernel oops once again, even with
updated libvirt.

Rebooting and repeating (including not stopping apparmor) I got no oops and
just the usual error from Virtual Machine Manager. So it's kinda not
deterministic.

> You should create a new one for the apparmor update, if there is none yet.

I'll do that.

Thanks.