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

Re: [Xen-users] No eth0 in domU...

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Jerry Amundson" <jamundso@xxxxxxxxx>
  • Date: Sat, 24 Feb 2007 12:54:52 -0600
  • Delivery-date: Sat, 24 Feb 2007 10:54:14 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=sD5fEmAoM/AAAXOx/pRmMS82EqHytkMV0VjzeMwVHOo+3rri0z+rss46FwpVteMaBne++wOqTGFvdJx7KRYNWPpKFmyWCNGPgVdGJynV51nYx3ytUeAfBGXMc3E93NisSyF6eQW+xavMvVV+bkVx04/TjgIhfn185x7421PGDYA=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On 2/24/07, Kraska, Joe A (US SSA) <joe.kraska@xxxxxxxxxxxxxx> wrote:

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?

Yes, but why? Having it there keeps the install "more normal"...


"Pay no attention to that man behind the curtain!"

Xen-users mailing list



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