From: "Andrew D. Ball" <aball@us.ibm.com>
To: Jeremy Katz <katzj@redhat.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen PXE solution
Date: Wed, 02 Aug 2006 09:54:40 -0400 [thread overview]
Message-ID: <1154526880.7786.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1154522529.20100.15.camel@aglarond.local>
As far as I know, the boot order option only accepts one of
{'a','b','c'}. I more descriptive list like you suggested would be
much, much better.
Peace.
Andrew
On Wed, 2006-08-02 at 08:42 -0400, Jeremy Katz wrote:
> On Mon, 2006-07-31 at 10:57 -0400, Andrew D. Ball wrote:
> > 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.
>
> Cool
>
> > 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.
>
> HVM is definitely the first step here.
>
> > 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:
>
> *nod* So are you looking at integrating into the rombios?
>
> > (device
> > (vif
> > (bridge xenbr0) (mac 00:16:3e:00:00:11) (type ioemu)
> > (pxe true)
> > )
> > )
>
> Quite possibly PXE would even default to 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.
>
> I think it's definitely better to go with pxe as an option to boot and
> then doing the NICs in config order. This matches up with how real
> hardware works[1]
>
> Jeremy
>
> [1] Also -- does anyone know if the boot option currently take multiple
> arguments? I'll have to try when I get to the office. It should be a
> list and fall back through them as things aren't available so that a
> default order of say PXE, CD, HD can be set up and be nice and useful :)
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2006-08-02 13:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 14:57 Xen PXE solution Andrew D. Ball
2006-08-01 13:20 ` Ben Thomas
2006-08-15 18:14 ` Henning Sprang
2006-08-15 18:46 ` Ben Thomas
2006-08-02 12:42 ` Jeremy Katz
2006-08-02 13:54 ` Andrew D. Ball [this message]
[not found] ` <452A380F.BA47.005A.0@novell.com>
2006-10-16 16:23 ` Andrew D. Ball
[not found] ` <a8a6bd980610161046y426cdf0bn64c8181c45fae9dd@mail.gmail.com>
2006-10-16 19:33 ` Andrew D. Ball
2006-10-16 19:47 ` Ben Thomas
-- strict thread matches above, loose matches on Subject: below --
2006-08-01 11:34 Ian Pratt
2006-08-15 18:24 Ian Pratt
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=1154526880.7786.2.camel@localhost.localdomain \
--to=aball@us.ibm.com \
--cc=katzj@redhat.com \
--cc=xen-devel@lists.xensource.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 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.