From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=45709 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PwrBL-0000d6-AP for qemu-devel@nongnu.org; Tue, 08 Mar 2011 02:18:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PwrBK-0001Mu-4s for qemu-devel@nongnu.org; Tue, 08 Mar 2011 02:18:11 -0500 Received: from mail-yx0-f173.google.com ([209.85.213.173]:51996) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PwrBK-0001Mq-01 for qemu-devel@nongnu.org; Tue, 08 Mar 2011 02:18:10 -0500 Received: by yxk8 with SMTP id 8so2370552yxk.4 for ; Mon, 07 Mar 2011 23:18:09 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: Date: Tue, 8 Mar 2011 07:18:09 +0000 Message-ID: Subject: Re: [Qemu-devel] OVMF Google Summer of Code ideas From: Stefan Hajnoczi Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jordan Justen Cc: Gleb Natapov , Kevin O'Connor , qemu-devel , Michal Suchanek , Avi Kivity On Tue, Mar 8, 2011 at 12:54 AM, Jordan Justen wrote: > On Mon, Mar 7, 2011 at 01:48, Stefan Hajnoczi wrote: >> Jordan, UEFI guest firmware comes up periodically. =A0It 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. =A0However, there seems to be some > progress here. =A0For 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). =A0There has been no progress in this > area. =A0(However, it has now been suggested by someone on our dev list > for a potential Google Summer of Code project. =A0We 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. =A0We 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. =A0But, 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