Public bug reported:
[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.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Cosmic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Disco)
Importance: Undecided
Status: Fix Released
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu Disco)
Assignee: dann frazier (dannf) => (unassigned)
** Changed in: linux (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Cosmic)
Assignee: (unassigned) => dann frazier (dannf)
** Description changed:
[Impact]
- Booting an armhf guest in EFI mode results in a panic.
+ 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 is a regression fix.
+ 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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809488
Title:
armhf guests fail to boot in EFI mode
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809488/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
