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] Big network problem on recent kernel update fromxen/stab

To: djmagee@xxxxxxxxxxxx
Subject: Re: [Xen-devel] Big network problem on recent kernel update fromxen/stable2.6.32.x
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Mon, 7 Jun 2010 18:04:29 +0300
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Fantu <fantonifabio@xxxxxxxxxx>
Delivery-date: Mon, 07 Jun 2010 08:09:43 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <EECC125FCE18E740AF561189E1260285052562@xxxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <28805128.post@xxxxxxxxxxxxxxx> <EECC125FCE18E740AF561189E1260285052562@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Mon, Jun 07, 2010 at 09:53:09AM -0400, djmagee@xxxxxxxxxxxx wrote:
> I discovered the same issue, with PV drivers only.  On Xen 3.4.3 and
> 4.0.0, I experienced the same problems.  Using one fully HVM linux domu,
> and fully PV linux domu, and one windows domu with gplpv drivers, I
> tested a 2.6.32.13 build from two weeks ago, and a 2.6.32.15 build from
> Saturday with the same config.  PV network does not work properly with
> 2.6.32.15, but qemu emulated device in the HVM domain without PV drivers
> works fine.  All three work just fine with 2.6.32.13.  Symptom is that
> packets never seem to get back to the domu.  For example, I have VMs on
> 192.168.2.0/24 subnet, and dom0 routes traffic to local physical net on
> 192.168.1.0/24.  If I ping 192.168.1.1 from a domu with PV drivers, I
> can see the echo request and reply in tcpdump on the bridge device on
> dom0, but domu does not seem to see the reply.  In some other cases,
> domu sees the reply, but reports 999-1001ms response times, which I know
> are inaccurate by watching tcpdump output.  Traffic other than ICMP is
> completely unreliable; the packets that do get through have incredibly
> high latency.  I'm 100% sure I don't have iptables or other network
> config problems.
> 

What bridge are you using? Is it virbr0, or some bridge with a physical NIC 
attached to it? 

-- Pasi

> 
> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Fantu
> Sent: Monday, June 07, 2010 9:20 AM
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-devel] Big network problem on recent kernel update
> fromxen/stable2.6.32.x
> 
> 
> I see only today how with last build of kernel do from last commit
> (27ed1b0e0dae5f1d5da5c76451bc84cb529128bd) do network of windows xp domU
> with gplpv 0.11.0.213 unusable, ping lost or over 1 second unable to
> connect
> with rdp to domU, unable to use network from domU and viceversa
> Also with build with 2.6.32.14 (from commit
> e8734951b7a8d838050277696541a7e57183bdce) have problem
> but my last build with 2.6.32.13 not have network problem, I can not
> remember committing but i have build on 26 may if just remember
> All these build have same config: 
> http://old.nabble.com/file/p28805128/config-2.6.32.15 config 
> -- 
> View this message in context:
> http://old.nabble.com/Big-network-problem-on-recent-kernel-update-from-x
> en-stable2.6.32.x-tp28805128p28805128.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

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