Link to home
Start Free TrialLog in
Avatar of okamon
okamon

asked on

Hyper-v as a server role in production environment?

does install Hyper-v as a server role on top of windows OS a bad idea in production environment?  To me it's not real Virtualization and it's wasting system resource and windows OS might corrupt, need to patch very often, etc. And the time to rebuild it taking long time when disaster occurs. I have been using vmware esxi so far and I am very happy with it. But haven't tried the hyper option. Please share with me your experience and advices, thanks.
Avatar of Lee W, MVP
Lee W, MVP
Flag of United States of America image

How is it not real?  It's a type 1 hypervisor.

I don't consider ESXi a real virtualization solution since it's just using a heavily modified linux kernel.  Seem like a fair statement?  It's equivalent to your statement.

ESXi still needs patching.  Whether you patch or not is another story.  Rebuild takes 20 minutes.  Less if you build an image.  And why wouldn't you be using Replica and/or a cluster?
Hyper-V is certainly ready for production especially on server 2012.
You can run it on server core and you will have very few patches (there is not much in server core to patch) and you have an extremely robust and cheap solution.
Your points are valid, but both Microsoft Hyper-V and VMware vSphere (ESXi) are very good production hypervisors.

ESXi does have a very small foot print (less than 1GB), installation time is very quick, it can be installed on a USB flash drive or SD card for embedded use on a server.

Both need to be patched, and we do see more monthly "Windows" patches than we do ESXi patches. Maybe this is because "Windows" is more of a target,

ESXi has support for more OS.
I have seen Hyper-V crash a lot in a certain production environment.

The reason was NOT hyper-v but faulty RAM and the client was made aware of this but they were not interested to fix it. They were not happy with saving the money on hypervisor alone.

Hyper-V works well.
Avatar of okamon
okamon

ASKER

I am not talking about server core hyper-v or hyper-v server here.  I meant to install it as a role after I do the full installation of windows 2012. So this is comparable with esxi? and this is still considered as type 1 hypervisor? I don't think rebuild only takes 20 mins... Full server installation takes more than that, I will have to install bunch of windows updates too.
Yes, it's a Type 1 Hypervisor.

But you are correct, if using Server with a GUI, you will need to apply updates.

But a true comparison is without the GUI, and manage it remote like ESXi! (you cannot manage ESXi from the host, Hyper-V does have a benefit there, if you use Server with a GUI)

But you could also argue, that after installing ESXi 5.1 GA Build 799733 , you will need to install updates to make it current!

e.g. apply - ESXi 5.1 Update 1 Build 1065491
SOLUTION
Avatar of Carol Chisholm
Carol Chisholm
Flag of Switzerland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Windows 2012 Datacenter Server Core installation (without a GUI) takes me -  

(8m 24s , and install was completed!)

After getting devices, ready, restart and the login appears

(11m 18s)

(longest time was inserting the serial number!)
ESXi 5.1 Update 1 installation

(7m 2s for installation to be completed.)

After reboot, starting services and devices

(8m 37s complete at login DCUI)
:) not much difference if you are prepared. And really not much time for either. okamon can make a valid choice. There are the cost factors depending on the size of the install and also the learning curve, though Hyper-V is not very complicated.
Avatar of okamon

ASKER

I don't understand why hyper-v running on top of full windows OS is Type 1 Hypervisor...
From what I know Type 1 hypervisor as running directly on the hardware with VM resources provided by the hypervisor. Type 2 hypervisor runs on a host operating system to provide virtualization services. So why it's not considered as Type 2?

Like vmware server, it's installed on windows os and it's Type2.
Its not Hyper-V communicates directly with Bare Metal.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial