public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Mailand <martin@tuxadero.com>
To: Simon Chen <simonchennj@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: weird packet loss between two VMs
Date: Mon, 05 Mar 2012 18:43:42 +0100	[thread overview]
Message-ID: <4F54FB4E.8040000@tuxadero.com> (raw)
In-Reply-To: <CANj2EbczGGp3sFSTFyygE8PAou3g+5pvhPwERjQvAfngypoO9A@mail.gmail.com>

Hi Simon,
you are using a 100Mbits nic and you try to send with 600M, try a 
1000Mbits on the sending site as well.

-martin

Am 05.03.2012 00:57, schrieb Simon Chen:
> For the two VMs, one is using 100M VNIC, the other is using 1000M one.
> The vnet interfaces for the two VMs are put on two bridges on the two
> servers, both tap into the second vlan. I then run iperf to send UDP
> packets from the 100M VM to the 1000M VM using the following
> parameter:
> iperf -c 10.6.6.17 -t 30 -i 2 -r -b 600M


      reply	other threads:[~2012-03-05 17:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-04 23:57 weird packet loss between two VMs Simon Chen
2012-03-05 17:43 ` Martin Mailand [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=4F54FB4E.8040000@tuxadero.com \
    --to=martin@tuxadero.com \
    --cc=kvm@vger.kernel.org \
    --cc=simonchennj@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox