This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Trouble getting a DHCP address when booting.

To: <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Trouble getting a DHCP address when booting.
From: "JHJE (Jan Holst Jensen)" <jhje@xxxxxxxxxxxxxxx>
Date: Fri, 18 Mar 2005 17:18:57 +0100
Delivery-date: Fri, 18 Mar 2005 16:20:59 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Thread-index: AcUr1i/W4++ctZP0TVicjzJ0kb7tww==
Thread-topic: Trouble getting a DHCP address when booting.

I spawned a thread last week about the failure of bridged networking and
I have gotten a little further. Turns out that I _do_ have network
connectivity from inside the domains, but I cannot get the network to
come up when I boot. I have to login and start up the network manually.

E.g. after installing Debian Sarge according to the debootstrap method
outlined in the users manual, I created a config file that goes like

  xen-test:~# cat debian.xen
  kernel = "/boot/vmlinuz-2.4.29-xenU"
  memory = 256
  name = "Debian-Sarge"
  nics = 1
  dhcp = "dhcp"
  disk = ["file:/root/debian.sarge,sda1,w"]
  root = "/dev/sda1 ro"

When I start this, the domain hangs upon trying to get a DHCP address:

xen-test:~# xm create debian.xen -c
Using config file "debian.xen".
Started domain Debian-Sarge, console on port 9610
************ REMOTE CONSOLE: CTRL-] TO QUIT ********
Linux version 2.4.29-xenU (xenod@xxxxxxxxxxxxxxxxxxxxx) (gcc version
3.3.3 20040412 (Red Hat Linux 3.3.3-7)) #1 Thu Mar 10 19:49:06 GMT 2005
On node 0 totalpages: 65536
zone(0): 4096 pages.
zone(1): 61440 pages.
zone(2): 0 pages.
Kernel command line:  ip=: root=/dev/sda1 ro
Initializing CPU#0
Xen reported: 1263.504 MHz processor.
Calibrating delay loop... 2523.13 BogoMIPS
Memory: 256912k/262144k available (1324k kernel code, 5232k reserved,
238k data, 60k init, 0k highmem)
Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode cache hash table entries: 16384 (order: 5, 131072 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 16384 (order: 4, 65536 bytes)
Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU: Intel(R) Pentium(R) III CPU family      1266MHz stepping 01
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
Journalled Block Device driver loaded
Installing knfsd (copyright (C) 1996 okir@xxxxxxxxxxxx).
Event-channel device installed.
Xen virtual console successfully installed as tty
xen_mem: Initialising balloon driver.
pty: 256 Unix98 ptys configured
xen_blk: Initialising virtual block device driver
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
SCSI subsystem driver Revision: 1.00
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
xen_net: Initialising virtual ethernet driver.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 32768)
Sending DHCP requests ...
************ REMOTE CONSOLE EXITED *****************

I exited the console, since it will hang here forever trying again and
again to obtain a DHCP address. It doesn't even respond to a Ctrl-C -
something that seems to be general for the Xen console (rather annoying
if you start e.g. 'ping' without a '-c' argument: the console is now

If however I uncomment the 'dhcp =' line in debian.xen and restart, it
boots in 5 seconds (Wow!) and I can log in and do 

  ifconfig lo up
  ifconfig eth0 up

and get a DHCP address without problems.

Any hints or solutions ?

Best regards
-- Jan Holst Jensen, Novo Nordisk A/S

SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>