From: Peter Lieven <pl@kamp.de>
To: Yan Vugenfirer <yvugenfi@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>, Tobias Schmidt <ts@kamp.de>,
Vadim Rozenfeld <vrozenfe@redhat.com>,
Lukas Friedrichs <lf@kamp.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Windows2012R2 virtio-win drivers and IPv6
Date: Tue, 16 Jun 2015 14:33:58 +0200 [thread overview]
Message-ID: <558017B6.3010206@kamp.de> (raw)
In-Reply-To: <0F7ECCC9-62AA-4939-A1A1-3F46E6558278@redhat.com>
Hi Yan,
thanks for the reply.
>
> * When you experience the issues is it between VMs on the same host?
I can reproduce it between a Windows VM on Host A and a Linux VM on Host B.
Linux and Windows are not on the same host systems due to licensing.
Between Linux VMs and/or if I download to the Windows VM there is no issue.
Only outbound TCP traffic from the Windows vServer is affected and it only affects IPv6 traffic.
>
> * Can you describe your host network configuration?
Windows VM on Qemu -> tap -> Linux Bridge -> eth (tagged) -> Network -> eth(tagged) -> Linux Bridge -> tap -> Linux VM on Qemu.
>
> * Can provide the output for "ethtool -k” for every NIC (including tap devices) in the host that is involved with the VM that has a problem?
Offload parameters for tap4:
rx-checksumming: off
tx-checksumming: on
scatter-gather: on
tcp-segmentation-offload: off
udp-fragmentation-offload: off
generic-segmentation-offload: on
generic-receive-offload: on
large-receive-offload: off
rx-vlan-offload: off
tx-vlan-offload: on
ntuple-filters: off
receive-hashing: off
Offload parameters for br136:
rx-checksumming: off
tx-checksumming: on
scatter-gather: on
tcp-segmentation-offload: off
udp-fragmentation-offload: off
generic-segmentation-offload: on
generic-receive-offload: on
large-receive-offload: off
rx-vlan-offload: off
tx-vlan-offload: on
ntuple-filters: off
receive-hashing: off
Offload parameters for eth2:
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
rx-vlan-offload: on
tx-vlan-offload: on
ntuple-filters: off
receive-hashing: off
>
> * What are the host kernel version, QEMU version and guest driver version you are using?
host: 3.13.0-53-generic
qemu: 2.2.1
guest dirver: 0.1.100
Thank You,
Peter
prev parent reply other threads:[~2015-06-16 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 14:07 [Qemu-devel] Windows2012R2 virtio-win drivers and IPv6 Peter Lieven
2015-05-28 14:24 ` Vadim Rozenfeld
2015-06-08 8:12 ` Peter Lieven
2015-06-10 7:49 ` Yan Vugenfirer
2015-06-16 12:33 ` Peter Lieven [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=558017B6.3010206@kamp.de \
--to=pl@kamp.de \
--cc=gleb@redhat.com \
--cc=lf@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=ts@kamp.de \
--cc=vrozenfe@redhat.com \
--cc=yvugenfi@redhat.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;
as well as URLs for NNTP newsgroup(s).