[Touch-packages] [Bug 1531703] Re: virsh save doesn't work for vm with hdd image in non-default location, AppArmor-related error

2017-06-09 Thread ChristianEhrhardt
** No longer affects: apparmor (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1531703 Title: virsh save doesn't work for vm with hdd image in non-default

[Touch-packages] [Bug 1531703] Re: virsh save doesn't work for vm with hdd image in non-default location, AppArmor-related error

2017-06-08 Thread ChristianEhrhardt
Sorry this has been dormant for way too long, but I can still not reproduce as Serge couldn't back then. To properly reflect that I'm setting incomplete for now. You could try to check what /usr/lib/libvirt/virt-aa-helper does with your XML. Maybe it fails to process it or generates content in

[Touch-packages] [Bug 1531703] Re: virsh save doesn't work for vm with hdd image in non-default location, AppArmor-related error

2016-06-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libvirt (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu.

[Touch-packages] [Bug 1531703] Re: virsh save doesn't work for vm with hdd image in non-default location, AppArmor-related error

2016-06-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu.

[Touch-packages] [Bug 1531703] Re: virsh save doesn't work for vm with hdd image in non-default location, AppArmor-related error

2016-03-15 Thread RussianNeuroMancer
> show something different than the original path? No, only path that represent current image location (inside btrfs snapshot). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu.

[Touch-packages] [Bug 1531703] Re: virsh save doesn't work for vm with hdd image in non-default location, AppArmor-related error

2016-03-11 Thread Serge Hallyn
Thanks, nothing looks out of the ordinary there. Just to make sure, does realpath /mnt/storage/data/images/owncloud.qcow2 show something different than the original path? (I.e. could a path element there be a symlink into one of the restricted paths?) -- You received this bug notification

[Touch-packages] [Bug 1531703] Re: virsh save doesn't work for vm with hdd image in non-default location, AppArmor-related error

2016-03-11 Thread RussianNeuroMancer
This particular VM is removed now (guest moved to nspawn container) but I find xml in host btrfs snapshots. ** Attachment added: "owncloud.xml" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1531703/+attachment/4595747/+files/owncloud.xml ** Changed in: libvirt (Ubuntu)

[Touch-packages] [Bug 1531703] Re: virsh save doesn't work for vm with hdd image in non-default location, AppArmor-related error

2016-03-10 Thread Serge Hallyn
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