[ovirt-users] Windows Server 2016 client licensing costs

[Markus Stockhausen]

Hi Andrew,

you are on the right way. Although I'm no licensing expert our customers
have the same problem with Orache database since years. The policy boils
down to:

You must license every hardware that the VM might run on. Oracle even
wants to license hardware accross virtualization clusters if there might
be the possibility to relocate the VM between them online (VMWare 6
and higher).

>From a technical perspective OVirt virtualization has the same limits. So 
setup small dedicated Windows (or Oracle clusters) to keep costs down.

Markus

Mit freundlichen Grüßen
Markus Stockhausen
Teamleiter Softwaretechnologie
_______________________

Ubierring 11 · 50678 Köln

Telefon: +49 221 336 08-0
Mobil: +49 151 12040 606
E-Mail: stockhausen at collogia.de

Web: www.collogia.de

________________________________________
Von: users-bounces at ovirt.org [users-bounces at ovirt.org]" im Auftrag von "Andrew Wippler [Andrew.Wippler at lancasterbaptist.org]
Gesendet: Dienstag, 25. April 2017 18:24
An: users at ovirt.org
Betreff: [ovirt-users] Windows Server 2016 client licensing costs

We have been running oVirt for over two years now and we are quite satisfied
with it. Most of our infrastructure is CentOS VMs with about 7 Windows VMs which
are all running on 4 oVirt nodes.

With Microsoft changing their licensing terms for 2016, it sounds like I have to
pay a license fee for the physical hypervisor cores if I intend to run Windows
Server 2016 virtual machines on them - even if Windows is not the Host OS. Does
this sound about right?

Has anyone had to buy 2016 licenses yet? Did you also have to buy licenses to
cover the host? What are other hypervisor companies (i.e. VMWare, Citrix, etc.)
instructing their customers to do?

_______________________________________________
Users mailing list
Users at ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: InterScan_Disclaimer.txt
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170425/91bbb4f6/attachment.txt>