New comment by sernkut on void-packages repository

https://github.com/void-linux/void-packages/issues/31904#issuecomment-901483813

Comment:
This is caused by `virt-aa-manager` as it's trying to automatically generate the AppArmor profile on VM startup.  
`virt-aa-manager` disallows some paths in generated AppArmor profiles which can be found here [`src/security/virt-aa-helper.c:454-490:valid_path()`](https://github.com/libvirt/libvirt/blob/master/src/security/virt-aa-helper.c#L454-L490)  

I fixed this for the `edk2-x86_64-code.fd` firmware image  by copying the executable and nvram-template files referenced in `/usr/share/qemu/firmware/60-edk2-x86_64.json` to `/usr/share/ovmf`.  
I then made a copy of `60-edk2-x86_64.json` with some other name like: `60-edk2-x86_64-custom.json` and updated the file paths in this copied file to reference the ones in `/usr/share/ovmf`.  
  
Also i am sorry for creating a extra issue.  
  
Edit: Make soulution more clear