Re: Cant install NetBSD DOMU

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

On Sat, Feb 09, 2008 at 04:53:55PM +0000, Mark Kirby wrote:
> Hi,
> 
> I have been following the XEN how-to and have a NetBSD i386 4.99.52  
> DOM0 running fine.
> 
> The problem i am having is that when i try to get a DOMU installed  
> via the install kernel it just seems to hang
> 
> The output from the failed boot is
> 
> # xm create -c /usr/pkg/etc/xen/nbsd_c
> Using config file "/usr/pkg/etc/xen/nbsd_c".
> Started domain nbsd_c
> vcpu0: AMD Unknown K7 (Athlon) (686-class), 2411.74 MHz, id 0x20ff2
> vcpu0: features  
> 78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR>
> vcpu0: features 78bfbff<PGE,MCA,CMOV,PAT,PSE36,MPC,MMX>
> vcpu0: features 78bfbff<FXSR,SSE,SSE2>
> debug virtual interrupt using event channel 3
> xenbus0 at hypervisor0: Xen Virtual Bus Interface
> xencons0 at hypervisor0: Xen Virtual Console Driver
> xencons0: console major 143, unit 0
> xencons0: using event channel 2
> npx0 at hypervisor0: using exception 16
> timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
> Xen clock: using event channel 4
> timecounter: Timecounter "xen_system_time" frequency 1000000000 Hz  
> quality 10000
> Kernelized RAIDframe activated
> md0: internal 5000 KB image area
> xenbus0: using event channel 1
> xbd0 at xenbus0 id 1: Xen Virtual Block Device Interface
> xbd0: using event channel 5
> unknown type console at xenbus0 id 0 not configured
> unknown type console at xenbus0 id 0 not configured
> 
> 
> It just sits there and never gets to sysinst.
> 
> nbsd_c looks like
> 
> wobble:/external mark$ cat nbsd_c
> kernel = "/root/netbsd-INSTALL_XEN3_DOMU"
> 
> memory = 512
> 
> name = "nbsd_c"
> 
> vuf = [ 'mac=aa:00:00:50:02:f0 bridge=bridge0' ]

typo: this should be vif = not vuf =. but I'm not sure it's the cause
of the hang (only the cause of the missing xennet).

> 
> disk = [ 'phy:/dev/wd0e,0x1,w' ]
> 
> root = "/dev/wd0d"
> 
> The install kernel is also 4.99.52, any one have any ideas where i  
> have gone wrong?

Do you get any info in the xen logs (/var/log/xen*) and dmesg ? 
Is wd0e used by something else ?

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