WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-users] Re: [Xen-devel] pci-passthrough in pvops causing offline

To: Mark Adams <mark@xxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Re: [Xen-devel] pci-passthrough in pvops causing offline raid
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Wed, 24 Nov 2010 15:28:43 -0500
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>, "JBeulich@xxxxxxxxxx" <JBeulich@xxxxxxxxxx>
Delivery-date: Wed, 24 Nov 2010 12:31:18 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20101124175926.GA17565@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <20101111184723.GA10054@xxxxxxxxxxxxxxxxxx> <20101111190658.GC15530@xxxxxxxxxxxx> <20101112171058.GA29875@xxxxxxxxxxxxxxxxxx> <20101112222215.GC26189@xxxxxxxxxxxx> <3A9FD6B4-B741-4BAA-90C9-E3CA1143EA7A@xxxxxxxxxxxxxxxxxx> <20101115171543.GB7414@xxxxxxxxxxxx> <20101115172309.GA30777@xxxxxxxxxxxxxxxxxx> <20101115174413.GA8227@xxxxxxxxxxxx> <20101115175626.GA31636@xxxxxxxxxxxxxxxxxx> <20101124175926.GA17565@xxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
On Wed, Nov 24, 2010 at 05:59:26PM +0000, Mark Adams wrote:
> > > > > > >>>> 
> > > > > > >>>> (XEN) msi.c:715: MSI is already in use on device 02:00.0
> > > > > > >>>> (XEN) msi.c:715: MSI is already in use on device 02:00.0
> > > > > > >>>> (XEN) msi.c:715: MSI is already in use on device 02:00.0
> > > > > 
> > > > > Looking briefly at the code it means that somebody enabled the MSI
> > > > > already on the device and did not disable them. But I wonder how
> > > > > you got those in the first place. Did you use xen-pciback.hide (for 
> > > > > PVOPS kernels)
> > > > > or pciback.hide (for older kernels) to "hide" the devices away from 
> > > > > the
> > > > > Linux Dom0 kernel?
> > > > 
> > > > using xen-pciback.hide as its a pvops kernel (debian squeeze
> > > > 2.6.32-5-27)
> > > 
> > > Ok. Then it might be worth looking in when this happens. I think
> > > there is an argument on the Xen hyperisor line to include the time-stamp, 
> > > but
> > > I don't remember it :-(
> > > 
> 
> I've got a test setup in place now, and am trying to reproduce this.
> I've not connected up serial as yet, but can see the following logs in
> the qemu-dm log file when I get the "MSI is already in use" errors
> above. Note also that this error -always- shows for the first specified
> device in the pci= field, and not the 2nd.
> 
> pt_msixctrl_reg_write: guest enabling MSI-X, disable MSI-INTx translation
> pci_intx: intx=1
> pt_msix_update_one: Update msix entry 0 with pirq 4d gvec 59
> pt_msix_update_one: Update msix entry 1 with pirq 4c gvec 61
> pt_msix_update_one: Update msix entry 2 with pirq 4b gvec 69
> pt_msixctrl_reg_write: guest enabling MSI-X, disable MSI-INTx translation
> pci_intx: intx=2
> 
> I have also seen the following log just once, not sure if it's related:
> 
> (XEN) domctl.c:811:d0 XEN_DOMCTL_test_assign_device: 2:0.0 already assigned, 
> or non-existent
> 
> Does this help at all with debugging my issues?

Not yet. Need to serial log of the Linux kernel and the Xen hypervisor when your
machine is toast. I mentioned in the previous email the key sequences - look on 
Google
on how to pass in SysRQ if you are using a serial concentrator.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>