Hi,
we have been experiencing serious SES-related problems with our Hyper-V-Failovercluster for a couple of weeks now.
Since this is really annoying and we do not want to trouble our heads about it anymore we thought extending one of our Proxmox-Clusters and migrating all the virtual machines (vhdx) to it could be a good idea.
We should be able to handle the migration itself but have some questions about proper licensing of our Windows VMs.
The first question is: Are there any known issues when it comes to licencing Windows Server VMs on third-party-hypervisors? And how is it done technically?
As far as we know it should be no legal problem to run Windows Server VMs on another hypervisor since the Windows license refers to bare metal and not to the operating system running on it.
We have two nodes with two six-core-CPU´s each and two Windows Server Datacenter Licences (16 cores each - which is the minimum).
Licence - Activation on a Windows Server WM is quite easy if it runs on a Hyper-V-Server: You simply type in "slmgr /ipk <AVMA_Key>" in an elevated cmd-shell and it is done. AVMA stands for Automatic VM Acitvation, it is the default way to activate Windows VMs on Hyper-V (https://docs.microsoft.com/de-de/windows-server/get-started-19/vm-activation-19). On the other hand the purchased licence is used to activate the Hyper-V-Server. So slmgr makes sure that there is a properly licenced Hyper-V-Server. Which just works fine if you use one.
But what will do the trick on a proxmox cluster? Where to type in the Windows Datacenter licence to acitvate our Windows Server VMs? Do we have to use our Datacenter Licence to activate the guest operating sytems?
The second question: Is it sufficient licensing only two of five Proxmox nodes with a Windows Datacenter License if we make sure that all of our Windows Server VMs run exclusively on those two nodes? Could we move the VMs to one of the other three nodes in an emergency (failover case - this should be possible with failover rights, I think)?
Any help is highly appreciated.
Cheers!
Gergö
we have been experiencing serious SES-related problems with our Hyper-V-Failovercluster for a couple of weeks now.
Since this is really annoying and we do not want to trouble our heads about it anymore we thought extending one of our Proxmox-Clusters and migrating all the virtual machines (vhdx) to it could be a good idea.
We should be able to handle the migration itself but have some questions about proper licensing of our Windows VMs.
The first question is: Are there any known issues when it comes to licencing Windows Server VMs on third-party-hypervisors? And how is it done technically?
As far as we know it should be no legal problem to run Windows Server VMs on another hypervisor since the Windows license refers to bare metal and not to the operating system running on it.
We have two nodes with two six-core-CPU´s each and two Windows Server Datacenter Licences (16 cores each - which is the minimum).
Licence - Activation on a Windows Server WM is quite easy if it runs on a Hyper-V-Server: You simply type in "slmgr /ipk <AVMA_Key>" in an elevated cmd-shell and it is done. AVMA stands for Automatic VM Acitvation, it is the default way to activate Windows VMs on Hyper-V (https://docs.microsoft.com/de-de/windows-server/get-started-19/vm-activation-19). On the other hand the purchased licence is used to activate the Hyper-V-Server. So slmgr makes sure that there is a properly licenced Hyper-V-Server. Which just works fine if you use one.
But what will do the trick on a proxmox cluster? Where to type in the Windows Datacenter licence to acitvate our Windows Server VMs? Do we have to use our Datacenter Licence to activate the guest operating sytems?
The second question: Is it sufficient licensing only two of five Proxmox nodes with a Windows Datacenter License if we make sure that all of our Windows Server VMs run exclusively on those two nodes? Could we move the VMs to one of the other three nodes in an emergency (failover case - this should be possible with failover rights, I think)?
Any help is highly appreciated.
Cheers!
Gergö