VMware Cloud Community
exto
Contributor
Contributor

Vendor Licensing Socket vs. Virtual CPU

I was wondering if anybody out there could help me out here.

I am looking to Virtualize a specific application, however the Vendor has been stringent and will not allow for licensing by Virtual CPU/Core. They currently only allow by physical socket.

I was wondering if anyone has any ammunition/strategies that I could use to help fight this battle with my Vendor. or perhaps some experience someone has in dealing with another Vendor in a similar situation.

Also, if anyone knew if it actually violates the "SOCKET" licensing agreement by moving it to a Virtual CPU (ie... if I have a 1cpu license, limiting to 1 cpu within VMWare).

It is unfortunate that the Vendor will not co-operate, would love to hear from anyone that can provide any insight. Winning these types of battles will help make VMWare even more successful.

ps. Although switching Vendors is an option, I would prefer not to due to rework.

0 Kudos
4 Replies
Ken_Cline
Champion
Champion

I'd suggest sending a note to sales@vmware.com and ask them to intervene on your behalf. Sometimes, all it takes is a little education. Other times, it takes enough customers taking their money elsewhere Smiley Sad

Ken Cline

Technical Director, Virtualization

Wells Landers

TVAR Solutions, A Wells Landers Group Company

VMware Communities User Moderator

Ken Cline VMware vExpert 2009 VMware Communities User Moderator Blogging at: http://KensVirtualReality.wordpress.com/
0 Kudos
Rodos
Expert
Expert

Welcome to the forums.

Go to this page on the VMware web site

Down the bottom it has this text

>If you have questions about a software vendor's support for running in a VMware environment, please consult with that specific vendor. If you have further questions, are an ISV who would like to be added to this list, or are dealing with a vendor that does not have a support policy for VMware, please feel free to email details to ISV Support Questions.

Follow that link and make sure you chase it up if they don't get in contact with you. VMware can speak to the vendor about their policy. It may solve the problem but if it does not you have done everything you can and you may help the next person.

Let us know how you get on, we would all be interested to know.

Rodos

Consider the use of the helpful or correct buttons to award points. Blog: http://rodos.haywood.org/

Rodos {size:10px}{color:gray}Consider the use of the helpful or correct buttons to award points. Blog: http://rodos.haywood.org/{color}{size}
0 Kudos
Texiwill
Leadership
Leadership

Hello,

Outside of getting VMware involved, they may not be able to assist much, I would tend to let the vendor know you will take your business to one who does support the licensing you require. Let them know that virtualization is here to stay and that you need to consider the infrastructure and licensing together.


Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

Blue Gears and SearchVMware Pro Blogs: http://www.astroarch.com/wiki/index.php/Blog_Roll

Top Virtualization Security Links: http://www.astroarch.com/wiki/index.php/Top_Virtualization_Security_Links

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
0 Kudos
exto
Contributor
Contributor

I ended up using material from some of the Major vendors which support VCPU licensing(IBM,BEA,MS,etc..). My Vendor ended up changing their mind and will now support a VCPU strategy and are currently formalizing a policy.

Thanks for the help.

0 Kudos