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-devel] pv_ops reassigndev for pci passthrough

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] pv_ops reassigndev for pci passthrough
From: Michael D Labriola <mlabriol@xxxxxxxx>
Date: Wed, 23 Dec 2009 15:10:18 -0500
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Chris <tknchris@xxxxxxxxx>, xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 23 Dec 2009 12:11:18 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C7581A1B.52C2%keir.fraser@xxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> New option is reassign_resources. Used like:
> guestdev=00:01.0,00:02.0 reassign_resources
> Where you use guestdev= instead of pciback.hide=

Can this be done somehow post boot?

Is it in Jeremy's xen/master?  It doesn't seem to be working in my pull 
from 2 hours ago...

What about the original complaint regarding PCI addresses not being 
guaranteed static?  I had the distinct impression that this wouldn't get 
merged upstream if we're still specifying PCI IDs at boot...


Xen-devel mailing list