On ARM, accelerated guests have the host interrupt controller somewhat
"passed through". I say that while vigorously waving my hands because I
don't recall the details well - but I do know that we needed to teach
the entire stack (host kernel -> QEMU -> edk2) about GICv3 and that was
new in the xenial release. AIUI, the existing hosts in ScalingStack
would've been X-Gene w/ older GICv2m controllers. I suspect the root
cause of these issues lie somewhere in the GICv3 support in QEMU and/or
edk2 - see bug 1675522 for a similar report. I'd definitely suggest
upgrading to >= bionic if possible. Or, if not, maybe consider enabling
the cloud archive to get a newer virt stack. If neither is possible, we
could also of course try and bisect down the fixes for the xenial stack
and try and SRU them back - but that will certainly take some time.
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926955
Title:
[VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception
at 0x000000009BC11F38"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1926955/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
