Re: Trouble installing a NetBSD domU

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

On Sun, Jun 26, 2016 at 05:24:18PM +0100, Alaric Snell-Pym wrote:
> 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 guess it waits either for the disks or network interface.
Does bridge0 exists in your dom0 ?

> 
> I dropped the domU into DDB with five plus signs:
> 
> [...]
> dmesg in DDB reveals more console output than I'd seen through my xen
> console, which is weird - it talks of IPSec setup:

that's not a problem: aprint_verbose outputs is not normally displayed
(unless you boot with -v) but is recorded in the message buffer.

> [...]
> 
> 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.

it is.

> 
> I do not know what's normal at this stage in the boot, so I don't know
> what to make of it all :-(

it looks good; I gess it's now waiting for the dom0 to provide the
virtual devices (maybe the disks).

does "dmesg" in dom0 shows anything ?

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