On Wed, 2006-11-01 at 13:27 -0500, Jimi Xenidis wrote:
> First, I really appreciate you updating the wiki, I think its awesome!
> On Oct 31, 2006, at 4:24 PM, [EMAIL PROTECTED] wrote:
> >
> > + === Example ===
> > + Have a machine with Linux install on /dev/hda3. We do not have  
> > any parameters to pass to the Xen hypervisor. So once
> > + SLOTH firmware loads up. You will PXE boot the Xen image built  
> > (no command line paramters specified in the build) and specify the  
> > parameters on here:
> What do you mean "PXE boot"? I think this is an intel/x86 world term.
> This is a standard Open Firmware command:
>    "boot <device> <params>"
sigh...me coming from x86, I screwed the terminology. I will change it,
if it has not already been changed. "netboot" would be a much better

> Specifically, (assuming you have not defined the file, IP  
> configuration, and TFTP server) in this case you will be TFTPing the  
> image that that a BOOTP packet tells "net1" to load
> > + {{{
> > + boot net1 xen -- root=/dev/hda3
> > + }}}

Yes I left out the part about setting up the bootp & tftp enviroment
(figured most folks whould probably know that part), mainly I was
putting an example of the command line to enter when using Sloth. I was
at first just doing "netboot root=/dev/hda3". I can rework the example
and make it more clear. But thought there needed to be a clear example
for folks to try and understand. 

> > + <!> - note the word "xen" is placed as the parameter for the  
> > Hypervisor because you cannot have no parameter, so just put  
> > somehting that will just be dropped.
> Is this _still_ true?  I think at some point Xen actually wanted to  
> see this string to verify that the person actually wanted to boot Xen  
> and has since been removed.  You should be able to boot without it,  
> if not we need to find out why.

I'll give it a try and let everyone know.

> -JX

Xen-ppc-devel mailing list

Reply via email to