Table of contents

Contents
1.0 - Introduction ....................................................................................................................... 2
2.0 Features in VMware when compared to Microsoft Microsofts Hyper V Server 2012 ...... 2
2.1 - Local machine processor................................................................................................ 2
2.2 - Host CPUs: ................................................................................................................... 2
2.3 - Maximum supported running VMs .............................................................................. 2
2.4 - Nested virtualisation: ..................................................................................................... 2
2.5 - Integration with AWS: ................................................................................................... 3
3.0 Features in Microsoft Microsofts Hyper V Server 2012 when compared to VMware
vSphere ...................................................................................................................................... 3
3.1 - Time in deploying servers:............................................................................................. 3
3.2 - Maximum supported host memory: ............................................................................... 3
3.3 - Maximum Virtual Switches: .......................................................................................... 3
3.4 - Cost ................................................................................................................................ 3
4.0 - Comparison between the two platforms based on some new features. ............................. 5
4.1 - Feature in trial version ................................................................................................... 5
5.0 - Service support for Microsoft Hyper V Server 2012: ....................................................... 5
6.0 - Open source challenge for Microsoft Hyper V ................................................................. 6
7.0 - Require updates: ................................................................................................................ 6
8.0 - Recommendation ............................................................................................................... 6
8.1 Requirement 1 ............................................................................................................... 6
8.2 Requirement 2 ............................................................................................................... 6
9.0 Bibliography ..................................................................................................................... 7

List of figures
Fig. 1- The rough cost analysis between VMware vSphere and Microsoft Hyper V4
Fig. 2 - The annual cost estimation between vSphere an Hyper V in graphical form . 4
Fig. 3 - The live migration of the virtual hard disk from the source device to the destination
device even when the VM is running 5
1.0 - Introduction
Which platform is best for the cloud infrastructure for intertrode network VMware vSphere
or Microsoft Microsoft Hyper V Server 2012 .
Three years have have passed to design intrtrode nrtwork on the vm ware vsphere and thb
time is there to change the infrastructure and now one question is in mind of the customere
whether to stay with the older cloud or would shift to the new one which is Microsoft hyper v
and Microsoft is a well known brand in the whole world in the IT field.
Bothe the cloud service providers are at war to implement their service in this field and
According to article published by Contel (Bradford, 2015) VM Ware is still a dominant force
in the market which has several products related to virtualisation and VM and are specifically
designed to meet the client need in the IT field and products like vSphere still scores high in
the customer satisfaction field which is required in todays marketing
According to (Antonowicz, 2008) both the platforms are Microsoft Hyper V Server 2012isor
based solutions and donot require any additional OS and are directly installed on the
hardware of the system.

2.0 Features in VMware when compared to Microsoft Microsofts Hyper V

Server 2012
Some features are such that which attracts client to remain with the VMware ESX like
2.1 - Local machine processor
VMware ESX supports both 32 bit and 64 bit host. Whereas Microsoft Hyper require only 64
bit host like if some traditional systems are there then Hyper V cannot support it.
2.2 - Host CPUs:
Maximum logical host CPU is the CPU number in VM host which VMware ESX support is
64 whereas Hyper V supports 16 (it can go with more than 16 but it will not support)
2.3 - Maximum supported running VMs
Number of vms which can run on same time or simultaneously in V Sphere can be up to 128
whereas it gets limited in number when Microsoft Hyper V Server 2012 comes .
2.4 - Nested virtualisation:
In the discussions of the VMware technology network (Eric_Allione, 2017) on the site one
most important thing was known which is the need of the future is that the VMware supports
nested virtualisation. In nested virtualisation another Microsoft Hyper V Server 2012isor is
run on the main Microsoft Hyper V Server 2012isor. Main Microsoft Hyper V Server
2012isor is called the level 0 Microsoft Hyper V Server 2012isor and the nested or guest
Microsoft Hyper V Server 2012isor is called the level 1 Microsoft Hyper V Server 2012isor
and so on the levels are there
2.5 - Integration with AWS:
VMware vSphere will soon integrate with the AWS(Amazon Web Services ) to offer large
services to its users. Users can now get the features of AWS and vSphere on the same
platform.

3.0 Features in Microsoft Microsofts Hyper V Server 2012 when compared

to VMware vSphere
But on other hand some attractive features are there which attracts client to shift to Hyper V
and are
3.1 - Time in deploying servers:
Hyper V take s less time to deploy server as compared to ESX also. It supports live migration
process and no downtime during maintenance which is the requirement of the today industry
which do not want to have a downtime no matters whether it is is for few minutes
3.2 - Maximum supported host memory:
In VMware vSphere, it is 256 Gb whereas if we focus on Hyper V it is approximately 8 times
than what vSphere supports which is 2 Tb.
3.3 - Maximum Virtual Switches:
Virtual Switches are needed in scalability of organisation to isolate one network from the
other and will be required in intertrode in future when the organisation will scale VMware
ESX support only 256 switches on the other hand Unlimited switches can be allocated by
Hyper V to its clients.
3.4 - Cost
The main factor which every client or organisation considers before implementing the
infrastructure on the cloud and according to (Roussey, 2016)the cost of Hyper V is less as
compared to what the cost is charged by ESX. Even if we are using the trial version of
VMware ESX then we cannot enjoy the full functions of it. The rough cost analysis of
shifting cloud infrastructure of intertrode network to Hyper V is calculated where we have
clicked on the existing user of the VM ware vSphere and the result is extreme that the cost of
the Hyper V is approximately three times less as compared to the cost for VMware vSphere
Fig 1 shows the cost calculated for Microsoft vSphere is approx. $35,000 per annum whereas
the cost of the VMware vSphere is approx. $114,000 which is three times more as compared
to the Hyper V. Fig shows that cost will include the licence of Microsoft also. We have
calculated the cost without the licence cost still it is cheaper.
Fig. 2 shows the annual cost estimation between Microsoft Hyper V an VMware vSphere
with the bar graph. It shows that the total cost of ownership for vSphere is mre than $100,000
per annum whereas it is near to $40,000 per annum for Microsoft vSphere.
Fig. 1- The rough cost analysis between VMware vSphere and Microsoft Hyper V

Fig. 2 - The annual cost estimation between vSphere an Hyper V in graphical form
4.0 - Comparison between the two platforms based on some new features.
4.1 - Feature in trial version
For the trial version (Mauro, 2016) Hyper v provides the same features in trial version which
are present in the paid version whereas in the trial version of the VMware vSphere only
limited to backup data feature and other limited features are there and if anyone wants to try
the additional features then he or she has to pay to go for enterprise version.
Example of one most of the most essential feature which is live migration in which the
storage and the host which are live can be migrated without shutting our VMs as shown in
fig.3
This feature is not available in the trial version of the VMware vSphere where it is present in
the trial version of the Microsoft Hyper v.
So if a customer enjoys trial version then surely he will get attracted to the Hyper V.

Fig. 3 - The live migration of the virtual hard disk from the source device to the destination
device even when the VM is running.
Virtual disk format
Virtual disk in Microsoft was previously known as VHD where as it is upgraded to VHDX
now it supports much storage upto 64 Gb and it provides the protection against the power
failure.
In vSphere virtual disk format is available in different forms which are
1. Thick provisioning: the storage is registered and is allocated to the vm only
2. Thin provisioning: the storage is allocated according to the requirement and no
reservation of the storage is there.

5.0 - Service support for Microsoft Hyper V Server 2012:

According to (Roussey, 2016)Microsoft has poor quality support for service templates which
the client for intertrode network will not accept if there is any network issue as the whole
organisation will suffer. On the other hand VMware vSphere has good quality of service
provided to its clients.

6.0 - Open source challenge for Microsoft Hyper V

Hyper v is from the trustworthy house of Microsoft but much of the challenges that Microsoft
is facing is that the features provided to users are already being replicated by the open source
challengers. According to (Hurley, 2014)open source challengers are group of volunteers
who have the software licence they developed it after that they can distribute and also, they
are facing challenges as they have to follow the regulations predefined)

7.0 - Require updates:

Microsoft Hyper V Server 2012 supports less number of guest operating system as compared
to the vSphere and it requires regular updates during its lifetime. whereas less updates are
required by the VMware vSphere for its operation in lifetime

8.0 - Recommendation:
According to the features compared above both the Hypervisors Microsoft HyperV Server
2012 and VMwares vSphere we came to the conclusion that according to the requirements of
the client it depends whether the hypervisor of Hyper V or vSphere is best
8.1 Requirement 1
If the requirements of the intertrode network client for the network is
Live Migration, Scalability time, Cost
Then Microsoft Hyper V Server 2012 is good option as it covers all the three above reuired
options.
8.2 Requirement 2
On the other hand, if the requirement of the network client for intertrode network include
Nested virtualisation, Good service Support, Making virtualisation possible on 32 bit
processors if the company has legacy system processors, AWS services in future
Then in that case we recommend that the client should stay with the present Hypervisor
which is VMwares vSphere as it will also integrate with Amazon Web Services sooner
(Eric_Allione, 2017) which is the best option for the client then large number of IT services
he will get under the same platform.
9.0 Bibliography
Antonowicz, T. (2008, 8 14). What is the basic difference between VMware and Hyper-V.
Retrieved from Mosaic Technology: http://www.mosaictec.com/tessera/what-is-the-
basic-difference-between-vmware-and-hyper-v.htm
Bradford, C. (2015, 12). Virtualization Wars: VMware vs. Hyper V: Which is Right For Your
Virtual Environment? Retrieved from storage craft recovery:
https://www.storagecraft.com/blog/virtualization-wars-vmware-vs-hyper-v-which-is-
right-for-your-virtual-environment/
Eric_Allione. (2017, 4 12). VMware Technology network. Retrieved from discussions :
https://communities.vmware.com/thread/561677
Hurley, D. (2014, 6 24). 12 challenges for open source projects. Retrieved from open
source.com: https://opensource.com/life/14/6/12-challenges-open-source-projects
Mauro, A. (2016, 11 23). Microsoft Hyper v 2016 vs VM ware vsphere 5.6. Retrieved from
vinfrastructure blog: http://vinfrastructure.it/2016/11/microsoft-hyper-v-2016-vs-
vmware-vsphere-6-5/
Roussey, B. (2016, 11 23). PICK YOUR POISON: VMWARE VSPHERE VS. MICROSOFT
HYPER-V. Retrieved from Tech Genix: http://techgenix.com/vmware-vsphere-vs-
microsoft-hyper-v/