<div dir="ltr">Ruben,<div><br></div><div>What is your output from this?</div><div><br></div><div>lspci -k | egrep -i '(nvidia|driver)'<br></div><div><br></div><div>Just need the lines with your video card and the driver line below each one of those.</div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Jan 28, 2016 at 2:18 PM Ruben Felgenhauer <<a href="mailto:4felgenh@informatik.uni-hamburg.de">4felgenh@informatik.uni-hamburg.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Hi again, Will!<br>
<br>
I had removed the hypervclock tag back then, but forgot to mention
it, sorry.<br>
In the meantime I played around with the config quite a lot, but
nothing helps, always Code 43.<br>
I tried to compare your xml file with mine, but nothing really stuck
out.<br>
<br>
Can you remember having done anything special to get the 750ti to
work?<br>
Did you ever have problems with Code 43 aswell?<br>
Is it maybe a problem with other devices or is the gpu simply still
noticing the hypervisor?<br>
Config is here: <a href="http://pastebin.com/fL6PGrM0" target="_blank">http://pastebin.com/fL6PGrM0</a><br>
<br>
Best regards,<br>
Ruben</div><div text="#000000" bgcolor="#FFFFFF"><br>
<br>
<div>Am 25.01.2016 um 17:01 schrieb Will
Marler:<br>
</div>
<blockquote type="cite">
<div dir="ltr">This is discussed in <a href="http://vfio.blogspot.com/2015/05/vfio-gpu-how-to-series-part-4-our-first.html" target="_blank">http://vfio.blogspot.com/2015/05/vfio-gpu-how-to-series-part-4-our-first.html</a>.
You have to do more than <kvm><hidden
state='on'/></kvm>:<br>
<div><br>
</div>
<div>"The GeForce card is nearly as easy, but we first need to
work around some of the roadblocks Nvidia has put in place to
prevent you from using the hardware you've purchased in the
way that you desire (and by my reading conforms to the EULA
for their software, but IANAL). For this step we again need
to run virsh edit on the VM. Within the <features>
section, remove everything between the <hyperv> tags,
including the tags themselves. In their place add the
following tags:</div>
<div><br>
</div>
<div> <kvm></div>
<div> <hidden state='on'/></div>
<div> </kvm></div>
<div><br>
</div>
<div>Additionally, within the <clock> tag, find the timer
named hypervclock, remove the line containing this tag
completely. Save and exit the edit session."</div>
<div><br>
</div>
<div>I can confirm it works, I've been getting a lot of mileage
from my passed-through 750Ti lately since getting a Steam Link
:-D.</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sun, Jan 24, 2016 at 7:32 AM, Ruben
Felgenhauer <span dir="ltr"><<a href="mailto:4felgenh@informatik.uni-hamburg.de" target="_blank">4felgenh@informatik.uni-hamburg.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> Hi,<br>
<br>
finally I had time to this again. I tried out virt-manager
and after a bit of playing around with it, it /somewhat/
worked:<br>
<br>
The machine is at least booting. I still have a standard
vga card enabled in the virt-manager config window.<br>
After the machine has booted, I can see that the device
gets recognized as 750ti.<br>
However, the gpu doesn't get used, because of 'Code 43'.<br>
Code 43 is a generic error, so any idea what it could mean
in this case?<br>
<br>
Of course I added the <kvm><hidden
state='on'/></kvm> lines at the associated
position.<br>
<br>
Best regards,<br>
Ruben
<div>
<div><br>
<br>
<div>Am 18.01.2016 um 22:27 schrieb Will Marler:<br>
</div>
<blockquote type="cite">
<div dir="ltr">I'm not sure what correct
command-line syntax is. Have you tried using
libvirt and VirtManager to handle your VM rather
than command line, and modifying the XML rather
than the command line? I think that's generally
the preferred method these days (it's certainly
easier from my point of view, and the way I got my
750 Ti to pass through).</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Jan 18, 2016 at
11:04 AM, Ruben Felgenhauer <span dir="ltr"><<a href="mailto:4felgenh@informatik.uni-hamburg.de" target="_blank"><a href="mailto:4felgenh@informatik.uni-hamburg.de" target="_blank">4felgenh@informatik.uni-hamburg.de</a></a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> Hi,
Alex!<br>
<br>
Thanks for your reply!<br>
My GPU indeed has a seperate audio device
located at 01:00.1.<br>
<br>
However, just adding -device
vfio-pci,host=01:00.1 doesn't seem to do the
trick.<br>
Of course the corresponding device is
already blacklisted and bound to vfio.<br>
<br>
The Debian Wiki entry about VGA passthrough
(<a href="https://wiki.debian.org/VGAPassthrough" target="_blank">https://wiki.debian.org/VGAPassthrough</a>)
mentions QEMU arguments like "-device
vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on,romfile=...
-device vfio-pci,host=01:00.1,bus=pcie.0"
which seems to address GPUs with audio
devices, but if I try to do something
similar, the buses 'root' and 'pcie'
couldn't be found. Maybe I missed something
very important?<br>
<br>
On the same article, it says that the "HDMI
soundcard [...] needs to be unbound from its
driver":<br>
# echo '0000:01:00.1' | sudo tee
/sys/bus/pci/devices/0000:01:00.1/driver/unbind<br>
I figured the vfio-bind script from the Arch
Linux Forum thread (<a href="https://bbs.archlinux.org/viewtopic.php?id=162768" target="_blank"><a href="https://bbs.archlinux.org/viewtopic.php?id=162768" target="_blank">https://bbs.archlinux.org/viewtopic.php?id=162768</a></a>)
would do exactly this thing, so I didn't
explicitly do so for the audio device. Is
that okay?<br>
<br>
Best regards,<br>
Ruben
<div>
<div><br>
<br>
<div>Am 18.01.2016 um 08:31 schrieb
Alexander Petrenz:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi Ruben,
<div><br>
</div>
<div>I guess your 750ti also has
some audio device. You should pass
through this too. It should be
something like 01:00.1. There are
many command line examples you can
find about that.</div>
<div>Also I´m not quite sure, if you
should remove the x-vga=on.</div>
<div><br>
</div>
<div>Regards</div>
<div>Alex</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sun, Jan
17, 2016 at 11:12 PM, Ruben
Felgenhauer <span dir="ltr"><<a href="mailto:4felgenh@informatik.uni-hamburg.de" target="_blank"><a href="mailto:4felgenh@informatik.uni-hamburg.de" target="_blank">4felgenh@informatik.uni-hamburg.de</a></a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I am trying to pass my nVidia
GTX 750ti to my QEMU guest.<br>
<br>
Problem is: After the QEMU
monitor pops up, nothing
happens. The GPU's output is
dead, and the vm won't be
accessible via SSH anymore, so
it's very likely that the VM
isn't booting up at all. Also,
there are no error messages from
QEMU on the console whatsoever
which makes debugging it
especially hard.<br>
<br>
This is how I start the vm with
normal vga emulation:<br>
qemu-system-x86_64 -hda vm.ovl
-boot c -enable-kvm -m 1024 -cpu
host,kvm=off -smp
cores=4,threads=2 -redir
tcp:5022::22<br>
Everything runs fine in this
case. To do the passthrough, I
add this:<br>
-device
vfio-pci,host=01:00.0,multifunction=on,x-vga=on
-vga none<br>
This brings said problems with
it. I also tried out multiple
different combinations of
-device's arguments or even
adding a romfile for the GPU,
but none of these steps changed
anything at all.<br>
<br>
Obviously, I am using a BIOS
installation and I'm well-aware
with this bug: <a href="https://bugzilla.kernel.org/show_bug.cgi?id=107561" target="_blank"><a href="https://bugzilla.kernel.org/show_bug.cgi?id=107561" target="_blank">https://bugzilla.kernel.org/show_bug.cgi?id=107561</a></a>,
but neither using less RAM (as
you can see I am using 1GB now)
nor switching to an older Kernel
changed anything about the
problem. I have tried Kernel
4.1.0 and 4.3.0.<br>
<br>
Host is Debian testing with QEMU
2.5.0.<br>
I tried both Debian and Windows
7 as a guest, but both are
showing exactly the same
behaviour.<br>
Mainboard is an ASUS Z87-PLUS.
The 750ti is produced by ASUS
aswell.<br>
<br>
Any idea how I could get
passthrough running?<br>
<br>
_______________________________________________<br>
vfio-users mailing list<br>
<a href="mailto:vfio-users@redhat.com" target="_blank">vfio-users@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/vfio-users" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/vfio-users</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
vfio-users mailing list<br>
<a href="mailto:vfio-users@redhat.com" target="_blank">vfio-users@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/vfio-users" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/vfio-users</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div>
_______________________________________________<br>
vfio-users mailing list<br>
<a href="mailto:vfio-users@redhat.com" target="_blank">vfio-users@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/vfio-users" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/vfio-users</a><br>
</blockquote></div>