From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wright Subject: Re: gfx card passthrough broken with latest head Date: Tue, 23 Aug 2011 16:28:36 -0700 Message-ID: <20110823232836.GA7796@sequoia.sous-sol.org> References: <4E467DBD.1030803@web.de> <4E50B6F5.1090301@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: kvm To: =?iso-8859-1?Q?Andr=E9?= Weidemann Return-path: Received: from sous-sol.org ([216.99.217.87]:36756 "EHLO sequoia.sous-sol.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756135Ab1HWX2j (ORCPT ); Tue, 23 Aug 2011 19:28:39 -0400 Content-Disposition: inline In-Reply-To: <4E50B6F5.1090301@web.de> Sender: kvm-owner@vger.kernel.org List-ID: * Andr=E9 Weidemann (Andre.Weidemann@web.de) wrote: > >git clone git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git > >./configure --audio-drv-list=3Dalsa --target-list=3Dx86_64-softmmu > >--enable-kvm-device-assignment > > > >ERROR: unknown option --enable-kvm-device-assignment > How come so many revision do not support device assignment? Is there > a trick to enable it? Bisection qemu-kvm userspace is tricky. The upstream qemu repo (git://git.qemu.org/qemu.git) does not have PCI device assignment support. The qemu-kvm repo does regular merges w/ the upstream qemu repo. As you bisect through the qemu-kvm repo history, you are likely to land on a commit that is from upstream (meaning a tree w/out downstream qemu-kvm additions, like device assignment). Depending on where you suspect the issue is coming from, you can be careful to bisect only through the qemu-kvm tree (by skipping back to a merge point), or you can remerge the qemu-kvm tree to the qemu tree whe= n you bisect into the qemu tree. Note...gfx assignment has many issues associated w/ it and often does not work. You can check out Allen Kay's presentation at the recent KVM =46orum for some examples: http://goo.gl/Hyk13 thanks, -chris