Menu

#411 Support for (U)EFI

open
nobody
ROM BIOS (28)
5
2018-02-07
2009-02-10
No

I think (U)EFI support in Bochs would be great to have. Tristan Gingold and whoever else is helping him have made quite some progress and he is actively developing for the implementation for Xen (under either GPL or BSD license, I'm not sure but you can check). In 2007, QEMU put a binary image of Tristan's EFI on their website but a lot has changed since.

Discussion

  • Love4Boobies

    Love4Boobies - 2009-02-10

    I forgot to mention that his latest sources can be found here: http://xenbits.xensource.com/ext/efi-vfirmware.hg

     
  • Stanislav Shwartsman

    What is needed (except the BIOS code of course) to support it ?
    I mean in hardware emulation and infrestructure side.

    Stanislav

     
  • Love4Boobies

    Love4Boobies - 2009-02-10

    My guess is nothing as the only thing QEMU needed was the image itself, I never heard about anyone complaining about adding some hardware support. AFAIK, the EFI does require some specific machine state when it gets control but I guess that's not the case for virtual machines and emulators which only implement the 2nd stage of BIOSes (that is, they don't initialize hardware components such as DRAM through the southbridge, they just provide the necessary services, bootstrapping mechanism and whatever else is visible to the software running on it).

    I might be wrong, however. Someone should really test this before including it in Bochs; unfortunately, I haven't got the time :( Try the latest image from the link I gave you - they also have binaries. At the time of my writing this, the latest image was to be found here: http://xenbits.xensource.com/ext/efi-vfirmware.hg?raw-file/758b47bad60a/binaries/xenia64-gfw.bin (10 days old).

    Bogdan

     
  • Marcel Sondaar

    Marcel Sondaar - 2014-01-07

    ... many years later, having official support would still be nice :)

    Apparently Tristan's UEFI image and bochs don't agree fully, although it does boot into the shell. The console errors that appear are currently:
    00185224644e[DEV ] IO device address conflict(write) at IO address 400h
    00185224644e[DEV ] conflicting devices: Bios Panic Port 1 & ACPI PM base
    00185224644e[DEV ] IO device address conflict(write) at IO address 402h
    00185224644e[DEV ] conflicting devices: Bios Info Port & ACPI PM base
    00229688523e[CMOS ] write to control register 0x0d ignored (read-only)

    The bios images I tested with can be found at: https://sourceforge.net/apps/mediawiki/tianocore/index.php?title=OVMF

    Besides the bios and vga roms, the settings that seem to be needed are:
    vga: extension=cirrus
    i440fxsupport: enabled=1 slot1=cirrus

     
  • secXsQuared

    secXsQuared - 2018-02-07

    Yet many more years later..... having official support would really be nice :)

     

Log in to post a comment.