We have a few changes, but none of these is "the" issue.
- Cpu features
- cpu model
- emulator without redirect
But I found that your nvram line is wrong:
<nvram>/usr/share/AAVMF/AAVMF_VARS.fd</nvram>
With that you want it to change the systems default template, you should
instead use
<nvram
template='/usr/share/AAVMF/AAVMF_CODE.fd'>/var/lib/libvirt/qemu/nvram/b1_VARS.fd</nvram>
With an individual guest name.
This misconfiguration is the problem that breaks it:
error: internal error: cannot load AppArmor profile
'libvirt-1f776433-dc84-43ac-9e60-b8e571ae22ff'
If anything the message is sort of misleading, but that is another issue
(see bug 1767934 for that).
For this bug here it is just misconfiguration, switching to my
suggestion above avoids the issue and make it work.
Note: The apparmor Deny messages are actually a Red Herring and no more
occurring in later versions.
** Changed in: libvirt (Ubuntu)
Status: New => Invalid
** Changed in: apparmor (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772538
Title:
Can't start arm64 VM due to apparmor error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1772538/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
