Re: Xen2 support broken?

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Tue, Nov 11, 2008 at 09:22:01AM -0500, Brian Marcotte wrote:
> > Did you try changing the memory line ? I use
> > memory = 64
> 
> I just tried various things from 64 to 1100. I also shut down as many
> other domains as I could for this test. Unfortunately, I can't shut them
> all down right now.
> 
> I found that this was added to xend-debug.log when trying to start the
> domain:
> 
>       VIRTUAL MEMORY ARRANGEMENT:
>        Loaded kernel: c0100000->c04dab54
>        Init. ramdisk: c0544000->c0544000
>        Phys-Mach map: c0544000->c058f000
>        Page tables:   c058f000->c0592000
>        Start info:    c0592000->c0593000
>        Boot stack:    c0593000->c0594000
>        TOTAL:         c0100000->c0800000
>        ENTRY ADDRESS: c0100000
>       vif-bridge up vif=vif48.0 domain=xxxxxxx mac=ee:ee:20:55:70:1c \
>         bridge=bridge8
>       VirqClient.virqReceived> 4
>       vif-bridge down vif=vif48.0 domain=xxxxxxx mac=ee:ee:20:55:70:1c \
>         bridge=bridge8

Looks good, mine starts with
VIRTUAL MEMORY ARRANGEMENT:
 Loaded kernel: c0100000->c041b178
 Init. ramdisk: c0471000->c0471000
 Phys-Mach map: c0471000->c0481000
 Page tables:   c0481000->c0484000
 Start info:    c0484000->c0485000
 Boot stack:    c0485000->c0486000
 TOTAL:         c0100000->c0800000
 ENTRY ADDRESS: c0100000
vif-bridge up vif=vif27.0 domain=lavardin1 mac=aa:00:00:50:0b:f0 
bridge=10.0.1.254 netmask 0xffffff00
vif-bridge up vif=vif27.1 domain=lavardin1 mac=aa:00:00:50:0b:f1 bridge=up

However your kernel looks larger. Could you try with the exaxt same kernel
as mine (netbsd-XEN2_DOMU.gz from
ftp://ftp.fr.netbsd.org/pub/NetBSD-daily/netbsd-5/200811030002Z/i386/binary/sets/

and see if the memory map is the same as mine ?

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