From mboxrd@z Thu Jan 1 00:00:00 1970 From: 0bo0 <0.bugs.only.0@gmail.com> Subject: Re: Re: follow up to a pciback "pv pci-passthrough co-assigned problem" Date: Mon, 25 Jan 2010 08:17:35 -0800 Message-ID: References: <20100123164850.GT2861@reaktio.net> <20100123174333.GW2861@reaktio.net> <20100123175705.GY2861@reaktio.net> <4B5CF79A.6020002@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: In-Reply-To: <4B5CF79A.6020002@intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Weidong Han Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org hi, On Sun, Jan 24, 2010 at 5:44 PM, Weidong Han wrote: > I think this is not a bug. pls note ... (snip) 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 ... thanks