[Xen-devel] Issue about domU missing interrupt

["G.R." <firemeteor@xxxxxxxxxxxxxxxxxxxxx>]

Hi developers,
I met some domU issues and the log suggests missing interrupt.
Details from here: http://www.gossamer-threads.com/lists/xen/users/263938#263938
In summary, this is the suspicious log:

(XEN) vmsi.c:122:d32767 Unsupported delivery mode 3

I've checked the code in question and found that mode 3 is an 'reserved_1' mode.
I want to trace down the source of this mode setting to root-cause the issue.
But I'm not an xen developer, and am even a newbie as a xen user. 
Could anybody give me instructions about how to enable detailed debug log?
It could be better if I can get advice about experiments to perform / switches to try out etc.

My SW config:
dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)
domU: Debian wheezy 3.2.x stock kernel.

Thanks,
Timothy
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel