All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Brady <mike.brady@devnull.net.nz>
To: xen-devel@lists.sourceforge.net
Cc: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
	Ruediger Berlich <ruediger.berlich@iwr.fzk.de>
Subject: Re: Re: PXE boot
Date: Thu, 29 Jul 2004 21:13:43 +1200	[thread overview]
Message-ID: <200407292113.43692.mike.brady@devnull.net.nz> (raw)
In-Reply-To: <E1Bq5PK-0000SI-00@mta1.cl.cam.ac.uk>

I haven't got to it yet, but I was hoping ot use SISuite and/or xCAT to build 
domains somehow.

On Thu, 29 Jul 2004 19:32, Ian Pratt wrote:
> > Hi there,
> >
> > > Xen currently doesn't support booting domains via PXE, though at
> > > some point someone talked about adding it. Basically, the domain
> > > builder would do the PXE request and tftp the kernel image that
> > > would be place in the domain.
> > >
> > > I'm sure you could get the domains booting sans PXE without too
> > > much hassle anyhow.
> >
> > I would assume that it would probably be sufficient to modify the
> > domain builder in a way that, upon request, it executes a script
> > (kind of like a constructor) before the domain starts up. One could do
> > things like setting up a disk image with all needed data (like the kernel
> > image) in that. As everything is physically handled in domain0, this
> > could easily replace  the PXE  boot. And one could of course do many
> > other cool things in such a constructor (and destructor type) script. Or
> > maybe I'm wrong.
>
> The domain's kernel image is placed in memory by the domain
> builder, so doesn't need to come off the domain's virtual disk.
>
> PXE is basically a combination of DHCP and tftp.
>
> We could have the domain builder issue a DHCP request using the
> domain it's building's MAC address, then use tftp to fetch the
> kernel image into a temporary file that the domain builder can
> then use.
>
> Adding support to xend to do this shouldn't be hard. The only
> slightly non trivial bit is sending a DHCP request using someone
> else's MAC -- rather than hacking dhclient it's probably easiest
> to hand craft something one-shot as you don't need a daemon
> (presumably you can rely on the server giving the same address to
> the same MAC if asked in quick succession)
>
> Ian
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click

  reply	other threads:[~2004-07-29  9:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-28 15:04 PXE boot Ruediger Berlich
2004-07-29  0:55 ` Ian Pratt
2004-07-29  1:15   ` Ruediger Berlich
2004-07-29  7:32     ` Ian Pratt
2004-07-29  9:13       ` Mike Brady [this message]
2004-07-29  9:16       ` desperate for help on netwrok of xen Yan Li
2004-07-29  9:21         ` Steven Hand
2004-07-29 10:33           ` Yan Li
2004-07-29 10:52             ` Steven Hand
2004-07-29 10:56               ` Steven Hand
2004-07-29 11:37                 ` Yan Li
2004-07-29 15:30         ` Fredrik Dahlberg
2004-07-29 16:59 ` PXE boot Adam Heath

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=200407292113.43692.mike.brady@devnull.net.nz \
    --to=mike.brady@devnull.net.nz \
    --cc=Ian.Pratt@cl.cam.ac.uk \
    --cc=ruediger.berlich@iwr.fzk.de \
    --cc=xen-devel@lists.sourceforge.net \
    /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.