问题

Windows 2019标准版AHV上的宾客OS许可

C
  • CESC
  • 探路者
  • 0答复

你好，

我们已经在Windows 2019标准版OS上部署了几个Guest VM，我们的6个节点群集。两位客人均配备了1个带有2个内核的VCPU以及16和32个内存。我们已经获得了操作系统的标准纸牌许可证。该管理程序正在AHV版本20170830.337和AOS上运行-5.10.8.1 LTS。

Windows Server OS是否有任何特定的许可模型可以在AHV上运行？如何确定Windows许可证？请帮助。

Hi,<\/p>

We have deployed couple of guest VMs on Windows 2019 Standard Edition OS on our 6 node cluster. Both the guests are configured with 1 VCPU with 2 cores along with 16 & 32 memory respectively. We have procured standard paper license of the OS. The hypervisors are running on AHV version 20170830.337 & AOS - 5.10.8.1 LTS.<\/p>

Is there any specific licensing model for Windows Server OS to run on AHV? How are the Windows licenses determined? Kindly help.<\/p>","quoteUsername":"CESC","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

3个答复

一个

@CESC

您的MS许可将对Nutanix完全不可知，必须单独处理。即使您正在使用Nutanix CE运行实验室，您仍然需要为Windows VM持有MS许可。我强烈建议您与您的MS许可VAR进行交谈以获得充分的澄清并确保您在许可合同中运行。

如果您使用的是试用 /评估Windows Server版本，那么只要您处理这些时间限制的时间，就可以了。

If you’re an MSDN license holder then you might be OK if you’re using MSDN keys for your windows installs - there are limitations to how MSDN instances are used so again you’ll need to review with MS or a licensing VAR to ensure compliance. I think that with MSDN - if you build a Windows MSDN VM that any user who uses that VM would need to hold their own MSDN developer license, ie one developer can’t ‘own’ all the Windows server to get them all legit under one license. I might be way off here so you’ll need to verify - I’m not an MSDN license holder though I do morn the loss of the MS TechNet subscription...

如果以前的海报得出结论，这是用于生产部署的，那么您将向MS支付一吨现金。他们以停车场的薪水为薪水，在停车场的一个位置支付 - 您必须确保为群集中的每个物理CPU核心拥有MS Windows Server数据中心许可证。您可以通过制作一些簇“仅Windows”来限制某些许可费用，以便您不在Windows许可的核心上运行Linux或其他工作负载…。另请注意，您可以从管理中的主机中添加或删除Microsoft许可的频率有限制 - 这似乎消除了我们根据加载动态分配许可的能力……鳄鱼和鲨鱼在这里，如果您有任何疑问，甚至遥不可及you may not fully understand your licensing for VMs you need to engage your VAR support team to nail that down or you could be in for large fines if you’re ever audited. Same goes for Oracle and other vendors with the ‘pay for the parking lot’ licensing model.

希望这个对你有帮助。

@CESC<\/user-mention>\u00a0<\/p>

Your MS licensing will be completely agnostic to Nutanix and must be dealt with separately. Even if you\u2019re running a lab with Nutanix CE you may still be required to hold MS licensing for Windows VMs.\u00a0I highly recommend you talk to your MS licensing VAR to get full clarification and ensure you\u2019re operating within your licensing contracts.\u00a0<\/p>

If you\u2019re using trial \/ evaluation Windows Server editions then you should be just fine as long as you work withing the time limits those come with.\u00a0<\/p>

If you\u2019re an MSDN license holder then you might be OK if you\u2019re using MSDN keys for your windows installs - there are limitations to how MSDN instances are used so again you\u2019ll need to review with MS or a licensing VAR to ensure compliance. I think that with MSDN - if you build a Windows MSDN VM that any user who uses that VM would need to hold their own MSDN developer license, ie one developer can\u2019t \u2018own\u2019 all the Windows server to get them all legit under one license. I might be way off here so you\u2019ll need to verify - I\u2019m not an MSDN license holder though I do morn the loss of the MS TechNet subscription...<\/p>

If as the previous poster concluded that this is for a production deployment then you\u2019ll be paying MS a ton of cash. They operate on a pay for the parking lot vs pay for one spot in the parking lot - you have to ensure that you have a MS Windows Server Datacenter license for every single physical CPU core in the cluster. You can limit some of your licensing costs by making some clusters \u201cWindows Only\u201d so you\u2019re not running Linux or other workloads on cores licensed for Windows\u2026. Also note that there are restrictions to how frequently you can add or remove Microsoft licensing from a hypervisor host - this seems to remove our ability to dynamically allocate licensing based on loading\u2026\u00a0crocodiles and sharks lie here, if you have any questions or even remotely think you may not fully understand your licensing for VMs you need to engage your VAR support team to nail that down or you could be in for large fines if you\u2019re ever audited. Same goes for Oracle and other vendors with the \u2018pay for the parking lot\u2019 licensing model.<\/p>

\u00a0<\/p>

Hope this is of some help.<\/p>","quoteUsername":"ADWM","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

s

对于Win 2019标准；

  • 服务器中的所有物理内核都必须获得许可
  • 每个处理器至少必须获得8个核心
  • 至少必须为每个服务器获得16个内核
  • 对于每两（2）个额外的OS或Hyper-V容器，服务器中的所有内核都必须再次获得许可。

多少虚拟CPU无关紧要。

因此，基本上，您必须每个物理节点购买16个核心许可证（如果您有16多个物理核心，则需要在此上方许可）才能获得2个VM。

因为这是一个6节点群集，您需要许可所有节点。16个内核 * 6节点= 96个核心许可。这将使您能够运行2个可以在所有机器上运行的标准VM。

即使您只想使用1个虚拟CPU运行1 VM，并且可以在6个物理节点上移动您至少必须以96个内核进行许可。

每两个VM都必须为他们可以运行的每台机器提供许可。

https://virtallyinclined.com/2019/03/27/windows-server-2019-licensing-calculator/

对于您所描述的，2个VM，在6个节点上运行，假设每个节点有16个内核。

  • 2核包装许可费用= $ 121.50
  • 每个虚拟主机的内核= 16
  • 每个虚拟主机2核包= 8
  • 所有虚拟主机的2核包= 48
  • 每个虚拟主机的成本= $ 972.00
  • 虚拟主机计数= 6
  • 所有主机的费用= $ 5,832.00

是的，运行2 VM的$ 6K。

12x 2019 Stardard VMS将使您大约$ 36K

无限的2019年数据中心VMS将使您大约$ 37K

欢迎获得Microsoft许可。

您会看到为什么数据中心变得有吸引力。

For Win 2019 Standard;<\/p>
m

为了添加上一个注释，使用Windows Server标准许可证，您只能在90天的时间内迁移一次VM，这意味着，如果AHV负载平衡函数在90天的时间内移动VM不止一次，您将违反Windows Server标准许可证。

我目前有一个带有3个节点的AHV群集，所有节点均已获得Windows Server数据中心许可，这意味着我们不仅没有90天限制，而且我们也没有对每个节点可以安装的VM的限制。数据中心许可的唯一问题是，您必须每两年支付一次软件保证，这一数字约为原始许可费用的1/3，但这使您可以在发布时升级到下一个操作系统。

我相信，从成本的角度来看，数据中心许可开始成为廉价的选项，即每个节点的每个节点有10个VM，我每个节点具有13个节点。

To add to the previous comment, with Windows Server Standard licenses you can only migrate a VM once in a 90-day period meaning that if the AHV load balancing function moves a VM more than once in a 90-day period you are in breach of the Windows Server Standard License.<\/p>

\u00a0<\/p>

I currently have an AHV cluster with 3 nodes and all nodes are licensed with Windows Server Datacenter meaning we are not only without the 90-day limit but we also have no limit on the number of VMs we can install per node. The only issue with the Datacenter licensing is that you have to pay the Software Assurance up every two years which costs about 1\/3 of the original license cost, but this allows you to upgrade to the next OS the moment it is released.<\/p>

\u00a0<\/p>

I believe from a cost point of view the Datacenter licensing starts to become the cheaper option at the point of having 10 VMs per node of which I have 13 per node.<\/p>","quoteUsername":"MBlenkiron","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">

回复


条款和条件
Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
Functional","cookiepolicy.modal.level2":"Normal
Functional + analytics","cookiepolicy.modal.level3":"Complete
Functional + analytics + social media + embedded videos"}}}">
Baidu