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-users

Re: [Xen-users] pci device not owned by pciback.

To: James Pifer <jep@xxxxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] pci device not owned by pciback.
From: "Sergio Charpinel Jr." <sergiocharpinel@xxxxxxxxx>
Date: Wed, 28 Apr 2010 11:49:51 -0300
Cc:
Delivery-date: Wed, 28 Apr 2010 07:51:25 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=9GQ9Q+MrUvZpbu1M6QE+Cw3OQUHxrI5UALIAqlvV5iQ=; b=Ch86AvtuKnWZjEjEXnPp6RBShEtwoG/zTLRXCQtv6DfeDY8JhzzNBw6rnwzu01f0sd j4U4APGL6feKm3qtliKE+5azaodZ/2Id6C716UDxRHA1mtvI+earVy6SIegJI+2D4Pa7 4qbqypJrSOcsxpAkxl0aiSwb5xFbnim8mbG24=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Gs5ae+qFCqmvezrnHQ9UWD9nPG0FJcxK6YM1GEOeWRYr1n43EaObmoKqI1U9wNvW6Z vxAQDVTmywQ+AtZW410p8ETOC1mtglFBzblDYkNDWUkltFblcjoBEu5gwR54c/cjI0gE 2CUlDYfsxX4QOQPcYmg6V92tEfmCHT5z89eng=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1272393974.3080.37.camel@xxxxxxxxxxxxxxxxxxxxxxxx>
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: <1272373556.19411.47.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <1272379155.3080.4.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <ca7c6f78eceaa0d46f54b6972db893fa.squirrel@xxxxxxxxxxxxxxxxx> <1272386381.3080.21.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <4BD717D2.4020802@xxxxxxxxxxxx> <1272391712.3080.31.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <A5447537-D9FB-435C-84E9-B2293F263B19@xxxxxxxxx> <1272393974.3080.37.camel@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
James,

To get this working on boot, you need to set the pciback.hide parameter in kernel boot line. But pciback must but compiled inside the kernel (not as module). If you are using CentOS or redhat, probably it is compiled as module.
You could check $(uname -r)-config file and see the options.  CONFIG_XEN_PCIDEV_BACKEND=y in xen kernel (dont know in pv_ops).

If these commands are working for you, just make a script for it.

2010/4/27 James Pifer <jep@xxxxxxxxxxxxxxxx>
> Yeah, getting device passthrough to work properly for pvops kernel
> can be tricky. The iommu and swiotlb magic sound familiar, it took
> some time before i got my ivtv cards working properly as well...
>
> Good to hear you got it to work now.

Well it's working, but not solved. I can't go through all those steps
every time. I will need to figure out how to get this to work on boot. I
will try the commands you wrote in the other response and see what
happens. Maybe I will open a ticket with Novell too.

Thanks,
James


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



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