Re: [Xen-devel] IOMMU fault with IGD passthrough setup on XEN 4.8.0

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 08.02.17 at 15:56, <firemeteor@xxxxxxxxxxxxxxxxxxxxx> wrote:
> On Wed, Feb 8, 2017 at 10:29 PM, G.R. <firemeteor@xxxxxxxxxxxxxxxxxxxxx> 
> wrote:
>> On Wed, Feb 8, 2017 at 8:44 PM, Jan Beulich <JBeulich@xxxxxxxx> wrote:
>>>>>> On 07.02.17 at 16:44, <firemeteor@xxxxxxxxxxxxxxxxxxxxx> wrote:
>>>> On Mon, Feb 6, 2017 at 8:40 PM, Jan Beulich <JBeulich@xxxxxxxx> wrote:
>>>>>>>> On 05.02.17 at 06:51, <firemeteor@xxxxxxxxxxxxxxxxxxxxx> wrote:
>>>>>> I finally get some spare time to collect the debug info.
>>>>>
>>>>> As I continue to be puzzled, best I could come up with is an
>>>>> extension to the debug patch. Please use the attached one
>>>>> in place of the earlier one, ideally on top of
>>>>> https://lists.xenproject.org/archives/html/xen-devel/2017-02/msg00448.html
>>>>>  
>>>>> to reduce the overall amount of output (and help readability).
>>>>
>>>> Please see attached...
>>>
>>> So can you please give
>>> https://lists.xenproject.org/archives/html/xen-devel/2017-02/msg00602.html 
>>> a try?
>>>
>> Hmm, it does not help.
>> But I'll need to double check if I was misleading you.
>> I used attempt dom0pvh=1 but it was too unstable and I was only able
>> to disable it through hacking grub.cfg through sshfs remotely.
>> I forgot to touch the /etc/default/grub so the dom0pvh=1 may have come
>> back when I was generating the log yesterday.
>>
>> Going to do it once again now.
> 
> It appears that dom0pvh or not does not affect the debug output
> without Roger's patch.
> Anyway, attaching the output for you to double check.

Well, if this indeed was with his patch in place, then I'm puzzled.
I'd have to further extend the debugging patch then, but this may
take a few days to get to.

Jan


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