From: Dennis Jacobfeuerborn <dennisml@conversis.de>
To: lartc@vger.kernel.org
Subject: Re: Ghost traffic seen in all guest on a kvm hypervisor
Date: Mon, 24 Mar 2014 10:34:38 +0000 [thread overview]
Message-ID: <53300A3E.5050900@conversis.de> (raw)
In-Reply-To: <532F9111.2050507@conversis.de>
Hi Remy,
the only physical interface used is eth0 but I'm using vlans so the
interface connected to the bridge is eth0.8 and all the guests are
connected to this bridge as well. The output of ethtool -k for both eth0
and eth0.8 is:
Offload parameters for eth0.8:
rx-checksumming: on
tx-checksumming: on
scatter-gather: on
tcp-segmentation-offload: on
udp-fragmentation-offload: off
generic-segmentation-offload: on
generic-receive-offload: off
large-receive-offload: off
Regards,
Dennis
On 24.03.2014 07:00, Remy Mudingay wrote:
> Hi Dennis,
>
> Please post the KVM bridge topology and also the output of ethtool -k ethX (for each real nic).
>
> Cheers,
>
> Remy
>
>
> Sent from my Phone
>
>> On 24 Mar 2014, at 02:57, Dennis Jacobfeuerborn <dennisml@conversis.de> wrote:
>>
>> Hi,
>> I have a problem on a kvm hypervisor that I cannot explain. It appears that some traffic shows up in the interface monitoring in all of the guests on that hypervisor. We are not using broadcasts in any way and I see peaks of 100mbit for several minutes on all of these systems.
>>
>> Does anybody have an idea what could cause this?
>>
>> Regards,
>> Dennis
>> --
>> To unsubscribe from this list: send the line "unsubscribe lartc" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-03-24 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 1:57 Ghost traffic seen in all guest on a kvm hypervisor Dennis Jacobfeuerborn
2014-03-24 6:00 ` Remy Mudingay
2014-03-24 7:04 ` Wolfgang Hennerbichler
2014-03-24 10:34 ` Dennis Jacobfeuerborn [this message]
2014-03-24 10:45 ` Dennis Jacobfeuerborn
2014-03-24 11:32 ` Joel Gerber
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=53300A3E.5050900@conversis.de \
--to=dennisml@conversis.de \
--cc=lartc@vger.kernel.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.