NetBSD -CURRENT with Xen3.0.3: grub failed with Error3 and Error 13

thanks for answer,

but ... i would wonder because of this:
http://www.netbsd.org/Ports/xen/howto.html#netbsd-domai
n0
and this:
http://www.gnu.org/software/grub/manual/grub.html#NetBSD


but i tried and get error 3 instead of error 13 for
netbsd-GENERIC.gz

More important first is the error 3 for xen.gz
What i found was this:
http://mail-index.netbsd.org/port-i386/2004/07/08/001
5.html
"Error 3 is reported when the first sector of the mbr
partition (sector
63 here) doesn't contain boot code. This is usually added by
installboot
but it (probably) relies on the root filesystem being at the
start of
that partition."

But i don't know what to do to boot successull into xen.

regards,
Rainer

Pavel Cahyna schrieb:

>On Sat, Nov 04, 2006 at 09:36:44PM +0100, Rainer
Brinkm�ller wrote:
>  
>
>>Hi,
>>
>>after i did install NetBSD 3.0.1 on my new Hardware
and did update it to 
>>-CURRENT
>>on this way: http://www.netbsd.org/Documentation/current/#updating
>>i did install grub, xentools30, xenkernel30 and
xentools-hvm
>>
>>Then configured grub. Reboot and .. failure ...
remember ... sure, the kernel 
>>file is to big
>>So, gzip the kernel file and reboot. Failure again.
>>
>>First Error when want to start by using kernel
xen.gz and netbsd-XEN0.gz as 
>>module:
>>
>>kernel (hd0,a)/xen.gz dom0_mem=131072
>>     [Multiboot-elf,
<0x100000:0x7e5d8:0x47a28>
>>
>>Error 3: Bad or corrupt data while decompressing
file
>>
>>Maybe something wrong with the xen.gz kernel file?
>>The second Error i've got when want to start by
using kernel netbsd-GENERIC.gz 
>>as module:
>>
>>root (hd0,a)
>>    Filesystem type is ffs, partition type 0xa9
>>kernel --type=netbsd /netbsd-GENERIC.gz
>>     [Multiboot-elf, <0x100000:0x9ddfc0:0x0>
>>    
>>
>
>Don't use --type=netbsd if the kernel is Multiboot, I
think.
>
>Pavel
>
>  
>

On Sun, 5 Nov 2006, Rainer Brinkmoeller wrote:
> What i found was this:
> http://mail-index.netbsd.org/port-i386/2004/07/08/001
5.html
> "Error 3 is reported when the first sector of the
mbr partition (sector
> 63 here) doesn't contain boot code. This is usually
added by installboot
> but it (probably) relies on the root filesystem being
at the start of
> that partition."
>
> But i don't know what to do to boot successull into
xen.

Maybe grub(?) can't read the filesystem to find the file
it's looking for?
I could imagine this happening when grub tries to find
things on an FFSv2 
or LFS filesystem...


  - Hubert

On Mon, 6 Nov 2006 22:19:54 +0100 (CET)
Hubert Feyrer <hubertfeyrer.de> wrote:

> Maybe grub(?) can't read the filesystem to find the
file it's looking
> for? I could imagine this happening when grub tries to
find things on
> an FFSv2 or LFS filesystem...

GRUB supports booting from FFSv2 around 2/3 years ago (even
maybe more).

Hubert Feyrer schrieb:

> On Sun, 5 Nov 2006, Rainer Brinkmoeller wrote:
>
>> What i found was this:
>> http://mail-index.netbsd.org/port-i386/2004/07/08/001
5.html
>> "Error 3 is reported when the first sector of
the mbr partition (sector
>> 63 here) doesn't contain boot code. This is usually
added by installboot
>> but it (probably) relies on the root filesystem
being at the start of
>> that partition."
>>
>> But i don't know what to do to boot successull into
xen.
>
>
> Maybe grub(?) can't read the filesystem to find the
file it's looking 
> for?
> I could imagine this happening when grub tries to find
things on an 
> FFSv2 or LFS filesystem...
>
>
>  - Hubert

It was a FFSv1 filesystem. But only one big (140 GB)
Partition in one 
slice with only a / mount point.

So i did learn and reinstall. Now my / is a 1024 MB big
mount point 
(within its own slice) with 8k/1k block/fragment sizes on a
FFSv1 
filesystem.
Other mount points (like /usr, /var, /home, etc.) are
different slices.

It seems to work fine. NetBSD -current with Xen 3.0.3 is
booting now. 
Thanks to Manuel.
The Problem with the GENERIC kernel still exist. But i
didn't try to 
compress again or without "--type=netbsd" yet.

> 
> Isn't it better to make a small /boot (or /stand)
partition which would
> hold only the kernels, like Linux does if the bios does
have disk size
> limit?
> 
> Small / can be inconvenient.
> 
> Rainer, can't you steal some space from swap partition
to create such
> small partition?
> 

Pavel:
no i could not because i used the complete disk as one
partition and 
also as mount point /.
Why do you think that a small / can be inconvenient?
In my opinion a 2048 MB / should be ok for grub. All other
mount points 
can have their own slices like the way i did.

regards,
Rainer