Dear Maintainer,

A few moving parts here. My setup:
1. Running through virt-manager.
2. Set up virtiofs to mount $USER/folder/shared-folder in the VM
3. I think all other settings are out-of-the-box

Until 12 August, my VM was working on Debian testing. It broke when I updated
to 12.6. I started getting these errors:
```
libvirtd[12345]: Unable to read from monitor: Connection reset by peer
libvirtd[12345]: internal error: QEMU unexpectedly closed the monitor (vm='my-
vm'): 2026-08-15T05:00:00.195923Z qemu-system-x86_64: -device {"driver":"vhost-
user-fs-pci","id":"fs0","chardev":"chr-vu-fs0","tag":"shared-
folder","bus":"pci.7","addr":"0x0"}: Failed to read msg header. Read 0 instead
of 12. Original request 0.
        2026-08-15T05:00:00.196451Z qemu-system-x86_64: -device
{"driver":"vhost-user-fs-pci","id":"fs0","chardev":"chr-vu-fs0","tag":"shared-
folder","bus":"pci.7","addr":"0x0"}: vhost_backend_init failed: Protocol error
```
It appears that AppArmor started applying strict seccomp rules that caused the
VM to crash. The workaround was to create a wrapper script
/usr/local/bin/virtiofsd_no_seccomp.sh:
```
exec /usr/libexec/virtiofsd --seccomp=none "$@"
```
and add it to the VM's filesystem:
```
<filesystem type="mount" accessmode="passthrough">
  <driver type="virtiofs"/>
  <binary path="/usr/local/bin/virtiofsd_no_seccomp.sh"/>
  <source dir="/home/me/folder/shared-folder"/>
  <target dir="shared-folder"/>
  <alias name="fs0"/>
  <address type="pci" domain="0x0000" bus="0x07" slot="0x00" function="0x0"/>
</filesystem>
```
and compel /etc/apparmor.d/local/usr.sbin.libvirtd to run that:
```
/usr/local/bin/virtiofsd_no_seccomp.sh PUx,
```
I'm guessing my setup is a bit unusual which is why it's causing these errors.
It would be nice if this worked out of the box, but I would also settle for
documentation identifying what's so unique about my setup and the recommended
way to correct it. I'm not sure how resilient these changes are.