No, I believe that is spurious. According to the message in the Description, I believe that the failure happens when the apparmor profile fails to be generated on the compute node. I believe that if adding kvm-spice sometimes seemed to fix it, that was an accident.
To check whether I'm right, can you take a vm which does work, remove the kvm-spice line, and check that it now indeed fails to start? -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
