Christian Thanks again for your help. Sorry for the delay on this. So a simple test of apparmor=0 on the kernel command line resolved the issue.
> You can either try to consume it via libvirt xml entries (but I assume you > need the nvme > type configs that libvirt doesn't expose yet) Correct, I need the use_cmb_mb entry in the NVMe drive type and libvirt has no support for that. > any similar pattern by modifying /etc/apparmor.d/abstractions/libvirt- qemu and adding a rule. This worked. > I really doubt this can be update related, as the same would not have worked > since > libvirt/qemu have apparmor support, which seems like a decade ago. I did have this working before but perhaps apparmor had been disabled (by me) and then re-enabled. Anyway I can't reproduce it so I suggest we close for now. Cheers Stephen -- 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
