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

[Xen-users] eth0 not brought up automatically

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Haavard Bjerke <havard.bjerke@xxxxxxx>
  • Date: Wed, 22 Mar 2006 10:58:56 +0100
  • Delivery-date: Wed, 22 Mar 2006 10:00:37 +0000
  • Domainkey-signature: a=rsa-sha1; c=nofws; s=beta; d=cern.ch; q=dns; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=I+Rof6wZtRzLlPK5sS0pRIk9H38N1icsHn4ixccUGNKeMoAESQLXEsNkQhcirkiZxDbDtkx+XaVKihZYYG+gAY3rGxEPOW4iVmKBB8ZvLt5Cf2/x5wh7a0wacGO3lnV3;
  • Keywords: CERN SpamKiller Note: -50 Charset: west-latin
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

When I boot domU, eth0 exists, but it is not up. Ie. I have to configure it manually, even though I have configured all the parameters in the domU config file:

gateway = "128.x.x.1"
vif = ['ip=128.x.x.100, mac=00:16:3E:00:00:11, bridge=xenbr0']
ip = "128.x.x.100"
hostname = "myhost"

If I look at the command line for domU ('cat /proc/cmdline') it contains 'ip=[...]:eth0:off'. Is it supposed to say 'eth0:on'?


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.