[Qemu-devel] [Bug 1835793] Re: Running an edk2 based bios

[Peter Maydell]

"Guest has not initialized display" simply means that the guest code
you're running has not done anything to the display device (VGA in this
case). There are two main reasons for this:

 (1) the guest code isn't intended to output to the display -- perhaps
it sends its output to the serial port instead. In this case the fix is
to use the right QEMU arguments to send the serial port output somewhere
you can read it (or to reconfigure the guest code to output where you
want it to).

 (2) the guest code is intended to output to the display, but it crashed
before it got as far as doing that. In this case, the fix is to debug
your guest code. QEMU's gdbstub is usually a good tool to use here. If
you control the guest code (ie you can modify and recompile it) you can
also add extra debugging to it (like making it output more information
earlier, or output debugging trace information to the serial port so you
can see how far it has got).

My guess would be that this is a variation on 2 caused by your BIOS
being compiled to assume different hardware from what QEMU is providing
-- if the BIOS tries to write to a device that isn't present it will
likely crash or go into an infinite loop.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1835793

Title:
  Running an edk2 based bios

Status in QEMU:
  New

Bug description:
  This is not necessarily a bug, however I wasn't sure were to get help.

  I am currently working on using QEMU  to run a BIOS my company has
  developed. In order to see if the software was working correctly, I
  was able to successfully run the edk2 bios using the following
  command:

  qemu-system-x86_64.exe -bios
  "C:\Users\matthew.intriago\Desktop\ovmf.fd" -net none

  However, when running the same command using  our personalized bios,
  QEMU launches stating that “guest has not initialized display”.
  Theoretically, QEMU should be able to run the bios since it is edk2
  based, the only difference between the two is that our bios has more
  features.

  If anyone has any insight on what the issue might be I would greatly
  appreciate any help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1835793/+subscriptions