[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] Xen PXE solution
- To: "Andrew D. Ball" <aball@xxxxxxxxxx>
- From: "Ben Thomas" <ben@xxxxxxxxxxxxxxx>
- Date: Tue, 1 Aug 2006 09:20:36 -0400
- Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
- Delivery-date: Tue, 01 Aug 2006 06:21:00 -0700
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=oaoi6F5xRhY273Axg+lFoQcpWnr97dIGBgHwi+2hwNGcDqlnf4QGv5BvzldGYLLLKwDXXQpobywlLwJeqo/RBzbGMmvnUWDdG5gXLkQxic5SgH59g1H6U2Cz8ZtcXEdGofNer5pLGvcKm25hkfkpovG3eNPCpiO8RMcsW1Y2WAI=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Hi Andrew,
For what it's worth, we've been using a PXE solution based upon
etherboot. It's effectively a floppy-like boot image that works
quite well. My memory is that there were some instruction
decode/emulation issues on VMX, but that we've submitted all of those
patches to this list. I believe that they were incorporated into
xen-unstable.
This approach has been working quite well for us for a while now, but may not completely address all of your needs.
fwiw,
-b
On 7/31/06, Andrew D. Ball <aball@xxxxxxxxxx> wrote:
Greetings.
I've been asked to work on a PXE solution for booting Xen domU's from a
network, and would like some feedback and any help anyone is willing to
provide.
I've been limiting my work to HVM domU's at the moment, because I don't
think the NBI's (as far as I know, these are bootloaders) that I have
available work in paravirtualized domU's. Something build around the
Linux kernel and kexec would be really cool for paravirtualized domU's.
So, I'd like to know if something like the PXE ROM's that come on most
servers nowadays would be more useful than doing something like booting
from PXE client ISO image. Ideally, I think the configuration may look
something like this:
(device
(vif
(bridge xenbr0) (mac 00:16:3e:00:00:11) (type ioemu)
(pxe true)
)
)
Then, I'm thinking the behavior would be to boot PXE on that NIC by
default, then try other boot devices. Of course, the 'boot' option that
currently accepts 'a','b', or 'c' could include pxe as an option, but
it's unclear to me which order the NICs would try to boot in. Maybe all
of the NICs with PXE ROMs in configuration order.
It looks like Etherboot
5.4.2 has at least the beginnings of full PXE
support for some drivers. AMD pcnet32 looked okay, but I don't have a
really demanding PXE environment for testing.
Many thanks for your help!
Andrew
=====
Andrew D. Ball <aball@us dot ibm dot com>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
