From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andreas Hartmann <andihartmann@01019freenet.de>
Subject: Re: [PATCH 0/3] VFIO-based PCI device assignment for
	QEMU 1.2
Date: Mon, 13 Aug 2012 20:32:46 +0200
Message-ID: <5029484E.2020808@01019freenet.de>
References: <20120801050241.22163.78549.stgit@bling.home>
	<87pq6uvs52.fsf@codemonkey.ws>
	<1344867810.4683.21.camel@ul30vt.home>
	<20120813174834.7f4346c7@dualc.maya.org>
	<1344874489.4683.27.camel@ul30vt.home>
	<50292CFD.1080903@01019freenet.de>
	<1344877056.4683.55.camel@ul30vt.home>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Anthony Liguori <aliguori@us.ibm.com>, kvm@vger.kernel.org, aik@ozlabs.ru,
	Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel@nongnu.org,
	Blue Swirl <blauwirbel@gmail.com>, Avi Kivity <avi@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Return-path: <qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org>
In-Reply-To: <1344877056.4683.55.camel@ul30vt.home>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org
Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org
List-Id: kvm.vger.kernel.org

Alex Williamson wrote:
> On Mon, 2012-08-13 at 18:36 +0200, Andreas Hartmann wrote:
[...]
>> If I'm using your qemu instead of qemu from kvm-0.15 (opensuse package),
>> this error comes up when passing through a PCIe device, which works
>> absolutely fine with kvm 0.15. I would have expected, that your qemu
>> works with the legacy way of handling pcie passthrough, too (with
>> pci-stub module).
> 
> VFIO cannot work with pci-stub, the backends are fundamentally
> different.  KVM making use pci-stub to hold onto a device is actually
> one of the design problems that VFIO is meant to correct.  The other
> significant interface change is use of IOMMU groups, which is actually
> why VFIO works for some of your uses while pci-assign does not.
> 
>> This would mean, that all users get errors if they use the traditional
>> way. IOW: there are changes needed (which?) to move from kvm 0.15 to
>> your qemu version.
> 
> But the way we solve this is to make libvirt understand how to do both.
> Then it can probe the qemu/kvm binary and host system to figure out
> which is supported and use the correct device options based on what it
> finds.  Trying to do both via the same qemu command line doesn't make
> sense to me, especially when the device setup is so different.

Ok! I thought your qemu version still would understand the old way via
pci-stub. But this obviously was a misunderstanding of mine :-(.


Thanks,
Andreas