From mboxrd@z Thu Jan 1 00:00:00 1970 From: mail ignored <0.bugs.only.0@gmail.com> Subject: Re: Re: follow up to a pciback "pv pci-passthrough co-assigned problem" Date: Sat, 23 Jan 2010 08:40:28 -0800 Message-ID: References: <20100123123042.GG2861@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20100123123042.GG2861@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: xen-devel@lists.xensource.com, weidong.han@intel.com List-Id: xen-devel@lists.xenproject.org hi On Sat, Jan 23, 2010 at 4:30 AM, Pasi K=E4rkk=E4inen wrote: > This has been discussed many times here on xen-devel and on xen-users.. You're right -- there sure has. That's been my problem -- there's not a consistent solution to be found. :-/ > with xen-unstable (upcoming Xen 4.0) take a look at /etc/xen/xend-config.= sxp: > =A0 =A0 =A0 =A0(pci-passthrough-strict-check yes) > set that to no, restart xend, and it'll work. Yep, I'm aware of that. But 4.0.x fails miserably on my box, atm :-/ I'm hoping that there's a fix for 'stable' 3.4.x. > With Xen 3.3, or 3.4, you can apply a "disable FLR" patch, which also mak= es it work: > http://xen.markmail.org/download.xqy?id=3D7dbm675e4x4dawec&number=3D1 I applied the patch at that link. At VM launch, I still get the Error: pci: 0000:04:07.0 must be co-assigned to the same guest with 0000:04:06.0 message ... Thanks.