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: "Andy Burns" <xen.lists@xxxxxxxxxxx>
Subject: Re: [Xen-users] Network is unreachable
From: Thomas <iamkenzo@xxxxxxxxx>
Date: Tue, 2 Sep 2008 23:42:51 +0200
Cc: Xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 02 Sep 2008 14:43:26 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=iYXcaUCKva+agbNNpV402TM9Bt77jeQA/0s6Hrgi0oY=; b=XQprBiEmoJdH5j2knhsn9L6j98iFlltqxpw0r7qpTphn7X4WPOWPYgqbCtL+OzJLr1 yaogdGbrH8CAYQoo7QeyVYhZCyRg48SpAALvQyNjHVRy8SSHoPKNTgKvRtnBRsEeQHd2 GzyXSdfr3pLZh6c/2Jv+SbynsDFYp//32sZuI=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=TaLD9EZsgigi8FyXBUCxGFhq0QYorpv0g6NJPD0sXFGGgkRSGAM0iRRBN1THTu6m7Y 53QXOto+4Z6K7GGfDihZvPzu4RpPA7wTju3hQ44yKeOqcIpBIiuTBkTY/a6B4ug6cGd4 MMMZfZ4S1Vt/4NMiNXJImbMwL5nMX9Jweag4k=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <b4057d410809021435r20fe101dxe6962ef912c8c22c@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> <b4057d410809021435r20fe101dxe6962ef912c8c22c@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> 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.
The domU is PV. The domU works perfectly apart the network.


> 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?
Yes exactly. I have heard scary things about pygrub, so I want to
install all kernels in dom0.

>> 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,
What I meant, is that if I install additional packaged kernels in my
dom0, could the dom0 get broken? because that already happened to me
in the past, when I installed by mistake
xen-linux-system-2.6.18-5-xen-amd64, it completely destroyed my dom0,
and I had to reinstall the server from scratch, so I don't want to get
into this anymore.

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