From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Williamson Subject: Re: pci passthrough error about insufficient iommu width Date: Thu, 07 Aug 2014 09:02:50 -0600 Message-ID: <1407423770.316.186.camel@ul30vt.home> References: <53E29CA8.6070806@netapp.com> <1407360689.316.182.camel@ul30vt.home> <53E318DA.5090501@netapp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: William Tu , kvm@vger.kernel.org To: Nishank Trivedi Return-path: Received: from mx1.redhat.com ([209.132.183.28]:13825 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932071AbaHGPCx (ORCPT ); Thu, 7 Aug 2014 11:02:53 -0400 In-Reply-To: <53E318DA.5090501@netapp.com> Sender: kvm-owner@vger.kernel.org List-ID: On Wed, 2014-08-06 at 23:12 -0700, Nishank Trivedi wrote: > On 8/6/14, 2:49 PM, William Tu wrote: > >> > >> Try vfio-pci instead of pci-assign > >> > > Thanks Alex, William. Using vfio worked. > So does that mean pci-assign is being deprecated? Yes, vfio is meant to replace pci-assign with a better device ownership model, better security, better separation from KVM, support for multiple architectures, etc. There are no concrete plans to remove pci-assign, but as you can see, it's not as well tested or maintained as vfio. Thanks, Alex