Thanks for the information.
Oddly, for the example in comment #4, the apparmor policy *is* in fact
in the listing of /etc/apparmor.d/libvirt.
Are you certain that instance also failed to boot?
I fear the log information will be overwhelming, but i think we'll need
full libvirt debug output. Please edit /etc/libvirt/libvirtd.conf on a
compute node where such a VM is defined (that won't start up), and add
the line
log_level = 1
then "sudo stop libvirt-bin; sudo start libvirt-bin"
and start the vm, then attach the file /var/log/libvirt/libvirtd.log.
** Changed in: libvirt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384532
Title:
libvirt-qemu apparmor profile missing kvm-spice
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1384532/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
