xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Xu, Quan" <quan.xu@intel.com>
To: Jan Beulich <JBeulich@suse.com>, "Hao, Xudong" <xudong.hao@intel.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
	Wei Liu <wei.liu2@citrix.com>,
	"Zhang, PengtaoX" <pengtaox.zhang@intel.com>
Subject: Re: [BUG] win2008 guest cannot get ip through sriov
Date: Wed, 8 Jun 2016 09:12:26 +0000	[thread overview]
Message-ID: <945CA011AD5F084CBEA3E851C0AB28894B8D1485@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <575698C002000078000F272A@prv-mh.provo.novell.com>

On June 07, 2016 3:50 PM, Jan Beulich <JBeulich@suse.com> wrote:
> >>> On 07.06.16 at 07:52, <quan.xu@intel.com> wrote:
> > -vf PT is not working for win2008: the logs:
> >    qemu-dm-win2k8.log -- qemu log, vf PT for win2008.
> >    xen-win2k8.log -- xen log, vf PT for win2008.
> 
> Hmm, that's very little output. In particular neither qemu nor Xen see _any_
> writes to the MSI-X table (without which interrupts obviously can't get
> enabled for that device).
> 
> Albeit - even in the SLES case only qemu sees such writes, so I'll have to check
> if I made a mistake with the debugging patch.
> 

Jan,  do you have any other suggestions on how could I dig into this issue?

Quan

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  parent reply	other threads:[~2016-06-08  9:12 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
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 [this message]
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=945CA011AD5F084CBEA3E851C0AB28894B8D1485@SHSMSX101.ccr.corp.intel.com \
    --to=quan.xu@intel.com \
    --cc=JBeulich@suse.com \
    --cc=pengtaox.zhang@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).