Comment 28 for bug 799997
Revision history for this message
| Michael Cook (michaelcook-mjc) wrote Re: error happen when using virsh to start a vm " internal error cannot generate AppArmor profile" | #28 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
FWIW I ran into this error when I changed a KVM guest name from "kvm-4.0" to "kvm-4.0 (new)" in the xml file and performed a virsh define. The naming convention is enforced in Virt Manager (no brackets or special symbols). There seems to be no checking on virsh define from the cmd line. There seems to be some dependency (at least with apparmour) on name format.
I returned the name of the machine back to the original "kvm-4.0" and it runs fine. I then tried another name "kvm-4.0 test". This failed. I think tried "kvm-4.0.1" this worked. I dont have time to try out more variations on machine name but it may help this investigation. (I did not look for or change apparmour profiles, I did try removing and re-adding disk images but this made no difference. I also created a new machine via the Virt Manager UI and this made no difference.).