Hi Stephen,
it would be useful to hear what release you are on going further.
But we didn't have an apparmor change in libvirt/qemu that puts on more
restrictions in any release, but maybe a side effect of somthing else?
I quickly retries and on all of my systems but can still start guests on
all of those.
The apparmor profile is generated based on your guest xml, and will be in
/etc/apparmor.d/libvirt/libvirt-<uuid of guest>.files
Usually disk entries in that file are added as rules, so I'd like to see the
xml and profile to check if something is missing.
Questions:
1. what Ubuntu release are you on
2. what is the version of your libvirt and qemu packages
3. could you share your guest xml (virsh dumpxml <guestname>)
4. could you share the generated apparmor profile (virsh dominfo to get the
uuid, then check the file path)
With those we might find what is going on.
** 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/1772936
Title:
Apparmor enforcment blocks image permissions in libvirtd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1772936/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
