Hi,
thanks for the information. The apparmor files do look correct. To be
sure, those came from the compute node (the remote server), not from the
client, right?
Does logging into the server and typing 'virsh destroy <vm-name>' also
fail? (I assume so)
All I can figure is that for some reason (a bug in apparmor or the
kernel) the running vm's policy did not get updated when the included
file in the apparmor policy was updated. Is it possible to reboot the
server, start the VM, and confirm whether stop works then?
** Changed in: virt-manager (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/1324393
Title:
"Force off" fails with "Permission denied" after upgrading to 14.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1324393/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
