WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Network is unreachable

To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Network is unreachable
From: "Andy Burns" <xen.lists@xxxxxxxxxxx>
Date: Tue, 2 Sep 2008 22:35:46 +0100
Cc:
Delivery-date: Tue, 02 Sep 2008 14:36:21 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=BG6xD6Dd8CUeeVhL0Ouu5zbvcgT4bHhO5HxzRgmulI4=; b=SUkO2+/16+yae1hfTlgHZH3qENGaACyDIXBV6TUhPbMWZZUPtTMqndMYyBEAxfOE6c UdZ+9fCPS9KRMlYQG6qnec9mqklXF33oa5gAAf8Weqct1iIrOMyHK7g6Os/fYraadQet ACZdGa0RON3Is3gemBLnYxUM6zG87ewKDYQO0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=ELt/xel7OEIRmdbHLTlUdXHh1O4HqarYs8f/V0lWt/0Wn0mFN8axFrtNu4LoCTUPoZ Kopa5NnukXv7pBY82xGEKwy1D8XJbWDFN89wSy8UOLvo+CDufLDDYbpbPFgu4F+p110R CLlGrVYxeI8J7FdHxSUHJ5yIqMnkFY208LJ/I=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <55da14450809021426u4cd973e9q60729ab3bb5e36f4@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <55da14450809021313v48f2c2e3ub640729b23cb1e20@xxxxxxxxxxxxxx> <49627735003F5C479100225C339F9FE0D4DF2FC825@xxxxxxxxxxxxxxxxxxxxxx> <55da14450809021326t3cf69326v1e03cb3401243160@xxxxxxxxxxxxxx> <b4057d410809021334v69b076fdybb4131b5309710d2@xxxxxxxxxxxxxx> <55da14450809021342n13cadfc9i8c5d2163e2193eb2@xxxxxxxxxxxxxx> <b4057d410809021400v3d3c6ad2v8a3439d12c076bf2@xxxxxxxxxxxxxx> <55da14450809021415i7e14ca82q2736c86af4233950@xxxxxxxxxxxxxx> <55da14450809021426u4cd973e9q60729ab3bb5e36f4@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
2008/9/2 Thomas <iamkenzo@xxxxxxxxx>:

> I have found in a mailing-list someone saying that the Debian xen
> kernels are not geared towards domU as they lack the xennet module.
> Unfortunately I can't the link anymore.

Can I double check the domU is a PV domain, not an HVM domain? Apart
from lack of networking the domU works? If so, seems strange that the
Debian kernel has xenblk but not xennet.

> By the way on my dom0 I use a custom 2.6.21 kernel. Is it safe to run
> "sudo aptitude install linux-image-2.6.18-6-xen-amd64"??? I want to
> install a kernel on dom0 so that domU can use it when it boots.

So you specify your own kernel/initrd in the domU config rather
installing the 2.6.18 domU kernel inside /boot of the domU and then
using pygrub?

> However I am wondering if doing so could wreck my dom0 distro?

I don't think the problem is with your dom0, just that the domU
doesn't have the xennet driver,

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users