qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Jordan Justen <jljusten@gmail.com>
Cc: Gleb Natapov <gleb@redhat.com>,
	Kevin O'Connor <kevin@koconnor.net>,
	qemu-devel <qemu-devel@nongnu.org>,
	Michal Suchanek <hramrach@centrum.cz>,
	Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] OVMF Google Summer of Code ideas
Date: Tue, 8 Mar 2011 07:18:09 +0000	[thread overview]
Message-ID: <AANLkTinMGXaAi95PC9V+2x9N6j6JMmxH17OKTEoc88zi@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinRqfzYto4eYBzc3CADE_9JBii_H7FWZ8Sg-g+8@mail.gmail.com>

On Tue, Mar 8, 2011 at 12:54 AM, Jordan Justen <jljusten@gmail.com> wrote:
> On Mon, Mar 7, 2011 at 01:48, Stefan Hajnoczi <stefanha@gmail.com> wrote:
>> Jordan, UEFI guest firmware comes up periodically.  It seems to be a
>> feature that will be required in the future but as of today I don't
>> know of QEMU developers who are working on or using it.
>>
>> Maybe you can start by giving an update on where OVMF stands today,
>> what the roadmap is, and where collaboration/integration with QEMU is
>> necessary?
>
> The status today is that we can boot UEFI Linux with qemu or kvm on
> IA-32 & X64 pretty reliably.
>
> The biggest issue for UEFI Linux seems to be getting distributions to
> ship UEFI compatible ISO images.  However, there seems to be some
> progress here.  For instance 64-bit Ubuntu 10.10's ISO is UEFI
> bootable.
>
> UEFI Windows 7 still does not boot on OVMF, and this is still a big open issue.
>
> One other OVMF issue that requires some help on the VM side is that we
> cannot support true non-volatile variables in OVMF due to a lack of
> flash support in QEMU/KVM.
>
> The biggest issue that you guys care about for OVMF is a lack of
> legacy bios compatibility (CSM).  There has been no progress in this
> area.  (However, it has now been suggested by someone on our dev list
> for a potential Google Summer of Code project.  We will have to see if
> anything comes of this...)

That would be cool.  Is there a way to just embed SeaBIOS?  Or do the
UEFI APIs still need to be around when CSM kicks in?

> In terms of a forward looking 'roadmap,' I'm sure that the UEFI Linux
> situation should only improve as more and more x86/x86-64 systems are
> shipped with UEFI available.  We will continue to try to improve UEFI
> Linux, and hopefully distributions will be able to leverage OVMF for
> UEFI compatibility testing.
>
> Clearly we hope to resolve the UEFI Win7 boot issue, or possibly
> address UEFI booting with Win8.
>
> Regarding the non-volatile variables issue, I have been trying to
> develop a proposal for addressing this with a change to QEMU's
> hardware support of bios.bin.  But, I don't have the suggestion (or
> implementation) ready at this time.

Sounds like something to keep discussing with the QEMU and SeaBIOS
communities.  Gleb Natapov and Kevin O'Connor have done a lot of the
recent BIOS and firmware interface work.  I think persistent CMOS has
come up several times and might be similar to non-volatile UEFI
storage.

Stefan

  reply	other threads:[~2011-03-08  7:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-06  4:12 [Qemu-devel] OVMF Google Summer of Code ideas Jordan Justen
2011-03-06 15:29 ` Michal Suchanek
2011-03-06 21:15   ` Jordan Justen
2011-03-07  9:48     ` Stefan Hajnoczi
2011-03-08  0:54       ` Jordan Justen
2011-03-08  7:18         ` Stefan Hajnoczi [this message]
2011-03-08  8:26           ` Gleb Natapov
2011-03-08 17:13             ` Jordan Justen
2011-03-09 10:16               ` Gleb Natapov
2011-03-09 18:34                 ` Jordan Justen
2011-03-08 17:00           ` Jordan Justen
2011-03-09  2:23             ` Kevin O'Connor
2011-03-09  5:34               ` Jordan Justen
2011-03-09 13:43                 ` Natalia Portillo
2011-03-09 18:44                   ` Jordan Justen
2011-03-09 23:20                     ` Natalia Portillo
2011-03-07 10:22   ` Peter Maydell

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=AANLkTinMGXaAi95PC9V+2x9N6j6JMmxH17OKTEoc88zi@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=hramrach@centrum.cz \
    --cc=jljusten@gmail.com \
    --cc=kevin@koconnor.net \
    --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).