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

[Xen-users] Missing Device eth0

  • To: <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Venefax" <venefax@xxxxxxxxx>
  • Date: Sat, 6 Dec 2008 08:58:14 -0500
  • Delivery-date: Sat, 06 Dec 2008 05:59:44 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :content-language; b=rtDRrgPubsHGeHYfTU3Wg2ZzzFxxtUyexKzXx9zo+i85d0IJYPtXr9vi02Gku4T/+N 59nDcWt21LgXALw394Rls8BObUWr0r0wmIH5KYtQAYsMZc2riJiEfPwgaqGrfLs09cTs b3c8CMyaCEBxygWrPmGgQsGWyteMpN2JLQq2U=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AclXXd21CvEq0agvS+ylmSaL17q1RgATI+eQ

One of my virtual para-virtualized machines has no eth0. Where is it defined in 
the virtual disk? The machine definition file is correct, it has valid 
configuration for device vif. I need to understand how to fix this when it 

if I type service network restart, it says
device eth0 does not seem to be present, delaying initialization

also of I type 
ifconfig eth0
it says:
eth0: error fetching interface information: Device not found

if delete the virtual machine and rebuild it, it does not get fixed, so the 
problem is inside the virtual disk.

I use a Suse 10 SP2 as host and Centos 5.2 64 bits as Guest.

Xen-users mailing list



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