On Thu, May 10, 2007 at 08:18:07PM +0300, Martti Kuparinen wrote:
> Manuel Bouyer kirjoitti:
> 
> >Adding mem=3072M on the xen.gz boot line worked around it for me ...
> 
> :-)
> 
> ROOT xen3:~> xm list
> Name                                      ID   Mem VCPUs      State   
> Time(s)
> Domain-0                                   0   256     1     r-----     11.9
> netbsd1                                    1   255     1     -b----      0.7
> 
> ROOT xen3:~> cat /grub/menu.lst
> default=0
> timeout=10
> title           NetBSD/xen with RAID-1
> root            (hd0,a)
> kernel          (hd0,a)/xen.gz dom0_mem=262144 mem=3072M
> module          (hd0,a)/netbsd root=/dev/hda1 ro console=tty0
> 
> title           NetBSD/i386 GENERIC
> root            (hd0,a)
> kernel          /netbsd.GENERIC
> 
> 
> This makes me wonder, what could be causing this? BIOS bug? Does this 
> affect Linux dom0 as well?

Initially I though it was a bios bug, but after more reports and though
it's probably a problem somewhere else. Brian Marcotte did more research
on this (he has the problem with a supermicro board), you can see his mails
on port-xen.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--