Description of problem: Cannot restart saved QEMU domain under (default) apparmour security container. The app-armor profiles are present and loadable --- Console --- virsh # managedsave Win7 Domain Win7 state saved by libvirt virsh # start Win7 error: Failed to start domain Win7 error: internal error: cannot load AppArmor profile 'libvirt-230df182-437a-457a-bd9c-62819ff24929' uk-lc13-lab:~>ls /etc/apparmor.d/libvirt/libvirt-230df182-437a-457a-bd9c-62819ff24929* /etc/apparmor.d/libvirt/libvirt-230df182-437a-457a-bd9c-62819ff24929 /etc/apparmor.d/libvirt/libvirt-230df182-437a-457a-bd9c-62819ff24929.files uk-lc13-lab:~>aa-exec -f /etc/apparmor.d/libvirt/libvirt-230df182-437a-457a-bd9c-62819ff24929 date Wed Jul 16 10:52:42 BST 2014 --- END --- Version-Release number of selected component (if applicable): 1.2.2 How reproducible: Always Steps to Reproduce: 1.virsh managedsave <domain> 2.virsh start <domain> 3. Actual results: Domain fails to start Expected results: Domain restarts from the saved state. Additional info: apparmor version 2.8.95 Ubuntu 14.04 with kernel 3.15.3-031503-lowlatency Disk volume is on ZFS.
I have the same issue. Mine is on an ext4 volume. I saw some people mentioning that a space in the name might be an issue. I tried to add the profile manually and set the apparmor policy to just alarm, but keep getting the error.
Sorry this didn't receive a timely response. Is anyone still seeing this with a more recent distro and libvirt version?
Since there's no response, closing as DEFERRED. But if anyone is still affected with newer libvirt versions, please re-open and we can triage from there