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/
Home Products Support Community News


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

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-users] Re: [Xen-devel] pci-passthrough in pvops causing offline raid
From: Mark Adams <mark@xxxxxxxxxxxxxxxxxx>
Date: Mon, 15 Nov 2010 17:23:09 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>, "JBeulich@xxxxxxxxxx" <JBeulich@xxxxxxxxxx>
Delivery-date: Mon, 15 Nov 2010 09:25:34 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20101115171543.GB7414@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20101111165340.GB30006@xxxxxxxxxxxx> <20101111173850.GA8756@xxxxxxxxxxxxxxxxxx> <20101111175809.GA30825@xxxxxxxxxxxx> <20101111181329.GA9058@xxxxxxxxxxxxxxxxxx> <20101111184723.GA10054@xxxxxxxxxxxxxxxxxx> <20101111190658.GC15530@xxxxxxxxxxxx> <20101112171058.GA29875@xxxxxxxxxxxxxxxxxx> <20101112222215.GC26189@xxxxxxxxxxxx> <3A9FD6B4-B741-4BAA-90C9-E3CA1143EA7A@xxxxxxxxxxxxxxxxxx> <20101115171543.GB7414@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Mon, Nov 15, 2010 at 12:15:44PM -0500, Konrad Rzeszutek Wilk wrote:
> On Sun, Nov 14, 2010 at 05:15:02PM +0000, Mark Adams wrote:
> > 
> > On 12 Nov 2010, at 22:22, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> 
> > wrote:
> > 
> > > On Fri, Nov 12, 2010 at 05:10:58PM +0000, Mark Adams wrote:
> > >> On Thu, Nov 11, 2010 at 02:06:58PM -0500, Konrad Rzeszutek Wilk wrote:
> > >>>> I've just noticed this at the end of xm dmesg
> > >>>> 
> > >>>> (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

> > > I was going to look in the source today to get an idea but never got to 
> > > it...
> > > 
> > > You might, as I mentioned in earlier emails, try to setup a serial console
> > > or netconsole and log the Linux kernel output when it hangs/fails.
> > > 
> > 
> > can't do this unfortunately, the server
> > Is in use so not able to just let it hang again... The passthrough is not 
> > in use now until I think there is some possible solution to get rid of the 
> > MSI conflict (when it won't hang anymore!)
> Didn't you say that you had two servers and saw this problem on another
> box too?
> Without more details on the Xen hypervisor line or the kernel line when
> the failure occurs I sadly can't help you.

Yes this occurs on both servers that I've tried it on. Doesn't the MSI
log above indicate that there is a conflict - which is what ends up
causing the device to go offline? Is there no other way to identify the


Xen-devel mailing list

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