Andrey Khavryuchenko wrote:
> Hi!
>
> I can't boot NetBSD 3.1 DomU in my Debian Dom0. It fails to find boot/root
> device.
>
> The configuration file is:
>
> $ cat /etc/xen/netbsd.kds.priv.cfg
> kernel="/xen/dist/kernels/netbsd/netbsd-XEN3_DOMU"
> extra="bootdev=/dev/wd0"
> root = "/dev/wd0a"
>
> memory='64'
> name="netbsd.kds.priv"
> dist = ['file:/xen/domains/netbsd.kds.priv/disk.img,0x3,w']
>
> ip='10.0.2.17'
> netmask='255.255.255.0'
> gateway='10.0.2.2'
>
> The DomU kernel was downloaded from
> ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-3.1/i386/binary/kernel/netbsd-XEN3_DOMU.gz
>
> The boot sequence is the following:
>
> akhavr@dom0 dist/kernels/netbsd $ sudo xm create -c netbsd.kds.priv.cfg
> Using config file "/etc/xen/netbsd.kds.priv.cfg".
> Started domain netbsd.kds.priv
> Loaded initial symtab at 0xc047f948, strtab at 0xc04ac50c, # entries 11383
> Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005
> 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.1 (XEN3_DOMU) #0: Tue Oct 31 04:58:28 UTC 2006
>
> builds@xxxxxxxxxxxxx:/home/builds/ab/netbsd-3-1-RELEASE/i386/200610302053Z-obj/home/builds/ab/netbsd-3-1-RELEASE/src/sys/arch/i386/compile/XEN3_DOMU
> total memory = 61464 KB
> avail memory = 59972 KB
> mainbus0 (root)
> cpu0 at mainbus0: (uniprocessor)
> cpu0: AMD Athlon Model 2 (686-class), 2010.38 MHz, id 0x623
> cpu0: features 2799fbfd<FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR>
> cpu0: features 2799fbfd<PGE,MCA,CMOV,PAT,MPC,NOX,MMX>
> cpu0: features 2799fbfd<FXSR,SSE,SSE2,LONG>
> cpu0: I-cache 64 KB 64B/line 2-way, D-cache 64 KB 64B/line 2-way
> cpu0: L2 cache 512 KB 64B/line 16-way
> cpu0: ITLB 255 4 KB entries direct-mapped, 255 4 MB entries direct-mapped
> cpu0: DTLB 255 4 KB entries direct-mapped, 255 4 MB entries direct-mapped
> cpu0: 8 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
> raidattach: Asked for 8 units
> Kernelized RAIDframe activated
> 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
> Searching for RAID components...
> boot device: <unknown>
> root device:
> use one of: raid0[a-p] raid1[a-p] raid2[a-p] raid3[a-p] raid4[a-p] raid5[a-p]
> raid6[a-p] raid7[a-p] ddb halt reboot
> root device: %
>
> It doesn't depend on any extra="bootdev..." or root = "/dev/wd0a" values as
> well on files line. Actually it produced the same output when the root
> image wasn't there.
>
> Googling didn't produce anything helpful.
>
> Any ideas?
>
> Thanks in advance!
Have you actually installed NetBSD using the netbsd-INSTALL_XEN3_DOMU
first? ( as per http://wiki.xensource.com/xenwiki/NetBSDdomU )
I am interested to get this up and running too. If I run the installer
without defining a disk in the config file, I get the installer dialogue
box, but I can't continue. However if I define a disk I get the following:
xen:/mnt/xen/vserver/images/domains/netbsd# xm create netbsd.cfg -c
Using config file "/etc/xen/netbsd.cfg".
Started domain nbsd
[ Kernel symbol table missing! ]
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005
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.1 (INSTALL_XEN3_DOMU) #0: Tue Oct 31 05:09:39 UTC 2006
builds@xxxxxxxxxxxxx:/home/builds/ab/netbsd-3-1-RELEASE/i386/200610302053Z-obj/home/builds/ab/netbsd-3-1-RELEASE/src/sys/arch/i386/compile/INSTALL_XEN3_DOMU
total memory = 121 MB
avail memory = 118 MB
mainbus0 (root)
cpu0 at mainbus0: (uniprocessor)
cpu0: Intel Pentium 4 (686-class), 2657.81 MHz, id 0xf27
cpu0: features bfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR>
cpu0: features bfebfbff<PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX>
cpu0: features bfebfbff<FXSR,SSE,SSE2,SS,HTT,TM,SBF>
cpu0: I-cache 12K uOp cache 8-way, D-cache 8 KB 64B/line 4-way
cpu0: L2 cache 512 KB 64B/line 8-way
cpu0: ITLB 4K/4M: 128 entries
cpu0: DTLB 4K/4M: 64 entries
cpu0: 16 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
raidattach: Asked for 8 units
Kernelized RAIDframe activated
md0: internal 5000 KB image area
xbd0 at xenbus0 id 3: Xen Virtual Block Device Interface
xbd0: using event channel 5
backend_changed backend
-------Hangs here ---------------
--
Ben
---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0650-2, 23/11/2006
Tested on: 24/11/2006 10:22:58 AM
avast! - copyright (c) 2000-2006 ALWIL Software.
http://www.avast.com
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home