From: "Jan Beulich" <JBeulich@suse.com>
To: Quan Xu <quan.xu@intel.com>
Cc: Xudong Hao <xudong.hao@intel.com>, Wei Liu <wei.liu2@citrix.com>,
PengtaoX Zhang <pengtaox.zhang@intel.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [BUG] win2008 guest cannot get ip through sriov
Date: Thu, 02 Jun 2016 03:03:50 -0600 [thread overview]
Message-ID: <5750129602000078000F0C78@prv-mh.provo.novell.com> (raw)
In-Reply-To: <945CA011AD5F084CBEA3E851C0AB28894B8C4A64@SHSMSX101.ccr.corp.intel.com>
>>> On 02.06.16 at 09:31, <quan.xu@intel.com> wrote:
> On May 27, 2016 10:06 PM, Jan Beulich <JBeulich@suse.com> wrote:
>> >>> On 27.05.16 at 15:34, <wei.liu2@citrix.com> wrote:
>> > On Fri, May 27, 2016 at 06:16:30AM -0600, Jan Beulich wrote:
>> >> >>> On 27.05.16 at 12:39, <wei.liu2@citrix.com> wrote:
>> >> > Is this a regression? Does it work on previous versions of Xen?
>> >>
>> >> I think this is what was already reported by other Intel people, see
>> >> e.g. Quan's most recent reply:
>> >> http://lists.xenproject.org/archives/html/xen-devel/2016-05/msg01896.
>> >> html It is not clear where the problem is, and not seeing the issue
>> >> myself makes it hard to analyze. In any event this quite likely is a
>> >> regression.
>> >>
>> >
>> > My reading of that email thread and all relevant links (including the
>> > KVM bug report) is that there is a regression vf driver, but not in Xen.
>>
>> Just from reading that I would tend to agree. But the report here is about
>> Win2K8.
>
> Do you know which commit is a regression one? I try to find out the
> regression commit. That may be helpful to find out the root cause.
Indeed. There was a lot of rework of MSI-X. Iirc one of your
colleagues had actually narrowed it down a while ago, but I can't
seem to find that mail right now. Nor did it really help understand
what's going wrong (or else we would likely have found a fix for it
already). My primary suspicion was that the interrupt doesn't get
enabled when it should, but the respective fix didn't help that
case (while it did help others). Hence my continued request for
someone being able to observe the problem to simply log guest
actions and what the hypervisor does for them (plus of course
provide all relevant debug information, like debug key output of
interest, for a guest in the broken state).
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-02 9:03 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 [this message]
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
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=5750129602000078000F0C78@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).