I found that booting an upstream 4.18 kernel in the guest trips this problem, while an upstream 5.4 does not. I bisected and found that this commit seems to be the relevant change:
commit 3b7142752e4bee153df6db4a76ca104ef0d7c0b4 (refs/bisect/bad) Author: Mark Rutland <[email protected]> Date: Wed Jul 11 14:56:45 2018 +0100 arm64: convert native/compat syscall entry to C Now that the syscall invocation logic is in C, we can migrate the rest of the syscall entry logic over, so that the entry assembly needn't look at the register values at all. The SVE reset across syscall logic now unconditionally clears TIF_SVE, but sve_user_disable() will only write back to CPACR_EL1 when SVE is actually enabled. Signed-off-by: Mark Rutland <[email protected]> Reviewed-by: Catalin Marinas <[email protected]> Reviewed-by: Dave Martin <[email protected]> Cc: Will Deacon <[email protected]> Signed-off-by: Will Deacon <[email protected]> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931728 Title: [scalingstack bos01] bionic (arm64) instances always fail to boot on eMAGs in this cloud To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1931728/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
