<html><head><meta http-equiv="content-type" content="text/html; charset=UTF-8"><style>body { line-height: 1.5; }blockquote { margin-top: 0px; margin-bottom: 0px; margin-left: 0.5em; }div.foxdiv20160405003949355484 { }body { font-size: 12pt; font-family: 微软雅黑; color: rgb(0, 0, 0); line-height: 1.5; }</style></head><body> <div><span></span>sorry alex,i had pasted the wrong log.</div><div><br></div><div>here is the log that makes the VM work well.</div><div><br></div><div>and i found that valua of the video memory report error is a BUG of dxdiag tool. The ref is : <span style="background-color: rgba(0, 0, 0, 0); font-size: 12pt; line-height: 1.5;">https://support.microsoft.com/en-us/kb/2026022</span></div><div><br></div><div>here is correct log,this log is from /var/log/libvirt/qemu,and I use the wrapper script to add the "x-vga=on" command ,so in libvirt log the "x-vga=on" command can not be found. </div><div><br></div><div><span style="color: rgb(0, 0, 0); background-color: rgba(0, 0, 0, 0);">2016-04-04 15:49:47.573+0000: starting up libvirt version: 1.2.18.2, package: 2.fc23 (Fedora Project, 2016-01-21-00:54:13, buildhw-01-nfs.phx2.fedoraproject.org), qemu version: 2.4.1 (qemu-2.4.1-7.fc23)<br>LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-kvm.vga -name win7 -S -machine pc-i440fx-2.4,accel=kvm,usb=off,vmport=off -cpu SandyBridge,+erms,+smep,+fsgsbase,+pdpe1gb,+rdrand,+f16c,+osxsave,+dca,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme,kvm=off -m 4096 -realtime mlock=off -smp 2,sockets=1,cores=2,threads=1 -uuid a6f3edfd-39a7-450f-b557-9ddb459f9401 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/win7.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x6.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/var/lib/libvirt/images/win7.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=23,id=hostnet0,vhost=on,vhostfd=24 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:41:6e:bb,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1 -device vfio-pci,host=03:00.0,id=hostdev0,bus=pci.0,addr=0x2 -device vfio-pci,host=03:00.1,id=hostdev1,bus=pci.0,addr=0x9 -device usb-host,hostbus=2,hostaddr=8,id=hostdev2 -device usb-host,hostbus=2,hostaddr=7,id=hostdev3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on</span></div><div><span style="color: rgb(0, 0, 0); background-color: rgba(0, 0, 0, 0);"><br></span></div><div><span style="color: rgb(0, 0, 0); background-color: rgba(0, 0, 0, 0);"><br></span></div><blockquote style="margin-top: 0px; margin-bottom: 0px; margin-left: 0.5em;"><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"><div style="PADDING-RIGHT: 8px; PADDING-LEFT: 8px; FONT-SIZE: 12px;FONT-FAMILY:tahoma;COLOR:#000000; BACKGROUND: #efefef; PADDING-BOTTOM: 8px; PADDING-TOP: 8px"><div><b>From:</b> <a href="mailto:alex.l.williamson@gmail.com">Alex Williamson</a></div><div><b>Date:</b> 2016-04-05 00:38</div><div><b>To:</b> <a href="mailto:Kayv@qq.com">温学敏</a></div><div><b>CC:</b> <a href="mailto:vfio-users@redhat.com">vfio-users</a></div><div><b>Subject:</b> Re: [vfio-users] physx can not work after VGA passthrough.</div></div></div><div><div class="FoxDiv20160405003949355484"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Apr 4, 2016 at 9:13 AM, 温学敏 <span dir="ltr"><<a href="mailto:Kayv@qq.com" target="_blank">Kayv@qq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div> <div><span></span>Hi guys:</div><div> I was passthrough my GTX 970 on a win7_x64 and it works fine.The host is running a Fedora 23 Workstation.</div><div><br></div><div><span style="color:rgb(0,0,0);background-color:rgba(0,0,0,0)"> I use virt-manager 1.3.2 to create the VM,The version of Libvirt is 1.2.18,QEMU version is 2.4.1.</span></div><div><br></div><div><span style="color:rgb(0,0,0);background-color:rgba(0,0,0,0)"> But when I run the 3Dmark 11 to confirm the function and performance,I found that the physx function didn't work.</span></div><div><span style="color:rgb(0,0,0);background-color:rgba(0,0,0,0)"><br></span></div><div><span style="color:rgb(0,0,0);background-color:rgba(0,0,0,0)"> Aslo i found that the display tab in the "dxdiag" command shows me the video memory is just 679MB,and the GTX 970 have 4096MB.</span></div><div><span style="font-size:12pt;line-height:1.5;background-color:rgba(0,0,0,0)"> </span></div><div><span style="font-size:12pt;line-height:1.5;background-color:rgba(0,0,0,0)"> Can anyone tell me where is wrong?</span></div><div><span style="font-size:12pt;line-height:1.5;background-color:rgba(0,0,0,0)"><br></span></div><div><span style="font-size:12pt;line-height:1.5;background-color:rgba(0,0,0,0)"><br></span></div><div><span style="font-size:12pt;line-height:1.5;background-color:rgba(0,0,0,0)"> </span><span style="font-size:12pt;line-height:1.5;background-color:rgba(0,0,0,0)"> here is my qemu startup log:</span></div></div></blockquote><div><br></div><div>Your log doesn't show any indication of having the GPU assigned to the VM at all. Nor does it show any of the options necessary to make the NVIDIA driver work in a VM and you're not even running OVMF for the VM BIOS. Have you followed any of the guides for configuring a VM for NVIDIA GeForce assignment? Start here:</div><div><br></div><div><a href="http://vfio.blogspot.com/2015/05/vfio-gpu-how-to-series-part-1-hardware.html">http://vfio.blogspot.com/2015/05/vfio-gpu-how-to-series-part-1-hardware.html</a><br></div><div><br></div><div>Read parts 1-4 for the preferred way to make this work, part 5 only if required. Thanks,</div><div><br></div><div>Alex</div></div></div></div> </div></div></blockquote> </body></html>