Re: [Xen-devel] Issue about domU missing interrupt

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

On Mon, Dec 3, 2012 at 4:46 PM, Jan Beulich <JBeulich@xxxxxxxx> wrote:

>>> On 03.12.12 at 04:47, "G.R." <firemeteor@xxxxxxxxxxxxxxxxxxxxx> wrote:
> 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.

Please check the list archives, this issue was discussed in great
lengths a couple of months ago (and should be fixed in current
trees).

Thanks, I just found the thread you mentioned:
http://lists.xen.org/archives/html/xen-devel/2012-06/msg01909.html

I can confirm that the debian version of the xen 4.1.3 still misses this patch.
Given the fact that xen 4.1.3 releases after the patch, I guess it is only intended for v4.2.0?

Do you believe this patch should work for v4.1.3 either?
But anyway, I'm going to try my luck later...

Thanks,
Timothy

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