Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 230663

Re: Splitting up a nVidia GRID K2's GPUs?

$
0
0

I can also confirm this happens in our environment.

 

Environment is

Horizon View 5.2.0 build 987719.

ESX 5.1.0 1157734 on Dell R720

LG Zero Client 23CAV42K (Tera 2 chip)

 

I have setup GPU passthrough for a VM. I followed recommendations of the following VMware guide.

http://www.vmware.com/files/pdf/techpaper/vmware-horizon-view-graphics-acceleration-deployment.pdf

 

The VM comes up fine with both the nVidia and SVGA card listed in device manager. However it always defaults to using the SVGA card i.e the zero client monitor attaches to the SVGA card and all 3d rendering is done by the SVGA card. If I try to open the nvidia control panel, it complains that I am not currently using a display that is attached to an NVIDIA GPU.

 

The doco I linked above states that as long as I have configured the cards fine, and I have set the zero client to use PCoIP and native resolution, when I boot up the VM,  it should attach to the nvidia k1, but it doesn’t.

 

The only way I can get the nvidia card activated is to uninstall the SVGA card from device manager. Once I have done that it activates the nvidia K1 and all is fine but only until you reboot. Upon reboot, windows detects the hardware for SVGA again and problem arises again.

 

I have found some clues on the web about this. See page 21 of this article “Configuring Virtual Monitors”

http://www.muycomputer.com/wp-content/uploads/2011/11/HP-Hardware-Accelerated-Graphics-for-VDI.pdf

and also

https://communities.vmware.com/thread/398755?start=0&tstart=0

 

The clues are that it has something to do with EDID. However I cannot do what is suggested which is plug in a monitor to the nvidia card on the host to save the EDID config as the nvidia K1’s don’t have any Display IO ports .


Viewing all articles
Browse latest Browse all 230663

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>