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:
/usr/share/AAVMF/AAVMF_VARS.fd
With that you want it to change the systems default template, you should
instead use
/var/lib/libvirt/qemu/
I set up a Xenial on arm64.
I created a working guest like:
b1
1f776433-dc84-43ac-9e60-b8e571ae22ff
https://launchpad.net/uvtool/libvirt/1";>ssh-rsa
B3NzaC1yc2EDAQABAAABAQCWcGghaCsAwBh0VauPNnnRshKfGD6uXqHEQb9djUlSQ/wKjgNCemAamaVTZjHJoT+Q5whAtv0SkRc6Vj9mlODBtBeBPqZS00HbM1TqH6Hk
Hi Newell - Hmm, interesting.
We have
owner @{PROC}/*/auxv r,
for qemu, but never had/needed so for
/etc/apparmor.d/usr.lib.libvirt.virt-aa-helper which your denies are against.
For "myself" IN only resolved arm VMs in Bionic and forward (since I made
uvtool fully work for me on arm), but tog
This is a top-notch bug report! Thanks
--
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:/
