Hello,
following is the licensing model with Windows Server 2012 R2 Editions:
- Datacenter includes virtualization rights* for unlimited number of Windows Server VMs
- Standard includes virtualization rights for 2 Windows Server VMs
- Hyper-V Server does not include virtualization rights
* Example about virtualization rights: In case you purchase a Windows Server 2012 R2 Standard license for your physical server, you are allowed to run 2 Windows Server VMs on this server without purchasing extra licenses.
Except the licenses, it depends on your hardware how many VMs you will be able to run.
Typical bottlenecks are here the disks and memory. Make sure that you purchase at least 10K disks and run them in a RAID1.
Please note that for information regarding Microsoft Licensing, you should contact the Microsoft Licensing Team. Here in the forum we can't give definitive answers, only advices.
Best Regards,
Jens
With that information, no one can tell you. You don't mention storage, which usually the first bottleneck, technically storage I/O. How many cores do the CPUs have, that's also important.
What are your VMs doing? CPU intensive, RAM intensive, disk intensive? You need to get a good measure of your current environment. If your VMs need 16-32GB of RAM vs 2-4GB of RAM that makes a huge difference in the number of VMs you're running.
There's no formula that works for all scenarios as everyone needs different things.
You can look at these tools to help you: http://h71019.www7.hp.com/ActiveAnswers/us/en/sizers/hp-sizer-server-virtualization.html
http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA1-2975ENW.pdf
You still need to know the metrics of your environment.
With that information, no one can tell you. You don't mention storage, which usually the first bottleneck, technically storage I/O. How many cores do the CPUs have, that's also important.
What are your VMs doing? CPU intensive, RAM intensive, disk intensive? You need to get a good measure of your current environment. If your VMs need 16-32GB of RAM vs 2-4GB of RAM that makes a huge difference in the number of VMs you're running.
There's no formula that works for all scenarios as everyone needs different things.
You can look at these tools to help you: http://h71019.www7.hp.com/ActiveAnswers/us/en/sizers/hp-sizer-server-virtualization.html
http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA1-2975ENW.pdf
You still need to know the metrics of your environment.
- Proposed as answer by Leo HanMicrosoft contingent staff, Moderator 1 hour 20 minutes ago
With that information, no one can tell you. You don't mention storage, which usually the first bottleneck, technically storage I/O. How many cores do the CPUs have, that's also important.
What are your VMs doing? CPU intensive, RAM intensive, disk intensive? You need to get a good measure of your current environment. If your VMs need 16-32GB of RAM vs 2-4GB of RAM that makes a huge difference in the number of VMs you're running.
There's no formula that works for all scenarios as everyone needs different things.
You can look at these tools to help you: http://h71019.www7.hp.com/ActiveAnswers/us/en/sizers/hp-sizer-server-virtualization.html
http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA1-2975ENW.pdf
You still need to know the metrics of your environment.
- Proposed as answer by Leo HanMicrosoft contingent staff, Moderator Thursday, August 27, 2015 5:40 AM
With that information, no one can tell you. You don't mention storage, which usually the first bottleneck, technically storage I/O. How many cores do the CPUs have, that's also important.
What are your VMs doing? CPU intensive, RAM intensive, disk intensive? You need to get a good measure of your current environment. If your VMs need 16-32GB of RAM vs 2-4GB of RAM that makes a huge difference in the number of VMs you're running.
There's no formula that works for all scenarios as everyone needs different things.
You can look at these tools to help you: http://h71019.www7.hp.com/ActiveAnswers/us/en/sizers/hp-sizer-server-virtualization.html
http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA1-2975ENW.pdf
You still need to know the metrics of your environment.
- Proposed as answer by Leo HanMicrosoft contingent staff, Moderator Thursday, August 27, 2015 5:40 AM
https://www.virten.net/vmware/vmware-vsphere-esx-and-vcenter-configuration-maximums/ it shows maximum
VM supports per host and limitation it is right?
"maximum number of VM can be installed on per host e.g 2 processor , 120 GB RAM, storage SAN around 20 TB "
The number of VMs you can INSTALL is limited to the amount of storage on your system. If you create one VM that uses 20 TB of storage, you can install a single VM. If each of your VMs use only 2 GB of storage, then you can install about 10,000 VMs. How many you can LOAD INTO MEMORY is limited to the amount of memory on your system. Assume the hypervisor itself uses about 2 GB. That leaves 118 GB (theoretically) available for VMs. If you create one VM that uses 64 GB of memory and another that uses 54 GB, you can load two VMs. If each of your VMs only takes 512KB of memory, you could load 236. (Actually, it will be less because each VM needs some additional memory space in the hypervisor). How many VMs can actually run is limited by the horsepower of the host system and the CPU requirements of the VMs. There is no simple formula for this because it is completely dependent upon what the VMs are doing. If they are simply sitting there with each one running its own operating system and no applications, you can get a lot of VMs 'running'. However, if you have CPU-hungry VMs, you might get only a couple running.
What I am attempting to say here is that a lot more information needs to be provided in order to answer your question. And you are the only one who will be able to answer it after you have gathered the disk, memory, and CPU requirements of the VMs you want to run.
1024 is the maximum number of VMs a host can run. Which is largely irrelevant in the real world.
https://technet.microsoft.com/en-us/library/jj680093.aspx
I've given you sizing guides, you need to measure your environment to get a useful answer, fill in that info, and get a basic answer.
Hi Cabpeter,
Since you have allocated all 120GB, we could not create a new VM unless we add more memory.
If you allocate 17GB to the 6 VMs, then we would be able to allocate 18GB to a new VM.
Here are the system requirements of Server 2008 and 2012, we could allocate memories according to them:
Windows Server 2008 System Requirements:
https://technet.microsoft.com/en-us/windowsserver/bb414778.aspx?f=255&MSPPError=-2147217396
System Requirements and Installation Information for Windows Server 2012 R2:
https://technet.microsoft.com/en-us/library/dn303418.aspx?f=255&MSPPError=-2147217396
Best Regards,
Leo
thanks so total physical server RAM needs to use same amount of RAM meaning 120 GB physical RAM needs to allocate only less than 120 GB not more than 120 GB my assumption is if I have 2 Octet core then we can allocate more than 16 VMs each VM 1 CPU but still I am not sure about CPU and RAM allocation for VM's like what is limitation and basic calculations
Overcommit means trying to 10 pounds of content into a five pound bag. Yes, VMware can do this, but they don't recommend it because it has a significant negative impact on performance. If there is only 120 GB of physical memory, and you absolutely have to have 150 GB of memory to run the workload, that means things are going to get paged out of memory (very slow process) and sometimes the wrong things, such as kernel code, can get paged out.
Microsoft uses a concept called dynamic memory. You can assign a range of memory to the VMs running on a host. As a machine needs more memory, it will ask for it. When it no longer needs it, it gives it back. If it needs it and there is no more to give, i.e. you are trying to overcommit memory, it will fail in the request.
How well this works in your environment is completely unknown to us. You need to monitor your particular requirements to see if it makes sense for you.
"Microsoft uses a concept called dynamic memory means Hyper will supports more workload?"
No, dynamic memory does not mean Hyper-V will support more workload than VMware. When all is said and done, the same physical hardware can support a very similar workload. If you are trying to use every last byte of memory on either system, you will start to run into issues.
Earlier, you were trying to get 6 20 GB VMs in 120 GB of physical memory. In neither system is the calculation that straightforward. In both cases, the hypervisor, Hyper-V or ESXi, requires the use of some of the physical memory. That is not a fixed amount, but let's assume each of them needs about 2 GB. Then in addition to the memory you assign to each VM, the hypervisor has to set aside 'management' space for each VM. After all, the hypervisor is the authority on what physical memory gets mapped to what virtual machine. So the hypervisor sets up tables in its memory to keep track of which VMs are using which physical memory. Similarly, there is a mapping between the physical cores on the host and the virtual CPUs in the VMs. More space in the hypervisor. As a result, there is overhead associated with each VM created. The last time I made the comparison, Hyper-V used less overhead per VM than did ESXi, so if you were trying to cram the absolute maximum number of small VMs onto a physical machine, Hyper-V stood a chance of getting maybe one or two more than ESXi. But it is completely dependent upon the workload.
Your questions are very theoretical. Either hypervisor will work. Hyper-V is cheaper if you are running Windows Server VMs. Each hypervisor has some things the other hypervisor does not have. Trying to make a decision on a hypervisor based on a single hardware platform configuration is not a fruitful use of time.
Hyper-V does not put a limit on the number of vCPUs per logical processor. That is completely dependent upon the application. Some applications do not like hyperthreaded logical processors, so you might want to turn that off on some Hyper-V hosts. Other applications work fine with hyperthreaded logical processors. Hyper-V has no way of telling what the application requirements are in regards to vCPUs to logical processor, so it does not enforce any limitation.
That's why I am saying so many of your questions are theoretical. Hyper-V imposes very, very few constraints. But once you put your own applications on the system, you are going to find that your applications create all sorts of constraints. That has nothing to do with the hypervisor.
Hi Cabpeter,
If the VCPU you mentioned means the Virtual Processors of VM.
1. You can use more than 16.
2. In Hyper-V, in one VM, no more than 16. All VMs together, more than 16.
Best Regards,
Leo
Under Windows Server 2012 there is no recommendation Ratio, only a natural
Hi Cabpeter,
1, 3:
>>third question what is formula or limitation of CPU in Vmware or Hyper V my assumption is if 2 CPU with Octa core means 16 Virtual CPU so we can use 16 CPU's I am right?2 CPU: physical CPU. Octa core: logical CPU.
For one VM: no more than 16 Virtual CPU.
2:
Yes.
Best Regards,
Hi Cabpeter,
Open Task Manager on host, then you could see the number of logical CPUs.
Open settings of VM, expand Processors, then you could see the number of virtual processors.
Of one VM, the number of virtual processors could not be larger than the number of logical CPUs. That means you can use 16 VCPUs.
Best Regards,
Leo
Thanks Please explain what is logic and virtual processor second question how to set logical processor third question if I have 2cpu with octaccor processor so how many logical and virtual processor fourth questions how much we use for guest vm
Hi Cabpeter,
1. We could regard Logical CPU as the core of physical CPU. About the detailed principle, we could ask the manufacturer of the CPU. A virtual processor is more like processing time. The hypervisor takes the logical processors and chunks then into processing
resources that are in turn used as they are needed. (According to BrianEH's post.)
2. It could not be set. It comes with physical CPU.
3. I have explained twice. 16 Logical CPUs. For one VM, no more than 16 Virtual Processors.
4. It depends on the hardware requirement of the guest OS.
Besides, it is better for reading and understanding if you could add punctuations between sentences please.
Best Regards,
Leo