** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1809488
Title:
armhf guests fail to boot in EFI mode
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
Fix Released
Bug description:
[Impact]
The fix for bug 1786878 introduced a regression that causes armhf guest
booted in EFI mode to panic.
[Test Case]
Boot an armhf guest in EFI mode. Here's how I do that on an arm64 box that
supports AArch32:
sudo qemu-system-aarch64 -enable-kvm -M virt,gic_version=host -smp 7
-m 2048 -cpu host,aarch64=off -nographic -pflash AAVMF32_CODE.fd
-pflash AAVMF32_VARS.fd -drive if=none,file=bionic-server-cloudimg-
armhf.img,id=hd0 -device virtio-blk-device,drive=hd0 -drive
if=none,file=my-seed.img,id=hd1 -device virtio-blk-
device,drive=hd1 -drive if=none,file=debian.img,id=hd3 -device virtio-
blk-device,drive=hd3 -netdev type=tap,id=net0 -device virtio-
net-device,netdev=net0,mac=<REDACTED>
[Fix]
33412b8673135 efi/arm: Revert deferred unmap of early memmap mapping
[Regression Risk]
This change is specific to efi/arm, which currently doesn't boot. The
reverted change was to allow for ACPI BGRT code, which isn't supported on
32-bit ARM.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809488/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
