On Mon, Sep 10, 2007 at 05:23:40PM +1000, Daniel Carosone wrote:
> On Mon, Sep 10, 2007 at 05:13:40PM +1000, Sarton O'Brien wrote:
> > Either way, I've been using the default version with NetBSD current and this 
> > has always been the case for me also, having to decompress the image for grub 
> > to load it. Passing xen a compressed dom0 is no issue.
> 
> Odd, I have had no problems with a compressed xen vmm, over quite a
> few machines and xen2 or xen3.

Yeah, I thought it odd. And now thinking back, I originally could use 
a compressed kernel so either grub or the xen kernel changed in some way.
I was pretty sure it was after a xen update (kernel file size?).

Honestly, it's been a non-issue.

> > If there is a size limit required of the first slice for grub to be able to 
> > boot the compressed image, I'm guessing I've exceeded it.
> 
> Maybe one of those bios/LBA-mode-X disk/partition size limits; I
> always use a small root or boot fs so I wouldn't hit this if it were
> so.

I'd say this is probably half my problem. I normally have a small root
partition but of late have got out of the habit. With xen, I've not
bothered at all but as I said above, pretty sure it was working with
a stock install at the beginning and I haven't altered the disk layout.

I might have a look at the original xen3 kernel, check the size and see
if it has the same limitation booting. It's not a problem for me at all
but it might be worth knowing why so it can be documented.

Sarton