virsh save doesn't work for vm with hdd image in non-default location, AppArmor-related error
Bug #1531703 reported by
RussianNeuroMancer
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libvirt (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
virsh save does work for vm located in /var/lib/
Error message:
~$ LANG=C virsh save owncloud /mnt/storage/
error: Failed to save domain owncloud to /mnt/storage/
error: внутренняя ошибка: не удалось обновить профиль AppArmor «libvirt-
Translation:
error: internal error: unable to update AppArmor profile «libvirt-
I tried to dumpxml and then define it again from xml, but that doesn't help.
Ubuntu Server 15.10.
affects: | apparmor → apparmor (Ubuntu) |
no longer affects: | apparmor (Ubuntu) |
To post a comment you must log in.
Thanks for reporting this bug. I can't reproduce it here:
0 ✓ serge@sl ~ $ virsh start docker
Domain docker started
0 ✓ serge@sl ~ $ virsh save docker /mnt/docker.dmp
Domain docker saved to /mnt/docker.dmp
Same happened on a 15.10 host.
Can you append your full xml?
Normally the apparmor profile messages happen when there is a pathname which confuses virt-aa-helper or libvirt.