From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mats Petersson Subject: Re: Issue about domU missing interrupt Date: Mon, 3 Dec 2012 10:15:08 +0000 Message-ID: <50BC7BAC.8050107@citrix.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org 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