[Bug 1632875] Re: qemu-efi built w/ gcc-6 doesn't boot in KVM mode

Launchpad Bug Tracker 1632875 at bugs.launchpad.net
Mon Oct 24 18:53:36 UTC 2016


This bug was fixed in the package edk2 - 0~20160813.de74668f-2

---------------
edk2 (0~20160813.de74668f-2) unstable; urgency=medium

  [ dann frazier ]
  * d/p/arm64-reorder-blocks-algorithm.diff: Workaround to fix
    booting in KVM mode. LP: #1632875.
  * debian/rules: Export compiler prefix variable to simplify
    build-qemu-efi target.
  * debian/rules: Make the target dependencies on setup-build explicit.
  * debian/rules: Set the aarch64 toolchain prefix agnostically of the
    toolchain tag being used.
  * debian/rules: Respect EDK2_TOOLCHAIN tag when building ovmf.

 -- Steve Langasek <vorlon at debian.org>  Wed, 19 Oct 2016 13:07:08 -0700

** Changed in: edk2 (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gcc-6 in Ubuntu.
https://bugs.launchpad.net/bugs/1632875

Title:
  qemu-efi built w/ gcc-6 doesn't boot in KVM mode

Status in edk2 package in Ubuntu:
  Fix Released
Status in gcc-6 package in Ubuntu:
  New
Status in edk2 source package in Yakkety:
  Triaged
Status in gcc-6 source package in Yakkety:
  New

Bug description:
  qemu-efi_0~20160813.de74668f-1 hangs when booting it in QEMU under
  KVM, though it does seem to work OK when running fully emulated.

  
  $ cp /usr/share/AAVMF/AAVMF_*.fd /tmp
  $ sudo qemu-system-aarch64 -enable-kvm -m 2048 -cpu host -M virt,gic_version=host -nographic -pflash /tmp/AAVMF_CODE.fd -pflash /tmp/AAVMF_VARS.fd
  WARNING: Image format was not specified for '/tmp/AAVMF_CODE.fd' and probing guessed raw.
           Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
           Specify the 'raw' format explicitly to remove the restrictions.
  WARNING: Image format was not specified for '/tmp/AAVMF_VARS.fd' and probing guessed raw.
           Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
           Specify the 'raw' format explicitly to remove the restrictions.
  [hang]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1632875/+subscriptions



More information about the foundations-bugs mailing list