Hi Sasa, I'm not aware of the new need for NFS 3->4 itself, but it could be related to qemu now requiring to lock the file (https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1716028). Eventually that is a function that users want thou to avoid data corruption. It is a useful info that bumping the NFS version helped your case - thanks!
Qemu/Libvirt always restricted the paths that you could use for images. At the start of your guest virt-aa-helper parses the guest XML and creates custom per-guest apparmor rules. For safety that allows only to scan a certain set of directories and further ones need to be added. And the default rule is actually very very deliberate already. If you look in /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper there are certain paths it can real all files from and certain file suffixes it can read from anywhere. Now in your case: /mnt/storage/docker/ isn't a path it can read everything and: *.ign isn't a suffix it can read from everywhere. If instead of /etc/apparmor.d/abstractions/libvirt-qemu you add your rule to /etc/apparmor.d/local/usr.lib.libvirt.virt-aa-helper that would have multiple benefits: 1. only a guest configured for a given disk in that path can eventually access it (isolation) 2. this is a local override meant to survive package upgrades while the place you chose might be overwritten (or at least prompt for a config change) on a later upgrade More Detail at: https://wiki.ubuntu.com/LibvirtApparmor#Using_uncommon_paths I can't really see how this ever would have worked without a rule on 16.04 - was there anything else different like mount paths or anything? If you have more info abotu that we might be able to find what was different/special on your 16.04 and think about it from there. For the 18.04 behavior for now - that seems exactly as it should be. Setting incomplete until further info was provided. ** Changed in: libvirt (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/1866175 Title: Can't create virtual disk or start virtual machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1866175/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
