From: "Jan Beulich" <JBeulich@suse.com>
To: Quan Xu <quan.xu@intel.com>, Xudong Hao <xudong.hao@intel.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>,
PengtaoX Zhang <pengtaox.zhang@intel.com>
Subject: Re: [BUG] win2008 guest cannot get ip through sriov
Date: Tue, 07 Jun 2016 01:43:11 -0600 [thread overview]
Message-ID: <5756972F02000078000F271F@prv-mh.provo.novell.com> (raw)
In-Reply-To: <945CA011AD5F084CBEA3E851C0AB28894B8C6CBD@SHSMSX101.ccr.corp.intel.com>
>>> On 07.06.16 at 08:07, <quan.xu@intel.com> wrote:
> On June 07, 2016 1:52 PM, Xu, Quan <quan.xu@intel.com> wrote:
>> On June 02, 2016 8:09 PM, Jan Beulich <JBeulich@suse.com> wrote:
>>
>
> Sorry, this below part is about NIC PF pass-through for win2008..
>
>> btw, when I updated the NIC driver for win2008, actually, it is working.
>> Xudong, could you help me verify it again?
>>
>> ((
>> xen commit: bbfd2d6ccb31a3aeea49c8f9c7884792ddc26e3b
>> NIC: Intel Corporation I350 Gigabit Network Connection
>> new win2k8 NIC
>> driver ,https://downloadcenter.intel.com/download/18720/Network-
>> Adapter-Driver-for-Windows-Server-2008-Final-Release?product=59679
>> ))
>>
>> qemu-dm-TestDom.log -- qemu log, pf PT for win2008.
Okay, but could you please make explicit what works and what
doesn't? I.e. do I take this to mean a passed through PF does
work (at least with the newer driver, maybe also with an older
one), while a passed through VF doesn't work (regardless of
driver version)? Especially with you (earlier) suspecting a driver
issue, precise information here is quite relevant.
Thanks, Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-07 7:43 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 9:04 [BUG] win2008 guest cannot get ip through sriov Zhang, PengtaoX
2016-05-27 10:39 ` Wei Liu
2016-05-27 12:16 ` Jan Beulich
2016-05-27 13:34 ` Wei Liu
2016-05-27 14:06 ` Jan Beulich
2016-06-02 7:31 ` Xu, Quan
2016-06-02 9:03 ` Jan Beulich
2016-06-02 10:22 ` Wei Liu
2016-06-02 10:38 ` Jan Beulich
2016-06-02 11:03 ` Wei Liu
2016-06-02 12:08 ` Jan Beulich
2016-06-02 13:05 ` Xu, Quan
2016-06-02 13:30 ` Jan Beulich
2016-06-02 14:02 ` Xu, Quan
2016-06-07 5:52 ` Xu, Quan
2016-06-07 6:07 ` Xu, Quan
2016-06-07 7:43 ` Jan Beulich [this message]
2016-06-07 7:49 ` Jan Beulich
2016-06-07 8:03 ` Xu, Quan
2016-06-07 8:08 ` Jan Beulich
2016-06-07 8:19 ` Xu, Quan
2016-06-08 9:12 ` Xu, Quan
2016-06-08 9:25 ` Jan Beulich
2017-10-27 7:27 ` Hao, Xudong
2017-10-27 8:37 ` Jan Beulich
2017-10-27 8:58 ` Hao, Xudong
2017-10-27 10:41 ` Julien Grall
2017-10-27 20:16 ` Stefano Stabellini
2017-11-02 13:49 ` Julien Grall
2017-11-03 1:10 ` Hao, Xudong
2017-11-03 11:23 ` Roger Pau Monné
2017-11-06 1:04 ` Hao, Xudong
2017-11-07 9:33 ` Roger Pau Monné
2017-11-09 0:22 ` Hao, Xudong
2017-11-09 9:27 ` Roger Pau Monné
2017-11-09 14:36 ` Julien Grall
2017-11-09 14:37 ` Julien Grall
2017-11-27 3:20 ` Hao, Xudong
2017-11-27 10:39 ` Julien Grall
2017-11-06 1:07 ` Hao, Xudong
2017-11-08 12:13 ` Anthony PERARD
2017-11-08 12:17 ` Julien Grall
2017-10-30 1:04 ` Hao, Xudong
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=5756972F02000078000F271F@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=pengtaox.zhang@intel.com \
--cc=quan.xu@intel.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
--cc=xudong.hao@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).