From mboxrd@z Thu Jan 1 00:00:00 1970 From: Weidong Han Subject: Re: Re: follow up to a pciback "pv pci-passthrough co-assigned problem" Date: Mon, 25 Jan 2010 09:44:58 +0800 Message-ID: <4B5CF79A.6020002@intel.com> References: <20100123123042.GG2861@reaktio.net> <20100123164850.GT2861@reaktio.net> <20100123174333.GW2861@reaktio.net> <20100123175705.GY2861@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: mail ignored <0.bugs.only.0@gmail.com> Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org mail ignored wrote: > On Sat, Jan 23, 2010 at 9:58 AM, mail ignored <0.bugs.only.0@gmail.com> wrote: > >> thanks. i suppose i'll file a bug @ opensuse abt this, and see if >> they'll put something into code so these changes will 'survive' >> xen(-tools) updates ... >> > > cref -> https://bugzilla.novell.com/show_bug.cgi?id=573311 > I think this is not a bug. pls note that the devices behind PCIe-to-PCI/PCI-x bridge or Conventional PCI bridge can only be collectively assigned to a single domain, because the source-id in DMA requests is not device's bdf. Pls refer to section 3.6.1 in VT-d spec. What's more, FLR is required to make sure the device in a correct status before assignment, and some devices need to reset secondary bus to reset the device which results in all the devices behind same PCIe-to-PCI/PCI-x bridge or Conventional PCI bridge be reset. In your case, you need to hide all NICs (04:06.0 and 04:07.0) behind the same bridge, and assign them together to a guest. 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). Regards, Weidong