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 problem

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Network problem
From: "Gino LV. Ledesma" <gledesma@xxxxxxxxx>
Date: Fri, 22 Apr 2005 12:04:54 -0700
Delivery-date: Fri, 22 Apr 2005 19:04:43 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=UwbSZPuabApmudv94NPCwKFjlYykTTrQd2cSqWOxljb/O8Lh4JyeX+U+nvCylg73qbZJQYGWUu4G0VnIchIITyqlGbpygoY4LDEbEezrjDkicANlbbqUtZYb/XgA+n2oCtP8fXpi0XbANQ8DTEMHetmNviHYKgXH9x5RphhL6oo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4268363B.8080201@xxxxxxxxxx>
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>
References: <e27bf7770504211329228e5758@xxxxxxxxxxxxxx> <42682D7C.4020109@xxxxxxxxxx> <e27bf777050421160467dd6571@xxxxxxxxxxxxxx> <4268363B.8080201@xxxxxxxxxx>
Reply-to: "Gino LV. Ledesma" <gledesma@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 4/21/05, Nivedita Singhvi <niv@xxxxxxxxxx> wrote:
> Gino LV. Ledesma wrote:
> 
> > I've managed to get the host and guest OSs talk to each other. I
> > needed to have one of them ping the other for a couple of seconds (is
> > this an ARP learning issue?). Now the next part, which is getting the
> 
> Hmm, there is a race window where the bridge doesn't get setup
> because the interface transfer doesn't happen in time, but that
> is not what you are seeing here. If the bridge seems to be up,
> they should ping themselves right away, the dom1->dom0 path is
> mostly fake.
> 
> I'd be interested in finding out if that is a persistent problem..

Sorry... This was a fluke on my part. I was running Xen within VMware,
and apparently, vmnet only bridges the guest OS's interface to the
host's interface. After installing Xen on another dedicated machine
(without LVM -- which was why I didn't install it on my box earlier),
everything worked out great out of the box.

Thanks for the support.

gino

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

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