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

[Xen-users] eth0 does not exist when booting to xen kernel

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "John Morris" <frankenbean@xxxxxxxxx>
  • Date: Mon, 2 Jul 2007 08:29:48 -0400
  • Delivery-date: Mon, 02 Jul 2007 05:27:48 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=n90mSsjrt8bJKEOau8dn73I35giA1iBKcdaEBwT68N13Qi9FFZ5T94Tl+P8MMQIm+Y14Q6y0ybwwGRvoyKbcMXW1/LwVjQzGUp7tXZbdyuepcvfPMZaGGH6ZR5QUsNc/sf8yy8NPdqEaSKJ6UBoU/gTXuoUywbjFO8FxCTp2cRM=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi everyone. 

I am pretty new to xen, but am having an issue that I can't seem to crack.  I am running the 2-6-16 kernel on Debian Etch.  If I boot into the Etch kernel, everything works as it should.  When I boot into the Xen kernel, eth0 no longer exists. 

From what I understand, the network-bridge script will down my eth0, create a new virtual eth0 and bridge it into xenbr0

However, ifconfig only shows my lo and xenbr0 interfaces.  ifconfig -a lists all the veth devices and the vif devices, but still no eth0

/etc/xen/scripts/network-bridge status returns 'Device "eth0" does not exist.

lsmod shows that the e1000 driver is loaded. 

Can anyone shed some light?

Xen-users mailing list



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