Hi, This short series fixes two AppArmor denials that stop <interface> devices using <backend type='passt'/> from working when libvirt confines QEMU with AppArmor. Both changes are in src/security/apparmor/libvirt-qemu. Patch 1: Allow passt to mmap its own binary. Once libvirt runs passt, it transitions into the "passt" subprofile. That subprofile only grants 'r' on /usr/bin/passt, but the binary also has to be memory-mapped. AppArmor mediates this with 'm', so passt was denied (operation="file_mmap", requested_mask="rm") and the interface could not be set up. The patch changes the rule to 'rm'. Patch 2: Allow QEMU to access the passt socket. passt creates its unix socket (path from qemuPasstCreateSocketPath()) under /run/libvirt/qemu/passt/. The "passt" subprofile lets passt create it, but the libvirt-qemu profile did not let QEMU connect to it. QEMU was denied 'wr' on /run/libvirt/qemu/passt/*.socket. The patch adds "/run/libvirt/qemu/passt/*.socket rw," to the main profile. Together, the two patches let a VM with a passt-backed network device start under AppArmor. Hector Cao (2): apparmor: Allow passt to mmap its own binary apparmor: Allow QEMU to access the passt socket src/security/apparmor/libvirt-qemu | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) -- 2.53.0