Configuration file to limit resolution to 1920x1080 (grid K2 with xenserver)

NVIDIA Virtual GPU Forums Virtual GPU Talks with the Developers
#1

Hello,
We are using grid K2 with xenserver 6.5. For performance reason, I need to limit VMs resolution to 1920x1080. Nvidia driver creates several profile files in /usr/share/nvidia/vgx/ but these files are read only. Please tell me what to modify to make sure users in VM won’t exceed resolution over 1920x1080

Thanks,

Syed

#2

Driver I installed are NVIDIA-GRID-vGPU-XenServer-6.5-352.46-354.13 and NVIDIA-GRID-vGPU-XenServer-6.5-346.68-348.27

Thanks,

Syed

#3

You’ll need to do this in the remoting stack and not at the driver level.

#4

Hello Jason,
Thanks for your reply. Please explain exactly how.

Syed

#5

That’s a question for whichever remoting solution vendor you are using, as most will default to the resolution of the monitor your connecting from and present that value to the VM which then sets the resolution accordingly.

What you’re looking to do is bypass that and fix the resolution, and the method will vary between remoting solutions.

#6

Jason, with previous driver NVIDIA-GRID-vGPU-XenServer-6.5-346.68-348.27 when I edited /usr/share/nvidia/vgx/grid_k240q.conf and set plugin0.max_resolution 1920x1080; VM using K240Q profile were set to use MAX 1920x1080 resolution but when I installed NVIDIA-GRID-vGPU-XenServer-6.5-352.46-354.13 with our K2, VMs with K240Q ignores grid_k240q.conf parameter and let user assign 2560x1600; with the latest driver (NVIDIA-GRID-vGPU-XenServer-6.5-352.46-354.13) how I may restrict user to resolution 1920x1080.

Our servers have both drivers with all K2 grids. Please tell me right way to restrict users to 1920x1080 with both drivers.

Thanks,

Syed

#7

Modifying the driver is not supported.

You have to manage this at the display level, which means setting the limit in the remoting protocol.

#8

I found technical answer: https://gridforums.nvidia.com/default/topic/258/nvidia-grid-vgpu/documentation-for-vgpu-configs/post/2087/#2087.
Ask NVidia to remove new restriction from display resolution and frl parameters or NVidia should accept parameters from *.conf with less value then in vgpuConfig.xml.

M.C>

#9

Thanks M.C! I’ve tried to modify vgpuConfig.xml but it only breaks the config and prevents any VM with vgpu profile from starting. VMs I’m having issue with running Windows 10

Syed

#10

Thanks M.C! I’ve tried to modify vgpuConfig.xml but it only breaks the config and prevents any VM with vgpu profile from starting. VMs I’m having issue with running on Windows 10

Syed

#11

Thanks M.C! I’ve tried to modify vgpuConfig.xml but it only breaks the config and prevents any VM with vgpu profile from starting. VMs I’m having issue with running on Windows 10

Syed

#12

Thanks M.C! I’ve tried to modify vgpuConfig.xml but it only breaks the config and prevents any VM with vgpu profile from starting. VMs I’m having issue with running on Windows 10

Syed

#13

This is not, and has never been supported.

If you modify the drivers and or vGPU Manager you will be deploying an unsupported solution.

#14

Yes this is expected. As I wrote this file has digitally signed metadata and does not support modification (see /var/log/messages and search for "nvidia-vgpud: error" when restarting "/etc/init.d/nvidia-vgpud").

The only way is on NVidia side to allow lowering parameters (eg. some software engineer should accept data from *.conf or runtime with lower parameters) or hack the code or rollback to older drivers (5/2015). As JS wrote in other forum just try to send feature enhancement request to NVidia.

M.C>

#15

Thanks guys!

Jason,
How do I request feature like setting max resolution to 1920x1080 or set that at any other desired resolution for our K2 grid using the latest driver. It seems nvidia is trying to enforce all the restriction to sell their license manager. We spent 6K for the K2 grid and want to use every penny and feature out of it.

NVidia should understand and provide necessary resources for existing hardwares they sold to their customers, and separate driver for grid 2.0 if necessary.

Syed

#16

JS wrote down here: https://gridforums.nvidia.com/default/topic/543/general-discussion/grid-2-0/post/2098/#2098.

#17

Thanks M.C

Syed

#18

The K2 is unaffected by the release of GRID 2.0 which is only required for GRID on Maxwell generation Tesla boards and future hardware releases.

K2 has all the features and functionality that were supported prior to GRID 2.0. Nothing has been changed, removed or downgraded.

K2 does have separately provided and maintained drivers. The GRID 2.0 driver and software stack is completely separate and is even downloaded from a different location to avoid confusion.

As MC has directed you to the other thread, you can request this as a feature enhancement through your Nvidia contacts who will help you develop the business justification.

#19

I think that it is not true. There are only deleted ~20 files (linux driver, licensing pdf and server and m6conf files in dom0.rpm) from NVIDIA-GRID-vGPU-kepler-XenServer-6.5-352.54-354.13.zip (2015.10.28). All function including problematic vgpuConfig.xml+nvidia-vgpud are deployed with kepler package.

M.C>

PS: readme+user guide pdf are the same as in GRID2.0 including all information about M6/M60, linux support and licensing issues. There will be more confused users.