From: Stefan Assmann <sassmann@redhat.com>
To: jacob jacob <opstkusr@gmail.com>
Cc: kvm-devel <kvm@vger.kernel.org>,
netdev@vger.kernel.org, Shannon Nelson <shannon.nelson@intel.com>,
Alex Williamson <alex.williamson@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Bandan Das <bsd@redhat.com>
Subject: Re: [Qemu-devel] PCI passthrough of 40G ethernet interface (Openstack/KVM)
Date: Mon, 23 Mar 2015 08:19:12 +0100 [thread overview]
Message-ID: <550FBE70.40201@redhat.com> (raw)
In-Reply-To: <CA+AkT2jPV_P436_RUQepT7wHtPaGOYGeE5uzUKtyXtk0s8U_gQ@mail.gmail.com>
On 20.03.2015 21:55, jacob jacob wrote:
> On Thu, Mar 19, 2015 at 10:18 AM, Stefan Assmann <sassmann@redhat.com> wrote:
>> On 19.03.2015 15:04, jacob jacob wrote:
>>> Hi Stefan,
>>> have you been able to get PCI passthrough working without any issues
>>> after the upgrade?
>>
>> My XL710 fails to transfer regular TCP traffic (netperf). If that works
>> for you then you're already one step ahead of me. Afraid I can't help
>> you there.
>
> I have data transfer working when trying the test runs on the host
> itself. Are you seeing problems when directly trying the TCP traffic
> from the host itself?
Correct.
> The issues that i am seeing are specific to the case when the devices
> are passed via PCI passthrough into the VM.
>
> Any ideas whether this would be a kvm/qemu or i40e driver issue?
> (Updating to the latest firmware and using latest i40e driver didn't
> seem to help.)
Hard to say, that's probably something for Intel to look into.
Stefan
next prev parent reply other threads:[~2015-03-23 7:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 16:17 [Qemu-devel] PCI passthrough of 40G ethernet interface (Openstack/KVM) jacob jacob
2015-03-12 16:26 ` Alex Williamson
2015-03-12 16:36 ` jacob jacob
2015-03-12 19:07 ` Bandan Das
2015-03-12 23:11 ` jacob jacob
2015-03-13 0:02 ` Bandan Das
2015-03-13 14:08 ` jacob jacob
2015-03-16 16:31 ` jacob jacob
2015-03-16 18:12 ` Bandan Das
2015-03-16 18:24 ` jacob jacob
2015-03-16 19:49 ` Bandan Das
2015-03-16 19:58 ` jacob jacob
2015-03-18 15:24 ` Bandan Das
2015-03-18 15:40 ` jacob jacob
2015-03-18 22:01 ` Shannon Nelson
2015-03-18 22:06 ` Shannon Nelson
2015-03-19 8:15 ` Stefan Assmann
2015-03-19 14:00 ` jacob jacob
2015-03-19 14:04 ` jacob jacob
2015-03-19 14:18 ` Stefan Assmann
2015-03-20 20:55 ` jacob jacob
2015-03-23 7:19 ` Stefan Assmann [this message]
2015-03-24 14:13 ` jacob jacob
2015-03-24 14:53 ` Shannon Nelson
2015-03-24 15:04 ` jacob jacob
2015-03-26 1:00 ` Shannon Nelson
2015-03-19 16:26 ` Shannon Nelson
2015-03-19 21:04 ` jacob jacob
2015-03-19 21:42 ` Shannon Nelson
2015-03-19 21:53 ` jacob jacob
2015-03-19 23:37 ` jacob jacob
-- strict thread matches above, loose matches on Subject: below --
2015-03-12 16:11 jacob jacob
2015-03-12 16:13 ` jacob jacob
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=550FBE70.40201@redhat.com \
--to=sassmann@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=bsd@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=opstkusr@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=shannon.nelson@intel.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).