From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Novotny Subject: Re: Big network problem on recent kernel update fromxen/stable2.6.32.x Date: Mon, 07 Jun 2010 17:11:09 +0200 Message-ID: <4C0D0C0D.2040004@redhat.com> References: <28805128.post@talk.nabble.com> <20100607150429.GK17817@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20100607150429.GK17817@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 06/07/2010 05:04 PM, Pasi K=E4rkk=E4inen wrote: > On Mon, Jun 07, 2010 at 09:53:09AM -0400, djmagee@mageenet.net wrote: > =20 >> 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 dom= u, >> 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 fro= m >> 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 drive= rs >> 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 o= n >> 192.168.2.0/24 subnet, and dom0 routes traffic to local physical net o= n >> 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 kn= ow >> 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. >> >> =20 > What bridge are you using? Is it virbr0, or some bridge with a physical= NIC attached to it? > > -- Pasi > > =20 The bridge is one automatically created using the xen daemon but the=20 configuration broke now when I rebooted so I need to make it working=20 first since now even `xm list` is not working and the xend.log is=20 completely empty :( Michal >> -----Original Message----- >> From: xen-devel-bounces@lists.xensource.com >> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Fantu >> Sent: Monday, June 07, 2010 9:20 AM >> To: xen-devel@lists.xensource.com >> 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 do= mU >> 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 >> --=20 >> 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@lists.xensource.com >> http://lists.xensource.com/xen-devel >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >> =20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > =20 --=20 Michal Novotny, RHCE Virtualization Team (xen userspace), Red Hat