* André Weidemann (andre.weidem...@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 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
