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-devel

Re: [Xen-devel] HELP!!!! problem in connecting DomU with xen-2.0.5+linux

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] HELP!!!! problem in connecting DomU with xen-2.0.5+linux-2.4.29-xen0+linux-2.4.27-xenU
From: Xin Zhao <zhaoxin@xxxxxxxxxxxxxx>
Date: Sun, 1 May 2005 03:32:04 -0400 (EDT)
Delivery-date: Sun, 01 May 2005 07:31:58 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200505010712.j417CoXR026343@xxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <200505010712.j417CoXR026343@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Just got the network work for me.

I just did ifconfig vif?.0 up. Looks like the vif is not activated. Why?
My solution is apparently not a final solution. :(

-x


On Sun, 1 May 2005, zhaoxin wrote:

> Hi,
>
> I used to use xen 2.0.1 with linux-2.4.27-xen0/U. The network works fine for
> me. But after I switched to Xen 2.0.5, I failed to connect to DomU.
>
> I did ifconfig, I cannot even find the vif1.0 or something ilke that. What's
> wrong?
>
> My network setting is like this: two network cards on my machine, one has
> public IP 141.123.10.XX(eth0), the other has internal IP 192.168.0.1(eth1)
> The DomU IP is assigned to:  192.168.0.188
>
> Another question, I use eth1 to talk to DomU, but /etc/xen/script/network
> always put eth0 into xen-br0. Even if I manually change it, it will go back
> to eth0 after next xen source code compile and installation. It seems that
> xen installation will copy some files to overwrite the network file. How can
> I modify it to survive the new xen installation?
>
> Any advice is highly appreciated!
> -x
>

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

<Prev in Thread] Current Thread [Next in Thread>