[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [BUG] win2008 guest cannot get ip through sriov
This bug exist much long time, there are many discussion last year but not a solution then. I call out it now because there is a fix in qemu upstream: commit a8036336609d2e184fc3543a4c439c0ba7d7f3a2 Author: Roger Pau Monne <roger.pau@xxxxxxxxxx> Date: Thu Aug 24 16:07:03 2017 +0100 xen/pt: allow QEMU to request MSI unmasking at bind time The fix is not in qemu-xen tree yet, when will qemu-xen sync this fix? Is it possible to catch Xen 4.10's qemu-xen? BTW, mail report bug is direct but not easy to track, I took much time to search this BUG report mail. @Lars, is there plan to introduce any bug system for Xen? Thanks, -Xudong > -----Original Message----- > From: Xu, Quan > Sent: Wednesday, June 8, 2016 5:12 PM > To: Jan Beulich <JBeulich@xxxxxxxx>; Hao, Xudong <xudong.hao@xxxxxxxxx> > Cc: Wei Liu <wei.liu2@xxxxxxxxxx>; Zhang, PengtaoX > <pengtaox.zhang@xxxxxxxxx>; Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx> > Subject: RE: [Xen-devel] [BUG] win2008 guest cannot get ip through sriov > > On June 07, 2016 3:50 PM, Jan Beulich <JBeulich@xxxxxxxx> wrote: > > >>> On 07.06.16 at 07:52, <quan.xu@xxxxxxxxx> 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@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |