qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Jordan Justen <jljusten@gmail.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	Bei Guan <gbtju85@gmail.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Does any version of QEMU support EFI?
Date: Sat, 19 Mar 2011 15:58:52 -0500	[thread overview]
Message-ID: <4D85190C.2040800@codemonkey.ws> (raw)
In-Reply-To: <AANLkTikJVrC0L3oSMrWwZz_u2MK_hLos9VdpYYSkF702@mail.gmail.com>

On 03/19/2011 02:50 PM, Jordan Justen wrote:
> On Sat, Mar 19, 2011 at 08:36, Bei Guan<gbtju85@gmail.com>  wrote:
>> Does QEMU have the plan to ship with EFI firmware?
> Hi.  I work on the OVMF project which Stefan mentioned.  I definitely
> can't speak for the qemu/kvm project, but I'll give my impressions
> from my OVMF perspective.
>
> I think qemu/kvm has some interest in supporting UEFI, but they are
> (understandably) concerned about losing legacy bios compatibility.
> Additionally, they do not want the user to have to choose between a
> legacy boot rom and a UEFI boot rom before starting the VM.

It's not just whether the user has to choose.  It's the testing 
associated with having two different firmware paths in the tree.  If we 
had UEFI as a secondary option, 99% of users would never use it so it 
would bit rot very quickly.

With a CSM, UEFI can become part of the standard path such that 100% of 
users are actually testing UEFI.  That's really what our goal is.

Regards,

Anthony Liguori

      reply	other threads:[~2011-03-19 20:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-19  9:53 [Qemu-devel] Does any version of QEMU support EFI? Bei Guan
2011-03-19 14:09 ` Stefan Hajnoczi
2011-03-19 15:36   ` Bei Guan
2011-03-19 19:50     ` Jordan Justen
2011-03-19 20:58       ` Anthony Liguori [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=4D85190C.2040800@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=gbtju85@gmail.com \
    --cc=jljusten@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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).