From: Peter Kieser <peter@kieser.ca>
To: kvm@vger.kernel.org
Cc: qemu-discuss@nongnu.org
Subject: Re: Unable to establish TCP sessions between guests using virtio-net on Linux 3.12 and above
Date: Fri, 27 Jun 2014 12:53:47 -0700 [thread overview]
Message-ID: <53ADCBCB.5060308@kieser.ca> (raw)
In-Reply-To: <53ADC3C2.5090201@kieser.ca>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
On 2014-06-27 12:19 PM, Peter Kieser wrote:
> Hello,
>
> Kernel versions tested: 3.13, 3.14, 3.15
> Related debian bug report:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738863
>
> I'm not sure if this is a problem specific to openvswitch or KVM. I
> have a network setup where I have one openvswitch bridge setup, with
> various ports with VLAN tags and a firewall running as a guest. After
> upgrading to Linux 3.13, all guests with virtio interfaces with TSO
> enabled (the default) are unable to establish TCP connections via the
> guest firewall. ICMP ping works fine. If I disable TSO on the vnet
> interfaces (as outlined in the bug report above) guests are then able
> to communicate with each other.
>
> Is there a patch for this issue that hasn't made it into mainline that
> I should test out? Is this an issue specific to KVM, or is it an
> openvswitch issue?
>
> Than kyou,
>
> -Peter
>
Hello,
Some further testing:
* Disabling vhost-net (vhost=off) for a particular VM has no effect to
this issue
* Changing from virtio to e1000 for the NIC completely resolves this issue
-Peter
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4504 bytes --]
prev parent reply other threads:[~2014-06-27 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 19:19 Unable to establish TCP sessions between guests using virtio-net on Linux 3.12 and above Peter Kieser
2014-06-27 19:53 ` Peter Kieser [this message]
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=53ADCBCB.5060308@kieser.ca \
--to=peter@kieser.ca \
--cc=kvm@vger.kernel.org \
--cc=qemu-discuss@nongnu.org \
/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.