From: Michal Novotny <minovotn@redhat.com>
To: xen-devel@lists.xensource.com
Subject: Re: Big network problem on recent kernel update fromxen/stable2.6.32.x
Date: Mon, 07 Jun 2010 17:11:09 +0200 [thread overview]
Message-ID: <4C0D0C0D.2040004@redhat.com> (raw)
In-Reply-To: <20100607150429.GK17817@reaktio.net>
On 06/07/2010 05:04 PM, Pasi Kärkkäinen wrote:
> On Mon, Jun 07, 2010 at 09:53:09AM -0400, djmagee@mageenet.net 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
>
>
The bridge is one automatically created using the xen daemon but the
configuration broke now when I rebooted so I need to make it working
first since now even `xm list` is not working and the xend.log is
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 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@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>
>> _______________________________________________
>> 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
>
--
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat
next prev parent reply other threads:[~2010-06-07 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 13:19 Big network problem on recent kernel update from xen/stable2.6.32.x Fantu
2010-06-07 13:53 ` Big network problem on recent kernel update fromxen/stable2.6.32.x djmagee
2010-06-07 15:04 ` Pasi Kärkkäinen
2010-06-07 15:11 ` Michal Novotny [this message]
2010-06-07 16:20 ` Big network problem on recent kernel updatefromxen/stable2.6.32.x djmagee
2010-06-09 14:45 ` Big network problem on recent kernel update from xen/stable2.6.32.x Fantu
2010-06-09 15:13 ` Pasi Kärkkäinen
2010-06-09 18:31 ` Jeremy Fitzhardinge
2010-06-09 22:48 ` Big network problem on recent kernel update fromxen/stable2.6.32.x djmagee
2010-06-10 1:26 ` Big network problem on recent kernel update from xen/stable2.6.32.x Xu, Dongxiao
2010-06-10 5:59 ` Pasi Kärkkäinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C0D0C0D.2040004@redhat.com \
--to=minovotn@redhat.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.