Comment 15 for bug 1719579
Revision history for this message
| Christian Ehrhardt (paelzer) wrote Re: [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save | #15 |
Hi Manoj,
my intention was (unless discussed and outlined to be important to do it otherwise):
18.04 - integrate the upstream changes so that --bypass-cache works
16.04 users using cloud-archive queens will have the same feature
16.04-17.10 and anyone not using bypass-cache will stay as-is I had not planned to backport the code so far.
I haven't checked yet, but assuming the time delta the backport could cause more
issues than it solves.
For the older releases I'd consider it a configuration issue.
If an admin chooses to use an uncommon path (like /var/tmp) then he has to make
it allowed to be accessed in the apparmor profiles.
Get me right I use virsh save/restore on a regular base and it works in the paths that are open by default, which are the places the images usually are from like /var/lib/
If that does not work that might be a modified apparmor rule, but for that I'd need to know way more about the case and see if it is actually a bug or really just using an uncommon dir.
If you want to look into potential config issues, remove the silent denies to /var and /var temp at the end of "/etc/apparmor.
Then run your case again, report back with
a) commands to trigger the issue
b) dmesg while that occurred
None of the latter is needed to get it fixed in 18.04 where I'll make bypass-cache work as suggested by IBM by picking the code changes.