qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com, mcb30@ipxe.org
Subject: Re: [Qemu-devel] [PATCH v2 0/3] pc-bios: Use iPXE ROMs
Date: Mon, 11 Apr 2011 14:10:31 -0600	[thread overview]
Message-ID: <1302552631.3589.86.camel@x201> (raw)
In-Reply-To: <1302551871.3589.83.camel@x201>

On Mon, 2011-04-11 at 13:57 -0600, Alex Williamson wrote:
> On Mon, 2011-04-11 at 14:48 -0500, Anthony Liguori wrote:
> > On 04/11/2011 02:35 PM, Alex Williamson wrote:
> > > This series replaces our current gPXE based PXE ROMs with iPXE
> > > versions from the iPXE project (http://ipxe.org).  This version
> > > adds ipxe to our submodules so it can be easily included in
> > > releases.  I'm still including a script for updating these,
> > > perhaps someone better with Makefiles can eventually adopt this
> > > to a build target.
> > >
> > > This email series is mainly for reference, there's too much
> > > renaming and replacing binary files to send out to the mailing
> > > list.  I'll strip out the binaries here so the rest can be
> > > reviewed.  For the real code, please pull:
> > >
> > > git://github.com/awilliam/qemu.git (ipxe branch)
> > >
> > > Thanks to Anthony for already setting up an ipxe mirror.
> > > Thanks,
> > 
> > Looks good to me.  How different is this from what we've been shipping?  
> > Have you tested PXE boot from the builtin TFTP server and from an 
> > external one (like dnsmasq)?
> 
> We were shipping v0.9.9, which was tagged 10/2009.  There's been a gpxe
> v1.0.0 release since then, plus the split between ipxe and gpxe.  I
> think Michael is hoping to have a release soon, but the code feels
> pretty stable to me as is.
> 
> I've tested external booting from dhcp/tftp server for all the NICs.
> I'll make a pass through testing with the builtin server and report
> back.  Thanks,

Check, tested virtio-net-pci, e1000, rtl8139, ne2k_pci, pcnet, and
i82550 using builtin server, with bootfile and tftp loaded
kernel/initrd.  All work.  Thanks,

Alex

  reply	other threads:[~2011-04-12  1:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11 19:35 [Qemu-devel] [PATCH v2 0/3] pc-bios: Use iPXE ROMs Alex Williamson
2011-04-11 19:36 ` [Qemu-devel] [PATCH v2 1/3] Add ipxe submodule Alex Williamson
2011-04-11 19:37 ` [Qemu-devel] [PATCH v2 2/3] PXE: Use consistent naming for PXE ROMs Alex Williamson
2011-04-11 19:38 ` [Qemu-devel] [PATCH v2 3/3] PXE: Refresh all PXE ROMs from the ipxe submodule Alex Williamson
2011-04-11 19:48 ` [Qemu-devel] [PATCH v2 0/3] pc-bios: Use iPXE ROMs Anthony Liguori
2011-04-11 19:57   ` Alex Williamson
2011-04-11 20:10     ` Alex Williamson [this message]
2011-04-12  9:38       ` Stefan Hajnoczi
2011-04-18 17:25     ` Alex Williamson
2011-04-18 17:34       ` Anthony Liguori
2011-04-18 20:43         ` Stefan Weil
2011-04-11 21:13 ` Stefan Weil
2011-04-11 21:26   ` Alex Williamson

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=1302552631.3589.86.camel@x201 \
    --to=alex.williamson@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=mcb30@ipxe.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.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).