From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Brady Subject: Re: Re: PXE boot Date: Thu, 29 Jul 2004 21:13:43 +1200 Sender: xen-devel-admin@lists.sourceforge.net Message-ID: <200407292113.43692.mike.brady@devnull.net.nz> References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Disposition: inline Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: xen-devel@lists.sourceforge.net Cc: Ian Pratt , Ruediger Berlich List-Id: xen-devel@lists.xenproject.org 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