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-users] No eth0 in domU...

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] No eth0 in domU...
From: "Kraska, Joe A \(US SSA\)" <joe.kraska@xxxxxxxxxxxxxx>
Date: Sat, 24 Feb 2007 10:48:53 -0800
Delivery-date: Sat, 24 Feb 2007 10:48:19 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcdYRG4BWn2gXo6eRbmxHRUsR1agVQ==
Thread-topic: No eth0 in domU...
Ran across this problem recently. Below attached worked for me on a
reboot. Still gathering “low level linux administration expertise”
here. Would one alternative to the modprobe.conf be to recompile the
domU kernel such that it needs no such modprobe entry?
The problem here is that you need to add the following to your
modprobe.conf of your domU:
alias eth0 xennet
Adding this line will load the driver for your fc5 domU. Redhat compiles
the xennet driver as a module. So you have to load that module to see
the interface.


Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>