Port-xen archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

NetBSD DomU stuck after xennet0 initialization (can't DIOCGPART file:/)


I'm trying to run a NetBSD-CURRENT DomU on a Xen 3.3.2nb1 kernel +
NetBSD 5.1_STABLE dom0, but the domU's boot process stops after
"xennet0: using RX copy mode". When I xm shutdown the VM it responds
and goes down cleanly â but in the meantime it just sits there and
does nothing:

% sudo xm create -c conf
Using config file "./conf".
Started domain netbsd-current
                             Loaded initial symtab at 0xc09d9c80,
strtab at 0xc0a12f4c, # entries 13661
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008, 2009, 2010, 2011
    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 5.99.43 (INSTALL_XEN3PAE_DOMU) #0: Sat Jan 15 00:49:20 CET 2011
total memory = 128 MB
avail memory = 115 MB
mainbus0 (root)
hypervisor0 at mainbus0: Xen version 3.3
vcpu0 at hypervisor0: Intel 686-class, 1662MHz, id 0x106ca
xenbus0 at hypervisor0: Xen Virtual Bus Interface
xencons0 at hypervisor0: Xen Virtual Console Driver
xencons0: using event channel 2
npx0 at hypervisor0: using exception 16
xbd0 at xenbus0 id 1: Xen Virtual Block Device Interface
xennet0 at xenbus0 id 0: Xen Virtual Network Interface
xennet0: MAC address 00:16:3e:4b:79:b0
xennet0: using RX copy mode

nothing happens until (on another shell)
% sudo xm shutdown netbsd-current

xenbus: power button pressed, shutting down!
syncing disks... done

The same happens with the XEN3PAE_DOMU kernel built from the same
source tree (via ./build.sh release, configuration unmodified) and the
5.1 install kernel binary from FTP.

In dmesg, there's a complaint from xbdback about "can't DIOCGPART
device 0xe03: 6":

xbdback backend/vbd/4/1: can't DIOCGPART device 0xe03: 6
xvif4.0: Ethernet address 00:16:3e:7d:59:69
xbd backend 0x1 for domain 4 using event channel 21, protocol x86_32-abi

xbackendd also has something to say:
Jan 16 14:18:03 zz xenbackendd[266]: Failed to read
/local/domain/0/backend/console/4/0/script (No such file or directory)

but from what I've googled this should be harmless(?)

I've found http://mail-index.netbsd.org/port-xen/2009/11/09/msg005549.html
which appears to be sort of the same problem ... except that I'm not
using LVM or anything, just a file of 2GiB zeroes.

This is my first time to xen, so I may have just been missing
something very obvious.

Some more info:

% uname -a
NetBSD zz.2pktfkt.net 5.1_STABLE NetBSD 5.1_STABLE (XEN3PAE_DOM0) #0:
Fri Jan 14 12:49:49 CET 2011

% sudo xm list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0   256     1     r-----    936.3
netbsd-current                               4   128     1     -b----      1.7

% ifconfig -a
mtu 1500
        address: 00:01:2e:bc:70:32
        media: Ethernet autoselect (1000baseT full-duplex)
        status: active
        inet netmask 0xffffff00 broadcast
        inet6 fe80::201:2eff:febc:7032%re0 prefixlen 64 scopeid 0x1
        inet6 2001:6f8:1c35:0:201:2eff:febc:7032 prefixlen 64
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33184
        inet netmask 0xff000000
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
bridge0: flags=41<UP,RUNNING> mtu 1500
mtu 1500
        address: 00:16:3e:7d:59:69
        inet6 fe80::216:3eff:fe7d:5969%xvif4.0 prefixlen 64 scopeid 0x4

% brconfig -a
bridge0: flags=41<UP,RUNNING>
                priority 32768 hellotime 2 fwddelay 15 maxage 20
                ipfilter disabled flags 0x0
                xvif4.0 flags=3<LEARNING,DISCOVER>
                        port 4 priority 128
                re0 flags=3<LEARNING,DISCOVER>
                        port 1 priority 128
        Address cache (max cache: 100, timeout: 1200):
                58:b0:35:f8:ad:f7 re0 1194 flags=0<>
                00:24:d7:50:35:78 re0 1186 flags=0<>
                d8:5d:4c:ae:4f:02 re0 614 flags=0<>

I've attached the VM configuration, xend.log and xend-debug.log.

Many thanks!

Attachment: xend.log
Description: Binary data

Attachment: conf
Description: Binary data

Attachment: xend-debug.log
Description: Binary data

Home | Main Index | Thread Index | Old Index