On Thu, Feb 26, 2009 at 09:38:33PM -0700, James Adams wrote:

> John are saying that I'm deluded in thinking that I followed the same steps 

No, I'm not.

> like it was before you guys removed it and I'll show you -- it listed the 
> same steps, plus several others in the mix to sufficiently obfuscate what's 
> actually required to get it done.  I didn't have to write GRUB menu 

Exactly. Writing the menu entries was the hard bit, and that's why the
document existed.

> If the xVM documentation I've been able to find wasn't so poor it might not 

The correct response to this (since you work for Sun) is to file bugs or
find the right people to fix the problems you see. But you're looking at
the Wiki on opensolaris.org. Sadly this is not a good place to be
looking. At this point, the best solution is to remove old docs from the
Wiki, not keep them around like a bad smell.

(I'd actually prefer to disable everything that's not known to be
current, but this has obvious problems.)

> 1. Go to Google and type in "solaris xvm documentation", and the first page 
> it lists is this one: 
> http://opensolaris.org/os/community/xen/docs/developers/.  That's an 

You want us to fix Google? Come on.

> 2. On that page click on bullet #5, "Booting".  This should be the place to 
> find out how to boot Solaris into xVM mode.

That's a dangling reference that we need to fix. The whole doc is kind
of pointless though - it should probably refer to the docs mentioned
below.

> Is there better xVM documentation available other than what I found above 
> and the virsh/xvm man pages?  I find it almost impossible to believe that 
> there isn't, probably I've just not found it. If so then someone please 
> clue me in so I can stop bothering this list with my newbie questions. 

Go to docs.sun.com and type xvm in the search box. The first two links
are what you want. If those don't answer your questions well enough,
please file bugs.

regards
john
_______________________________________________
xen-discuss mailing list
[email protected]

Reply via email to