Re: domU kernel with pci support

[Florian Heigl <floh%deranfangvomen.de@localhost>]

On Fri, Oct 14, 2005 at 12:02:28PM -0300, Evaldo Gardenali wrote:
> If you don't want to build your own kernel, you can just use a dom0 
> kernel on a domU, and it will have PCI support.
> I would recommend, though, building a custom kernel to avoid wasting 
> resources ;)

I have used the standard dom0 config and enabled the xennet and xbd devices 
(otherwise the root mount fails), but now experienced a panic, something seems
unhappy.

xen-host-2# diff XEN0 XEN.TEST
193c193
< #xennet*      at hypervisor?          # Xen virtual network interface
---
> xennet*       at hypervisor?          # Xen virtual network interface
195c195
< #xbd*         at hypervisor?          # Xen virtual block device
---
> xbd*          at hypervisor?          # Xen virtual block device


--->bootup, ends in db>

Loaded initial symtab at 0xc067b204, strtab at 0xc06c2a48, # entries 18239
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.0_BETA (XEN.TEST) #0: Fri Oct 14 22:37:33 CEST 2005
        root@xen-host-2:/usr/src/sys/arch/i386/compile/XEN.TEST
total memory = 505 MB
avail memory = 494 MB
mainbus0 (root)
cpu0 at mainbus0: (uniprocessor)
cpu0: Intel Pentium III (686-class), 745.80 MHz, id 0x681
cpu0: features 383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR>
cpu0: features 383fbff<PGE,MCA,CMOV,PAT,PSE36,MMX>
cpu0: features 383fbff<FXSR,SSE>
cpu0: I-cache 16 KB 32B/line 4-way, D-cache 16 KB 32B/line 4-way
cpu0: L2 cache 256 KB 32B/line 8-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: 8 page colors
hypervisor0 at mainbus0
debug virtual interrupt using event channel 2
misdirect virtual interrupt using event channel 0
Domain controller: using event channel 1
xencons0 at hypervisor0: Xen Virtual Console Driver
xencons0: console major 143, unit 0
Initialising Xen virtual ethernet frontend driver.
npx0 at hypervisor0: using exception 16
Xen clock: using event channel 3
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
pci0 at hypervisor0
pci0: no spaces enabled!
Status change: invalid netif handle 0
xbd: using event channel 4
isa0 at hypervisor0
panic: x86_memio_map: bad bus space tag
Stopped in pid 3.1 (ctrlif) at  netbsd:cpu_Debugger+0x4:        leave
cpu_Debugger(0,0,0,cb2c3d64,0) at netbsd:cpu_Debugger+0x4
panic(c05d5360,0,0,0,0) at netbsd:panic+0x121
x86_memio_map(c11abc00,60,1,0,cb2c3b80) at netbsd:x86_memio_map+0xee
pckbc_isa_match(c1015480,c05f37d4,cb2c3d64,0,c1015480) at netbsd:pckbc_isa_match
+0xdd
[I snipped here, if anyone needs it, I can easily reproduce it;]

I unfortunately don't grok 'pci0: no spaces enabled!'

florian


-- 

florian heigl                    http://deranfangvomen.de/

Grid Computing erfreut sich gerade bei Windows-Nutzern sehr regem Zuspruch, auch
wenn die Rechnerbesitzer meist nichts von ihrem Glück wissen. --f. weimer