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 problems

To: Xen User-List <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] network problems
From: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Date: Fri, 24 Jul 2009 08:55:43 +0700
Delivery-date: Thu, 23 Jul 2009 18:56:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A691070.80606@xxxxxxxxxxxx>
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: <4A67976D.1020502@xxxxxxxxxxxx> <4A691070.80606@xxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, Jul 24, 2009 at 8:37 AM, Mike Lovell<mike@xxxxxxxxxxxx> wrote:
> I tried setting an independent wallclock on all of the virtual machines. I
> also managed to miss that I had the wrong netmask configured for the vmnet
> bridge. It should have been 255.255.255.128. The vms were able to talk to
> each other before changing the netmask and I saw traffic flowing past the
> switch.
>
> Does anyone have any clue as to what might be going on? I am great need of
> some help here.

How well maintained is Debian's 2.6.26 xen kernel? xen.org's 2.6.18
kernel might work better for you. Or go the other way around, using
latest pv_ops kernel.

-- 
Fajar

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

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