您使用PVS还是MCS来部署VM?
如果是,您的主映像附加了哪个vGPU配置文件....确保您的VM具有与主服务器相同的vGPU配置文件。
当您更改vGPU配置文件时,操作系统会将其视为不同的GPU,这通常需要重新启动。
如果你有非持久性虚拟机,这可能是正在发生的事情......
当您使用512MB配置文件时,您将不会在任何这些VM上使用NVEnc。
NVEnc仅适用于1GB以上的配置文件。
此外,除非您需要Quadro功能,否则1B配置文件在许可证上会更便宜。
问候
本
以上来自于谷歌翻译
以下为原文
Are you using PVS or MCS to deploy your VMs? If yes, which vGPU profile does your Master image have attached .... Make sure your VMs have the same vGPU profile as your Master. When you change vGPU profiles, the OS will see it as a different GPU, and this typically requires a reboot. If you have non-persistent VMs, this could be what's happening ...
As you're using a 512MB profile, you won't be using NVEnc on any of those VMs. NVEnc only works with 1GB profiles and above. Also, unless you need Quadro features, a 1B profile will be cheaper on the licenses.
Regards
Ben
您使用PVS还是MCS来部署VM?
如果是,您的主映像附加了哪个vGPU配置文件....确保您的VM具有与主服务器相同的vGPU配置文件。
当您更改vGPU配置文件时,操作系统会将其视为不同的GPU,这通常需要重新启动。
如果你有非持久性虚拟机,这可能是正在发生的事情......
当您使用512MB配置文件时,您将不会在任何这些VM上使用NVEnc。
NVEnc仅适用于1GB以上的配置文件。
此外,除非您需要Quadro功能,否则1B配置文件在许可证上会更便宜。
问候
本
以上来自于谷歌翻译
以下为原文
Are you using PVS or MCS to deploy your VMs? If yes, which vGPU profile does your Master image have attached .... Make sure your VMs have the same vGPU profile as your Master. When you change vGPU profiles, the OS will see it as a different GPU, and this typically requires a reboot. If you have non-persistent VMs, this could be what's happening ...
As you're using a 512MB profile, you won't be using NVEnc on any of those VMs. NVEnc only works with 1GB profiles and above. Also, unless you need Quadro features, a 1B profile will be cheaper on the licenses.
Regards
Ben
举报