用于将分辨率限制为1920x1080的配置文件（使用xenserver的网格K2）

我安装的驱动程序是NVIDIA-GRID-vGPU-XenServer-6.5-352.46-354.13和NVIDIA-GRID-vGPU-XenServer-6.5-346.68-348.27
谢谢，
赛义德



以下为原文

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

您需要在远程处理堆栈中执行此操作，而不是在驱动程序级别执行此操作。



以下为原文

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

你好贾森，
感谢您的回复。
请详细解释如何。
赛义德



以下为原文

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



Syed

对于您正在使用的任何远程解决方案供应商而言，这是一个问题，因为大多数将默认为您连接的监视器的分辨率，并将该值呈现给VM，然后相应地设置分辨率。
您要做的是绕过它并修复分辨率，并且该方法在远程处理解决方案之间会有所不同。



以下为原文

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.

Jason，以前的驱动程序NVIDIA-GRID-vGPU-XenServer-6.5-346.68-348.27，当我编辑/usr/share/nvidia/vgx/grid_k240q.conf并设置plugin0.max_resolution 1920x1080;
使用K240Q配置文件的VM设置为使用MAX 1920x1080分辨率但是当我使用K2安装NVIDIA-GRID-vGPU-XenServer-6.5-352.46-354.13时，带有K240Q的VM忽略grid_k240q.conf参数并让用户分配2560x1600;
使用最新的驱动程序（NVIDIA-GRID-vGPU-XenServer-6.5-352.46-354.13）我如何限制用户分辨率为1920x1080。
我们的服务器都有两个带有所有K2网格的驱动程序。
请告诉我使用这两种驱动程序将用户限制在1920x1080的正确方法。
谢谢，
赛义德



以下为原文

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

不支持修改驱动程序。
您必须在显示级别对此进行管理，这意味着在远程协议中设置限制。



以下为原文

Modifying the driver is not supported.

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

我找到了技术答案：https：//gridforums.nvidia.com/default/topic/258/nvidia-grid-vgpu/documentation-for-vgpu-configs/post/2087/#2087。
要求NVidia从显示分辨率和frl参数中删除新的限制，或者NVidia应该接受来自* .conf的参数，其值较小，然后在vgpuConfig.xml中。
M.C>



以下为原文

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>

谢谢M.C！
我试图修改vgpuConfig.xml，但它只会破坏配置并阻止任何具有vgpu配置文件的VM启动。
虚拟机我遇到运行Windows 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 Windows 10

Syed

谢谢M.C！
我试图修改vgpuConfig.xml，但它只会破坏配置并阻止任何具有vgpu配置文件的VM启动。
虚拟机我在Windows 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

谢谢M.C！
我试图修改vgpuConfig.xml，但它只会破坏配置并阻止任何具有vgpu配置文件的VM启动。
虚拟机我在Windows 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

谢谢M.C！
我试图修改vgpuConfig.xml，但它只会破坏配置并阻止任何具有vgpu配置文件的VM启动。
虚拟机我在Windows 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

这不是，也从未得到过支持。
如果修改驱动程序和/或vGPU Manager，则将部署不受支持的解决方案。



以下为原文

This is not, and has never been supported.

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

是的，这是预期的。
正如我写的那样，这个文件有数字签名的元数据并且不支持修改（请参阅/ var / log / messages并在重新启动“/etc/init.d/nvidia-vgpud”时搜索“nvidia-vgpud：error”）。
唯一的方法是在NVidia方面允许降低参数（例如，某些软件工程师应接受来自* .conf或具有较低参数的运行时的数据）或破解代码或回滚到较旧的驱动程序（5/2015）。
正如JS在其他论坛中所写，只是尝试向NVidia发送功能增强请求。
M.C>



以下为原文



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>

多谢你们！
杰森，
如何请求将最大分辨率设置为1920x1080或使用最新驱动程序为我们的K2网格设置任何其他所需分辨率的功能。
似乎nvidia正试图强制执行所有限制来出售他们的许可证管理器。
我们花了6K用于K2网格，并希望使用每一分钱和功能。
NVidia应该了解并为他们销售给客户的现有硬件提供必要的资源，并在必要时为网格2.0提供单独的驱动程序。
赛义德



以下为原文

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

JS在这里写道：https：//gridforums.nvidia.com/default/topic/543/general-discussion/grid-2-0/post/2098/#2098。



以下为原文


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

谢谢M.C.
赛义德



以下为原文

Thanks M.C

Syed

K2不受GRID 2.0发布的影响，只有Maxwell一代Tesla板上的GRID和未来的硬件版本才需要。
K2具有GRID 2.0之前支持的所有特性和功能。
没有任何改变，删除或降级。
K2确实有单独提供和维护的驱动程序。
GRID 2.0驱动程序和软件堆栈是完全独立的，甚至可以从不同的位置下载以避免混淆。
由于MC已将您引导至其他主题，您可以通过Nvidia联系人请求此功能，以帮助您开发业务理由。



以下为原文



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.

我认为这不是真的。
从NVIDIA-GRID-vGPU-kepler-XenServer-6.5-352.54-354.13.zip(2015.10.28）中只删除了~20个文件（linux驱动程序，许可pdf和服务器以及dom0.rpm中的* m6 * conf文件）。
包含有问题的vgpuConfig.xml + nvidia-vgpud的所有功能都与kepler包一起部署。
M.C>
PS：自述文件+用户指南pdf与GRID2.0相同，包括有关M6 / M60，Linux支持和许可问题的所有信息。
会有更多混淆的用户。



以下为原文



I think that it is not true. There are only deleted ~20 files (linux driver, licensing pdf and server and *m6*conf 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.