Re: Xen3 domU functionnal

[Stephane Bortzmeyer <stephane%sources.org@localhost>]

On Wed, Mar 22, 2006 at 10:28:24PM +0100,
 Manuel Bouyer <bouyer%antioche.eu.org@localhost> wrote 
 a message of 31 lines which said:

> This is the problem; maybe you want /dev/hda or /dev/hda1 here instead ?

Much better, now NetBSD starts but crashes:

Loaded initial symtab at 0xc0485cb4, strtab at 0xc04b4498, # entries 11826
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006
    The NetBSD Foundation, Inc.  All rights reserved.                         
Copyright (c) 1982, 1986, 1989, 1991, 1993           
    The Regents of the University of California.  All rights reserved.
                                                                      
NetBSD 3.99.17 (XEN3_U) #1: Mon Mar 20 18:15:29 CET 2006
        
bouyer%blues.lip6.fr@localhost:/Volumes/data/bouyer/tmp/i386/obj/Volumes/data/bouyer/current/src/sys/arch/i386/compile/XEN3_U
total memory = 61420 KB                    
avail memory = 60168 KB
mainbus0 (root)        
cpu0 at mainbus0: (uniprocessor)
cpu0: Intel Pentium II (Klamath) (686-class), 231.78 MHz, id 0x634
cpu0: features 80f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR>
cpu0: features 80f9ff<PGE,MCA,CMOV,MMX>                           
cpu0: I-cache 16 KB 32B/line 4-way, D-cache 16 KB 32B/line 4-way
cpu0: L2 cache 512 KB 32B/line 4-way                            
cpu0: ITLB 32 4 KB entries 4-way, 2 4 MB entries fully associative
cpu0: DTLB 64 4 KB entries 4-way, 8 4 MB entries 4-way            
cpu0: 32 page colors                                  
hypervisor0 at mainbus0
debug virtual interrupt using event channel 3
xenbus0 at hypervisor0: Xen Virtual Bus Interface
xenbus0: using event channel 1                   
xencons0 at hypervisor0: Xen Virtual Console Driver
xencons0: console major 143, unit 0                
xencons0: using event channel 2 
npx0 at hypervisor0: using exception 16
Xen clock: using event channel 4       
crypto: assign driver 0, flags 2
crypto: driver 0 registers alg 1 flags 0 maxoplen 0
crypto: driver 0 registers alg 2 flags 0 maxoplen 0
crypto: driver 0 registers alg 3 flags 0 maxoplen 0
crypto: driver 0 registers alg 4 flags 0 maxoplen 0
crypto: driver 0 registers alg 5 flags 0 maxoplen 0
crypto: driver 0 registers alg 17 flags 0 maxoplen 0
crypto: driver 0 registers alg 6 flags 0 maxoplen 0 
crypto: driver 0 registers alg 7 flags 0 maxoplen 0
crypto: driver 0 registers alg 15 flags 0 maxoplen 0
crypto: driver 0 registers alg 8 flags 0 maxoplen 0 
crypto: driver 0 registers alg 16 flags 0 maxoplen 0
crypto: driver 0 registers alg 9 flags 0 maxoplen 0 
crypto: driver 0 registers alg 10 flags 0 maxoplen 0
crypto: driver 0 registers alg 13 flags 0 maxoplen 0
crypto: driver 0 registers alg 14 flags 0 maxoplen 0
crypto: driver 0 registers alg 11 flags 0 maxoplen 0
crypto: driver 0 registers alg 18 flags 0 maxoplen 0
raidattach: Asked for 8 units                       
Kernelized RAIDframe activated
xbd0 at xenbus0 id 769: Xen Virtual Block Device Interface
panic: kernel diagnostic assertion "(flags & UVM_KMF_TYPEMASK) == UVM_KMF_WIRED 
|| (flags & UVM_KMF_TYPEMASK) == UVM_KMF_PAGEABLE || (flags & UVM_KMF_TYPEMASK) 
== UVM_KMF_VAONLY" failed: file 
"/Volumes/data/bouyer/current/src/sys/uvm/uvm_km.c", line 525
Stopped in pid 2.1 (xenbus_probe) at    netbsd:cpu_Debugger+0x4:        popl    
%
ebp
db> 
db>