From: Mats Petersson <mats.petersson@citrix.com>
To: xen-devel@lists.xen.org
Subject: Re: Issue about domU missing interrupt
Date: Mon, 3 Dec 2012 10:15:08 +0000 [thread overview]
Message-ID: <50BC7BAC.8050107@citrix.com> (raw)
In-Reply-To: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
On 03/12/12 03:47, G.R. 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.
>
> 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
Are you passing hardware (PCI Passthrough) to the HVM guest?
What are the exact messages in the DomU?
--
Mats
next prev parent reply other threads:[~2012-12-03 10:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 3:47 Issue about domU missing interrupt G.R.
2012-12-03 7:06 ` Zhang, Xiantao
2012-12-03 13:06 ` G.R.
2012-12-03 8:46 ` Jan Beulich
2012-12-03 12:43 ` G.R.
2012-12-03 13:06 ` Jan Beulich
2012-12-03 10:15 ` Mats Petersson [this message]
2012-12-03 13:14 ` G.R.
2012-12-03 13:19 ` Mats Petersson
2012-12-03 13:58 ` Mats Petersson
2012-12-04 3:07 ` G.R.
2012-12-04 3:12 ` G.R.
2012-12-04 10:15 ` Jan Beulich
2012-12-04 11:01 ` Pasi Kärkkäinen
2012-12-04 15:20 ` G.R.
2012-12-05 12:58 ` G.R.
2012-12-04 23:05 ` Sander Eikelenboom
2012-12-05 11:51 ` Stefano Stabellini
2012-12-05 12:02 ` Sander Eikelenboom
2012-12-05 12:07 ` Stefano Stabellini
2012-12-05 12:11 ` Sander Eikelenboom
2012-12-05 15:34 ` Sander Eikelenboom
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=50BC7BAC.8050107@citrix.com \
--to=mats.petersson@citrix.com \
--cc=xen-devel@lists.xen.org \
/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).