I have a NetBSD 5.0_RCish amd64 dom0, and there is a NetBSD i386PAE
guest and an NetBSD amd64 running just fine. I am using bridge0 to
connect xvifN.0 to the real interface, uneventfully. This is 3.3:
xentools33-3.3.1nb6 Userland Tools for Xen 3.3.x
xenkernel33-3.3.1nb1 Xen 3.3.1 Kernel
I am trying to install a Debian guest. Here is my config file, with the
real name replaced by foobar.
----------------------------------------
# -*- mode: python; -*-
#
ftp://ftp.debian.org/debian/dists/lenny/main/installer-i386/current/images/netboot/xen/vmlinuz
kernel = "/n0/xen/foobar.kernel"
#
ftp://ftp.debian.org/debian/dists/lenny/main/installer-i386/current/images/netboot/xen/initrd.gz
ramdisk = "/n0/xen/foobar.initrd"
memory = 256
name = "foobar"
vif = [ 'mac=aa:00:00:4b:00:03,bridge=bridge0' ]
disk = [ 'file:/n0/xen/foobar-wd0,xvda,w' ]
# from
ftp://ftp.debian.org/debian/dists/lenny/main/installer-i386/current/images/netboot/xen/xm-debian.cfg
root = "xvda"
# needed?
console = "hvc0"
autorestart = True
----------------------------------------
The problem seems to be that the network on the domU doesn't work.
xm network-list shows:
Idx BE MAC Addr. handle state evt-ch tx-/rx-ring-ref BE-path
0 0 aa:00:00:4b:00:03 0 1 -1 -1 /-1
/local/domain/0/backend/vif/25/0
my working (netbsd) domU shows
Idx BE MAC Addr. handle state evt-ch tx-/rx-ring-ref BE-path
0 0 aa:00:00:4b:00:01 0 4 7 509 /508
/local/domain/0/backend/vif/4/0
in the domU, I get a failure to obtain DHCP address and:
# ip address
1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
tcpdump on the xvif on dom0 shows no activity.
In the domU's /var/log/console I see (cut/paste from more):
Apr 1 15:57:43 kernel: [ 0.215561] registered taskstats version 1
Apr 1 15:57:43 kernel: [ 0.215573] XENBUS: Device with no driver:
device/vbd/51712
Apr 1 15:57:43 kernel: [ 0.215579] XENBUS: Device with no driver:
device/vif/0
sole/0 0.215584] XENBUS: Device with no driver:
device/con--More-- (53% of 20221 bytes)
Apr 1 15:57:43 kernel: [ 0.215601] drivers/rtc/hctosys.c: unable to open
rtc device (rtc0)
Apr 1 15:57:43 kernel: [ 0.215706] Freeing unused kernel memory: 256k freed
Apr 1 15:57:43 kernel: [ 0.359036] Initialising Xen virtual ethernet driver.
Apr 1 15:57:43 kernel: [ 0.360004] net eth0: backend does not support
copying rece
Apr 1 15:57:43 kernel: ive path
Apr 1 15:57:43 kernel: [ 10.456019] XENBUS: Timeout connecting to device:
device/vif/0 (state 1)
Apr 1 15:57:43 kernel: [ 10.524695] thermal: Unknown symbol
acpi_processor_set_thermal_limit
Apr 1 15:57:43 init: init: starting pid 521, tty '': '/sbin/reopen-console
/sbin/debian-installer'
Apr 1 15:57:43 init: init: starting pid 533, tty '/dev/tty4': '/usr/bin/tail
-f /var/log/syslog'
Apr 1 15:57:44 debconf: Setting debconf/language to en
Trying this on NetBSD i386 4.0 with xen 3.1.2 got me:
Error: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')
On 4.99.72 amd with xen 3.1.2, I got a similar invalid loader complaint.
I then tried the linux kernel from xen.org. It can talk to the net
fine, but seems unhappy with the debian ramdisk.
Any clues appreciated.
Attachment:
pgpaMyMowHVnR.pgp
Description: PGP signature