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] Re: follow up to a pciback "pv pci-passthrough co-assign

To: 0bo0 <0.bugs.only.0@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: follow up to a pciback "pv pci-passthrough co-assigned problem"
From: Weidong Han <weidong.han@xxxxxxxxx>
Date: Tue, 26 Jan 2010 09:42:00 +0800
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 25 Jan 2010 17:42:35 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <c67eed301001250817o66c39940o2d234bcb040fd593@xxxxxxxxxxxxxx>
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: <c67eed301001221732s4b6a9a10p4be4182ecf831b6a@xxxxxxxxxxxxxx> <20100123164850.GT2861@xxxxxxxxxxx> <c67eed301001230936o37dc63c2le944386cbaa02ff3@xxxxxxxxxxxxxx> <20100123174333.GW2861@xxxxxxxxxxx> <c67eed301001230945i45b8bb22q8cc3ded555cd7959@xxxxxxxxxxxxxx> <c67eed301001230954i6e9098fdwde189d429b8591fa@xxxxxxxxxxxxxx> <20100123175705.GY2861@xxxxxxxxxxx> <c67eed301001230958x2b22a5cs45df42cb956f75ed@xxxxxxxxxxxxxx> <c67eed301001231015v2c572d2fxb4a221157f3f1bfd@xxxxxxxxxxxxxx> <4B5CF79A.6020002@xxxxxxxxx> <c67eed301001250817o66c39940o2d234bcb040fd593@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (Windows/20090302)
0bo0 wrote:

On Sun, Jan 24, 2010 at 5:44 PM, Weidong Han <weidong.han@xxxxxxxxx> wrote:
I think this is not a bug. pls note ...


Ack'd, even if the limitations are not fully understood:-/

or you
can set "pci-passthrough-strict-check no" in /etc/xen/xend-config.sxp and
restart xend to loose the check in xend, but in this way you should be aware
of potential issues (e.g. assigned device doesn't work).

sure.  would it not be reasonable to have a similar config-file option
in xen 3.x -- with similar warnings etc -- as is done in 4.x? if all
that's required for a workaround is a patch similar to that above ...

The option was introduced by changeset 20179. It's small. It can be back ported to Xen 3.x if need.


Xen-devel mailing list

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