All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Kevin O'Connor <kevin@koconnor.net>, beth kon <eak@us.ibm.com>,
	Avi Kivity <avi@redhat.com>, Gleb Natapov <gleb@redhat.com>
Subject: [Qemu-devel] PC machine types switched to SeaBIOS/gPXE
Date: Fri, 30 Oct 2009 09:54:49 -0500	[thread overview]
Message-ID: <4AEAFE39.1030302@us.ibm.com> (raw)

Hi,

I just wanted to let everyone know that I've switched the PC machine 
type to SeaBIOS and gPXE.  SeaBIOS is a port of the Bochs BIOS to GCC, 
by Kevin O'Conner, along with quite a lot of clean up and new feature work.

gPXE is the new development tree of etherboot which is now deprecated.  
We've done a lot of testing of and while there are a few outstanding 
issues, almost everything seems to be working okay.

Some known issues:
 o e1000 pxe booting doesn't seem to work
 o gPXE does not like the slirp tftp server
 o SeaBIOS doesn't support CPU hotplug (not an issue for upstream qemu)

I've renamed the old pcbios to pcbios.bin.  If you suspect a bug in 
SeaBIOS, you can use "-bios pcbios.bin" to try with the old BIOS in an 
effort to debug.

I want to thank everyone who helped make this all happen.  It was a big 
effort and I think it's going to be a really nice feature for the 0.12.0 
release!

-- 
Regards,

Anthony Liguori

             reply	other threads:[~2009-10-30 14:55 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-30 14:54 Anthony Liguori [this message]
2009-10-30 19:37 ` [Qemu-devel] Re: PC machine types switched to SeaBIOS/gPXE Jan Kiszka
2009-10-30 19:45   ` Anthony Liguori
2009-10-31 12:42     ` Stefan Weil
2009-10-31 13:10       ` Jan Kiszka
2009-11-02 23:09         ` Beth Kon
2009-11-02 23:22           ` Anthony Liguori
2009-11-03  4:16             ` Kevin O'Connor
2009-11-03 14:11               ` Beth Kon
2009-11-04  1:38                 ` Kevin O'Connor
2009-11-04  1:55                   ` Anthony Liguori
2009-10-31 11:07 ` [Qemu-devel] " Stefan Weil
2009-10-31 12:02   ` [Qemu-devel] " Jan Kiszka
2009-11-02 12:51 ` [Qemu-devel] " Alexander Graf
2009-11-02 13:08   ` Avi Kivity
2009-11-02 13:15     ` Alexander Graf
2009-11-02 13:32       ` Avi Kivity
2009-11-02 13:51         ` Kevin O'Connor
2009-11-02 13:56           ` Avi Kivity
2009-11-02 14:06             ` Alexander Graf
2009-11-02 14:39               ` Avi Kivity
2009-11-09 18:41               ` Glauber Costa
2009-11-10 13:02                 ` Avi Kivity
2009-11-10 13:03                   ` Alexander Graf
2009-11-10 13:07                     ` Avi Kivity
2009-11-10 13:09                       ` Alexander Graf
2009-11-03  4:50             ` Kevin O'Connor
2009-11-03  4:57               ` Alexander Graf
2009-11-03  5:01                 ` Avi Kivity
2009-11-03  6:02                   ` Kevin O'Connor
2009-11-03  6:08                     ` Avi Kivity
2009-11-03 13:42                       ` Kevin O'Connor
2009-11-03  4:58               ` Avi Kivity
2009-11-02 14:51   ` Gleb Natapov
2009-11-02 14:54     ` Gleb Natapov

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=4AEAFE39.1030302@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=eak@us.ibm.com \
    --cc=gleb@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.