Re: i386 2Gb RAM, netbsd-4-0-RELEASE XEN3_DOM0

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

On Fri, Feb 29, 2008 at 06:33:14PM +0100, Damian Sobczak wrote:
> Hi,
> 
> again have some small problems. This domU with.
> I want netbsd-4-0-RELEASE as dom0 and NetBSD currnet and Solaris as domU
> 
> My dom1 config:
> 
> Quantum# cat /usr/pkg/etc/xen/dom1
> # -*- mode: python; -*-
> #============================================================================
> # Python defaults setup for 'xm create'.
> # Edit this file to reflect the configuration of your system.
> #============================================================================
> 
> #----------------------------------------------------------------------------
> # Kernel image file. This kernel will be loaded in the new domain.
> kernel = "/netbsd-XEN3_DOMU"
> #kernel = "/netbsd-INSTALL_XEN3_DOMU"
> 
> # Memory allocation (in megabytes) for the new domain.
> memory = 512
> 
> # A handy name for your new domain. This will appear in 'xm list',
> # and you can use this as parameters for xm in place of the domain
> # number. All domains must have different names.
> #
> name = "dom1"
> 
> # Which CPU to start domain on (only relevant for SMP hardware). CPUs
> # numbered starting from ``0''.
> #
> cpu = 0 # leave to Xen to pick
> 
> #----------------------------------------------------------------------------
> # Define network interfaces for the new domain.
> 
> # Number of network interfaces (must be at least 1). Default is 1.
> #nics = 1
> 
> # Define MAC and/or bridge for the network interfaces.
> #
> # The MAC address specified in ``mac'' is the one used for the interface
> # in the new domain. The interface in domain0 will use this address XOR'd
> # with 00:00:00:01:00:00 (i.e. aa:00:00:51:02:f0 in our example). Random
> # MACs are assigned if not given.
> #
> # ``bridge'' is a required parameter, which will be passed to the
> # vif-script called by xend(8) when a new domain is created to configure
> # the new xvif interface in domain0.
> #
> # In this example, the xvif is added to bridge0, which should have been
> # set up prior to the new domain being created -- either in the
> # ``network'' script or using a /etc/ifconfig.bridge0 file.
> #
> vif = [ 'mac=aa:00:00:50:02:f0, bridge=bridge0' ]
> 
> #----------------------------------------------------------------------------
> # Define the disk devices you want the domain to have access to, and
> # what you want them accessible as.
> #
> # Each disk entry is of the form:
> #
> # phy:DEV,VDEV,MODE
> #
> # where DEV is the device, VDEV is the device name the domain will see,
> # and MODE is r for read-only, w for read-write. You can also create
> # file-backed domains using disk entries of the form:
> #
> # file:PATH,VDEV,MODE
> #
> # where PATH is the path to the file used as the virtual disk, and VDEV
> # and MODE have the same meaning as for ``phy'' devices.
> #
> # VDEV doesn't really matter for a NetBSD guest OS (it's just used as an
> index),
> # but it does for Linux.
> # Worse, the device has to exist in /dev/ of domain0, because xm will
> # try to stat() it. This means that in order to load a Linux guest OS
> # from a NetBSD domain0, you'll have to create /dev/hda1, /dev/hda2, ...
> # on domain0, with the major/minor from Linux :(
> # Alternatively it's possible to specify the device number in hex,
> # e.g. 0x301 for /dev/hda1, 0x302 for /dev/hda2, etc ...
> 
> disk = [ 'phy:/dev/wd0i,0x1,w' ]
> #disk = [ 'file:/var/xen/nbsd-disk,0x01,w' ]
> #disk = [ 'file:/var/xen/nbsd-disk,0x301,w' ]
> 
> #----------------------------------------------------------------------------
> # Set the kernel command line for the new domain.
> 
> # Set root device. This one does matter for NetBSD
> root = "/dev/wd0d"
> # extra parameters passed to the kernel
> # this is where you can set boot flags like -s, -a, etc ...
> #extra = ""
> 
> #----------------------------------------------------------------------------
> # Set according to whether you want the domain restarted when it exits.
> # The default is False.
> #autorestart = True
> 
> # end of nbsd config file
> ====================================================
> 
> And here are the errors:
> 
> Quantum# xm create -c /usr/pkg/etc/xen/dom1
> Using config file "/usr/pkg/etc/xen/dom1".
> Started domain dom1
> Loaded initial symtab at 0xc048a97c, strtab at 0xc04b8068, # entries 11558
> Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
>   2006, 2007
>   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 4.0 (XEN3_DOMU) #0: Sun Dec 16 01:26:00 PST 2007
>   builds@wb34
> :/home/builds/ab/netbsd-4-0-RELEASE/i386/200712160005Z-obj/home/builds/ab/netbsd-4-0-RELEASE/src/sys/arch/i386/compile/XEN3_DOMU
> total memory = 512 MB
> avail memory = 498 MB
> timecounter: Timecounters tick every 10.000 msec
> mainbus0 (root)
> hypervisor0 at mainbus0
> vcpu0 at hypervisor0: (uniprocessor)
> vcpu0: Intel Pentium Pro, II or III (686-class), 3333.50 MHz, id 0x6f6
> vcpu0: features bfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR>
> vcpu0: features bfebfbff<PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX>
> vcpu0: features bfebfbff<FXSR,SSE,SSE2,SS,HTT,TM,SBF>
> 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
> 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
> xenbus0: using event channel 1
> xbd0 at xenbus0 id 1: Xen Virtual Block Device Interface
> xbd0: using event channel 5
> xennet0 at xenbus0 id 0: Xen Virtual Network Interface
> xennet0: MAC address aa:00:00:50:02:f0
> xennet0: using event channel 6
> unknown type console at xenbus0 id 0 not configured
> xbd0: 76963 MB, 512 bytes/sect x 157622094 sectors
> Searching for RAID components...
> unknown type console at xenbus0 id 0 not configured
> boot device: xbd0
> root on xbd0a dumps on xbd0b
> mountroot: trying lfs...
> mountroot: trying ffs...
> root file system type: ffs
> warning: no /dev/console
> init: copying out path `/sbin/init' 11
> exec /sbin/init: error 2
> init: copying out path `/sbin/oinit' 12
> exec /sbin/oinit: error 2
> init: copying out path `/sbin/init.bak' 15
> exec /sbin/init.bak: error 2
> init: not found
> panic: no init
> Stopped in pid 1.1 (init) at netbsd:cpu_Debugger+0x4: popl %ebp
> db>

Looks like you have no binaires installed on your root partition.
Did you use INTALL-XEN3_DOMU kernel to install a working system
on the virtual drive ?

> 
> 
> Almost everything after HowTO made (?)
> 
> 
> Next,  if I set 2097152 (RAM) for dom0 = Kernel Panic. Unable to boot.

that's quite possible. Doing so would leave no RAM available for
Xen or other domains, if your system has only 2GB physical RAM.

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