From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kip Macy Subject: Re: Diskless boot at cambridge Date: Thu, 14 Apr 2005 10:51:14 -0700 Message-ID: References: <002701c54118$e4ef3670$b13a6a83@falcon> Reply-To: Kip Macy Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <002701c54118$e4ef3670$b13a6a83@falcon> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: James Bulpin Cc: xen-devel List-Id: xen-devel@lists.xenproject.org > We use either grub with tftp (limited driver support here),=20 I'm having hard time even getting to the GRUB prompt so I don't think that is an option. > or XenoBoot > (now an optional function of the new Xen demo CD).=20 Is that documented anywhere? > We have a fairly > elaborate system involving our lab-wide NFS tree and scripts and > symlinks for getting the right images for each machine.=20 We have innumerable mount points and so use the automounter (which you obviously don't use as it is disabled in the default config). > Root filesystems > for diskless systems are either iSCSI, as previously discussed or NFS. How would you give a machine a unique persistent initiator-name when booting from a general cd? Thanks.=20 -Kip=20 > James >=20 > -----Original Message----- > From: xen-devel-bounces@lists.xensource.com > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Kip Macy > Sent: Thursday, April 14, 2005 6:29 PM > To: xen-devel > Subject: [Xen-devel] Diskless boot at cambridge >=20 > All the power-cycling I've been doing appears have done bad things to > the local disk on one of my development machines. I'm hoping that you > might have short recipe on setting up diskless boot with xen. >=20 > I set up PXEboot long ago, but I recall the documentation as being > rather poor. >=20 > Thanks. > -Kip >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel >=20 >