Hello folks!
I have a nice NetBSD-as-dom0 Xen setup, but now it's time to make my
NetBSD domUs.
It's an amd64, running NetBSD-7.0.1 in dom0:
pkbs# uname -a
NetBSD pkbs.XXX 7.0.1 NetBSD 7.0.1 (XEN3_DOM0.201605221355Z) amd64
I've installed xenkerlen45 and xentools45.
And I'm trying to fire up a domU with the NetBSD-7.0.1 amd64 INSTALL kernel.
My xl.cfg file says:
name="vm2"
builder="generic"
vcpus="2"
maxvcpus="2"
memory=1024
maxmem=1024
kernel="/domU/blob-cache/NetBSD-7.0.1.install-kernel.gz"
disk=["phy:/dev/vg0/vm2-root,0x0,w", "phy:/dev/vg0/vm2-swap,0x1,w"]
vif=['mac=aa:00:00:d1:00:2,bridge=bridge0']
But what I get is:
------------B<-----------
pkbs# xl create -c /domU/domUs/vm2/xl.cfg
Parsing config from /domU/domUs/vm2/xl.cfg
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015
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 7.0.1 (INSTALL_XEN3_DOMU.201605221355Z)
total memory = 1024 MB
avail memory = 977 MB
kern.module.path=/stand/amd64/7.0/modules
mainbus0 (root)
hypervisor0 at mainbus0: Xen version 4.5.3
vcpu0 at hypervisor0: Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz, id 0x306c3
vcpu1 at hypervisor0: Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz, id 0x306c3
xenbus0 at hypervisor0: Xen Virtual Bus Interface
xencons0 at hypervisor0: Xen Virtual Console Driver
xenbus: can't get state for device/suspend/event-channel (2)
xbd0 at xenbus0 id 0: Xen Virtual Block Device Interface
xbd1 at xenbus0 id 1: Xen Virtual Block Device Interface
xennet0 at xenbus0 id 0: Xen Virtual Network Interface
xennet0: MAC address aa:00:00:d1:00:02
balloon0 at xenbus0 id 0: Xen Balloon driver
balloon0: current reservation: 1048576 KiB
xennet0: using RX copy mode
xenbus: can't get state for device/suspend/event-channel (2)
balloon0: current reservation: 262144 pages => target: 262144 pages
ignore shutdown request:
xenbus: can't get state for device/suspend/event-channel (2)
------------B<-----------
...and it hangs there forever. I can quit the xl console and "xl
destroy" the VM, but the INSTALL kernel just seems to sit tight, doing
nothing.
I dropped the domU into DDB with five plus signs:
------------B<-----------
fatal breakpoint trap in supervisor mode
trap type 1 code 0 rip ffffffff8012e5ad cs e030 rflags 202 cr2 0 ilevel
8 rsp ffffa0002d9eac58
curlwp 0xffffa00001df3840 pid 0.2 lowest kstack 0xffffa0002d9e82c0
Stopped in pid 0.2 (system) at netbsd:breakpoint+0x5: leave
breakpoint() at netbsd:breakpoint+0x5
xencons_tty_input() at netbsd:xencons_tty_input+0xb2
xencons_handler() at netbsd:xencons_handler+0x65
intr_biglock_wrapper() at netbsd:intr_biglock_wrapper+0x19
evtchn_do_event() at netbsd:evtchn_do_event+0x281
do_hypervisor_callback() at netbsd:do_hypervisor_callback+0x143
hypervisor_callback() at netbsd:hypervisor_callback+0x9e
idle_loop() at netbsd:idle_loop+0xe8
ds 3a40
es c540
fs bfe0
gs 6033
rdi ffffa00002166030
rsi ffffffff80fc6004
rbp ffffa0002d9eac58
rbx ffffffff80fc6004
rdx 2b
rcx 2b
rax 1
r8 0
r9 ffffffff805fc540 cpu_info_primary
r10 3594c0522ed011b7
r11 246
r12 ffffa0000216e980
r13 ffffffff80fc6005
r14 ffffa00002166030
r15 1
rip ffffffff8012e5ad breakpoint+0x5
cs e030
rflags 202
rsp ffffa0002d9eac58
ss e02b
netbsd:breakpoint+0x5: leave
------------B<-----------
dmesg in DDB reveals more console output than I'd seen through my xen
console, which is weird - it talks of IPSec setup:
------------B<-----------
db{0}> dmesg
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015
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 7.0.1 (INSTALL_XEN3_DOMU.201605221355Z)
total memory = 1024 MB
avail memory = 977 MB
kern.module.path=/stand/amd64/7.0/modules
timecounter: Timecounters tick every 10.000 msec
mainbus0 (root)
hypervisor0 at mainbus0: Xen version 4.5.3
VIRQ_DEBUG interrupt using event channel 3
vcpu0 at hypervisor0: Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz, id 0x306c3
vcpu1 at hypervisor0: Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz, id 0x306c3
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
timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
timecounter: Timecounter "xen_system_time" frequency 1000000000 Hz
quality 10000
Xen clock: using event channel 5
Xen clock: using event channel 7
xenbus0: using event channel 1
xenbus: can't get state for device/suspend/event-channel (2)
xbd0 at xenbus0 id 0: Xen Virtual Block Device Interface
xbd0: using event channel 8
xbd1 at xenbus0 id 1: Xen Virtual Block Device Interface
xbd1: using event channel 9
xennet0 at xenbus0 id 0: Xen Virtual Network Interface
xennet0: MAC address aa:00:00:d1:00:02
xennet0: using event channel 10
balloon0 at xenbus0 id 0: Xen Balloon driver
balloon0: current reservation: 1048576 KiB
xennet0: using RX copy mode
xenbus: can't get state for device/suspend/event-channel (2)
balloon0: current reservation: 262144 pages => target: 262144 pages
ignore shutdown request:
xenbus: can't get state for device/suspend/event-channel (2)
IPsec: Initialized Security Association Processing.
fatal breakpoint trap in supervisor mode
trap type 1 code 0 rip ffffffff8012e5ad cs e030 rflags 202 cr2 0 ilevel
8 rsp ff
ffa0002d9eac58
curlwp 0xffffa00001df3840 pid 0.2 lowest kstack 0xffffa0002d9e82c0
------------B<-----------
I *think* the fatal breakpoint trap is purely me entering DDB manually,
because it matches the addresses and whatnot I got as soon as I entered
the sequence.
ps gives me this lot:
------------B<-----------
db{0}> ps
PID LID S CPU FLAGS STRUCT LWP * NAME WAIT
1 1 3 1 0 ffffa00002172100 init lbolt
0 36 3 0 200 ffffa00002172520 cryptoret crypto_w
0 35 3 0 200 ffffa0000216c0c0 unpgc unpgc
0 34 3 0 200 ffffa00002173960 xen_balloon xen_balloon
0 33 3 0 200 ffffa00002173540 vmem_rehash vmem_rehash
0 32 3 0 200 ffffa00002174980 xenbus rdst
0 31 3 0 200 ffffa00002173120 xenwatch evtsq
0 21 3 1 200 ffffa0000216c4e0 xcall/1 xcall
0 20 1 1 200 ffffa0000216c900 softser/1
0 19 1 1 200 ffffa0000216b0a0 softclk/1
0 18 1 1 200 ffffa0000216b4c0 softbio/1
0 17 1 1 200 ffffa0000216b8e0 softnet/1
0 > 16 7 1 201 ffffa0000215d080 idle/1
0 15 3 0 200 ffffa0000215d4a0 pmfsuspend pmfsuspend
0 14 3 0 200 ffffa0000215d8c0 pmfevent pmfevent
0 13 3 0 200 ffffa00001e02060 sopendfree sopendfr
0 12 3 0 200 ffffa00001e02480 nfssilly nfssilly
0 11 3 0 200 ffffa00001e028a0 cachegc cachegc
0 10 3 0 200 ffffa00001e00040 vrele vrele
0 9 3 0 200 ffffa00001e00460 vdrain vdrain
0 8 3 0 200 ffffa00001e00880 modunload mod_unld
0 7 3 0 200 ffffa00001df6020 xcall/0 xcall
0 6 1 0 200 ffffa00001df6440 softser/0
0 5 1 0 200 ffffa00001df6860 softclk/0
0 4 1 0 200 ffffa00001df3000 softbio/0
0 3 1 0 200 ffffa00001df3420 softnet/0
0 > 2 7 0 201 ffffa00001df3840 idle/0
0 1 3 0 200 ffffffff8060ac60 swapper cfgmisc
------------B<-----------
I do not know what's normal at this stage in the boot, so I don't know
what to make of it all :-(
Does anybody know what I might be doing wrong, or what I need to do to
find out what the problem is?
Many thanks,
ABS
--
Alaric Snell-Pym
http://www.snell-pym.org.uk/alaric/
Attachment:
signature.asc
Description: OpenPGP digital signature