public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: "André Weidemann" <Andre.Weidemann@web.de>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: gfx card passthrough broken with latest head
Date: Tue, 23 Aug 2011 16:28:36 -0700	[thread overview]
Message-ID: <20110823232836.GA7796@sequoia.sous-sol.org> (raw)
In-Reply-To: <4E50B6F5.1090301@web.de>

* André Weidemann (Andre.Weidemann@web.de) wrote:
<snip>
> >git clone git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git
<snip>
> >./configure --audio-drv-list=alsa --target-list=x86_64-softmmu
> >--enable-kvm-device-assignment
> >
> >ERROR: unknown option --enable-kvm-device-assignment
<snip>
> 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 when
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
Forum for some examples: http://goo.gl/Hyk13

thanks,
-chris

      reply	other threads:[~2011-08-23 23:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-13 13:35 gfx card passthrough broken with latest head André Weidemann
2011-08-21  7:42 ` André Weidemann
2011-08-23 23:28   ` Chris Wright [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110823232836.GA7796@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=Andre.Weidemann@web.de \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox