qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jordan Justen <jljusten@gmail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] pc.c: Add UEFI IA32 & X64 machine types.
Date: Mon, 10 Aug 2009 12:33:27 -0700	[thread overview]
Message-ID: <2a50f7880908101233x6d714803x8b59edce805f9253@mail.gmail.com> (raw)
In-Reply-To: <4A806C86.6030504@codemonkey.ws>

On Mon, Aug 10, 2009 at 11:52 AM, Anthony Liguori<anthony@codemonkey.ws> wrote:
> Jordan Justen wrote:
>>
>> For i386, this change adds a 'uefi' machine type.  For x86_64, this
>> change adds 'uefi' and 'uefi32' machine types.
>>
>
> Why are uefi32 machines explicitly needed?

In UEFI systems, the OS architecture is assumed to be the same as the
firmware architecture.  So, when booting a 32-bit x86 UEFI OS, you
need to use a firmware that runs in 32-bit mode.

So, you could either run the 32-bit qemu:
$ qemu -M uefi
or, achieve similar results from the x86_64 qemu:
$ qemu-system-x86_64 -M uefi32

I am not sure if this is desirable for qemu in general, but I often
test the 32-bit OVMF via qemu-system-x86_64.

> How does one build the uefi roms?

I work for Intel on the OVMF project, which supports UEFI for qemu:
* https://edk2.tianocore.org/OVMF.html
(Currently this project is considered at an alpha stage.)

It is not a trivial process to build OVMF, but it can be done on
Linux, OS X or Windows.  This page is a decent starting point, but it
will call out from pre-requisite setup instructions from other web
pages.
* https://edk2.tianocore.org/build-ovmf.html

Also, binary builds are available at:
* https://edk2.tianocore.org/servlets/ProjectDocumentList?folderID=101

> Is uefi all that useful in the absence of a CSM?  Wouldn't it make more
> sense to add a CSM to uefi and then switch the default pc to use uefi?

CSM is an interface that layers on top of a UEFI firmware to provide
legacy BIOS support.

Considering that UEFI is attempting to replace the legacy BIOS
interfaces with non-legacy interfaces, obviously it should be useful
without a CSM. :)  You can boot a UEFI OS without a CSM, and I have
been making good progress on booting Fedora 11 (UEFI) on qemu with
OVMF.

---

Regarding CSM, I have a few more points, but I should mention that
these might involve my personal opinions, and not represent Intel...

Firstly, I don't think there is an open-source CSM available.  I think
tianocore.org could benefit from an open source CSM, even if it was
limited compared to other commercial CSM offerings.

I think something like a bochs BIOS based CSM is definitely possible.
But since I think the bochs BIOS is GPL licensed, it would more
difficult for us to use it on tianocore.org, since we try to stick
with BSD licensed code.

>
>> These machine types will load different bios and video bios images:
>>
>
> Regards,
>
> Anthony Liguori
>

      reply	other threads:[~2009-08-10 19:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-09  1:43 [Qemu-devel] [PATCH] pc.c: Add UEFI IA32 & X64 machine types Jordan Justen
2009-08-10 18:52 ` Anthony Liguori
2009-08-10 19:33   ` Jordan Justen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2a50f7880908101233x6d714803x8b59edce805f9253@mail.gmail.com \
    --to=jljusten@gmail.com \
    --cc=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).