{"id":2829,"date":"2020-06-18T08:00:25","date_gmt":"2020-06-18T15:00:25","guid":{"rendered":"https:\/\/www.www.pogolinux.com\/blog\/?p=2829"},"modified":"2020-06-22T09:54:28","modified_gmt":"2020-06-22T16:54:28","slug":"vmware-licensing-core-based-pricing-model","status":"publish","type":"post","link":"https:\/\/www.pogolinux.com\/blog\/vmware-licensing-core-based-pricing-model\/","title":{"rendered":"Announcement: VMware Core-Based Pricing Model Licensing Update"},"content":{"rendered":"<p>If you manage a virtualized environments at your organization, you should be aware that effective April 2, 2020, VMware moved from a <em>per-CPU pricing model <\/em>to a <em>core-based pricing model<\/em><em>. <\/em>As a result of this licensing change, VMware will require an additional CPU license if a server&#8217;s CPU has more than 32 physical cores.<\/p>\n<p>Announced on a <a href=\"https:\/\/www.vmware.com\/company\/news\/updates\/cpu-pricing-model-update-feb-2020.html\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">VMware company blog post<\/a>, the infrastructure virtualization software company said the change is intended to simplify its software licensing with industry-standards by moving in lock-step with the direction of the server hardware market. (VMware\u2019s <strong><em>Enterprise PKS<\/em><\/strong> and <strong><em>NSX Data Center<\/em><\/strong> subscriptions are some examples of the products that use CPU cores as the licensing metric).<\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_89 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.pogolinux.com\/blog\/vmware-licensing-core-based-pricing-model\/#VMware_Core-based_Pricing_Model\" >VMware Core-based Pricing Model<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.pogolinux.com\/blog\/vmware-licensing-core-based-pricing-model\/#What_this_means_for_Intel_Xeon_and_AMD_EPYC_Users\" >What this means for Intel Xeon and AMD EPYC Users<\/a><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"VMware_Core-based_Pricing_Model\"><\/span><strong>VMware Core-based Pricing Model<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>With the change, if a VMware customer has a server with a CPU that has more than 32 cores, an additional per CPU license will need to be purchased. Customers who purchased VMware software per-CPU licenses prior to April 30, 2020 will be eligible for free per-CPU licenses to cover the additional\u00a0 cores on those CPUs.<\/p>\n<p>Under the new core-based pricing model, one CPU license covers up to 32 cores in a single CPU. If a VMware customer has a server with a CPU that has more than 32 physical cores, an additional per CPU license will need to be purchased (e.g. If a customer has a 64-core processor, the business will need to purchase two VMware CPU licenses). To provide some examples:<\/p>\n<p style=\"text-align: center;\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-5023 aligncenter\" src=\"https:\/\/www.pogolinux.com\/blog\/wp-content\/uploads\/2020\/06\/20-Q2-blog-article_servers-vmware-licensing-update.jpg\" alt=\"\" width=\"725\" height=\"400\"><\/p>\n<p>&nbsp;<\/p>\n<h2><span class=\"ez-toc-section\" id=\"What_this_means_for_Intel_Xeon_and_AMD_EPYC_Users\"><\/span><strong>What this means for Intel Xeon and AMD EPYC Users<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>In recent years, both current-generation <a href=\"https:\/\/www.pogolinux.com\/blog\/intel-xeon-servers-cascade-lake-refresh-overview\/\">Intel Xeon Scalable<\/a> and <a href=\"https:\/\/www.pogolinux.com\/blog\/rackmount-server-solutions-amd-epyc-processor-overview\/\">AMD EPYC 7002 Series processors<\/a> have moved toward x86 architectures increased core-counts per socket. These higher core-count CPUs with increased clock-speeds deliver more cycles and more caching capabilities for data to interact with applications or high-transaction workloads &#8211; ideal for virtualization. VMware&#8217;s licensing change will impact data center processors with high core counts such as AMD\u2019s EPYC Rome and Intel\u2019s upcoming 56-core Cooper Lake models, effectively doubling the price for VMware licenses for 48-core or 64-core models.<\/p>\n<p>The company believes that changing the pricing model will not impact on the vast majority its customers that are at (or below) the 32-core threshold on Intel and AMD-based servers.<\/p>\n<p>For the few customers who are currently deploying VMware on CPUs with more than 32 cores, or for those that are in the process of purchasing physical servers with more than 32 cores per CPU, we are providing a grace period after the licensing metric change goes into effect on April 2, 2020.<\/p>\n<p>Any customer who purchased VMware software licenses, for deployment on a physical server with more than 32-cores per CPU, prior to April 30, 2020 will be eligible for additional free per-CPU licenses to cover the CPUs on that server.<\/p>\n<p>Questions about your VMware deployment? <a href=\"https:\/\/www.pogolinux.com\/blog\/book-meeting\/\">Schedule a time<\/a> or give us a call at <strong>(888) 828-7646<\/strong> to learn more about how VMware&#8217;s new pricing model will impact your server infrastructure.<\/p>\n<p><a href=\"https:\/\/www.pogolinux.com\/products\/intel-servers\" target=\"_blank\" rel=\"noopener noreferrer\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-4957 alignleft\" src=\"https:\/\/www.pogolinux.com\/blog\/wp-content\/uploads\/2020\/05\/blog-article-footer_intel-xeon-servers.jpg\" alt=\"\" width=\"725\" height=\"200\"><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>If you manage a virtualized environments at your organization, you should be aware that effective April 2, 2020, VMware moved from a per-CPU pricing model to a core-based pricing model. As a result of this licensing change, VMware will require an additional CPU license if a server&#8217;s CPU has more than 32 physical cores. Announced&#8230;<\/p>\n","protected":false},"author":6,"featured_media":5040,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[198,248,1,3],"tags":[],"class_list":["post-2829","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-amd-servers","category-intel-servers","category-rackmount-servers","category-workstations"],"_links":{"self":[{"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/posts\/2829","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/comments?post=2829"}],"version-history":[{"count":26,"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/posts\/2829\/revisions"}],"predecessor-version":[{"id":5045,"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/posts\/2829\/revisions\/5045"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/media\/5040"}],"wp:attachment":[{"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/media?parent=2829"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/categories?post=2829"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.pogolinux.com\/blog\/wp-json\/wp\/v2\/tags?post=2829"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}