Host System Or No Host System, That Is The Question
hi,
i starting first foray vms, , have basic question right off bat....
should install host system first, hypervisor, or install hypervisor directly without host?
to mind, given resource consumption of vms, strikes me not having underlying resource hog (e.g. os running) surely better.
however have read in places people have found easier share , manage resources on host if there underlying host system.
what pros , cons of 2 approaches?
regards,
rob.
okay - let me see if can clear terminology here.
"hosted" virtualization engine - these virtual server, vmware server, virtualbox
there functional, not limited in way, operating system engine runs on top application.
there benefits , drawbacks - 1 raw vm performance, less here.
"hypervisor" - these esx, hyper-v, xenserver, oraclevm (or whatever callig now), sun hypervisor
these thin hypervisor layer sits on top of hardware , have 'parent' partition manages vms , provides additional services vms.
where gets muddy server 2008 hyper-v role - iti s technically hypervisor, parent parittion looks full operating system. however, parent partition functions full os - no longer has full access hardware (that hypervisor in-between).
this gives local gui configuration environment - easier complex configurations - don't think can have expereince if use regular windows server.
in mind depends on need, , why.
if talking production - use hypervisor. there independant tests speak raw power of each.
if talking test , demo - use fits , interface of.
brian ehlert (hopefully have found useful)
"hosted" virtualization engine - these virtual server, vmware server, virtualbox
there functional, not limited in way, operating system engine runs on top application.
there benefits , drawbacks - 1 raw vm performance, less here.
"hypervisor" - these esx, hyper-v, xenserver, oraclevm (or whatever callig now), sun hypervisor
these thin hypervisor layer sits on top of hardware , have 'parent' partition manages vms , provides additional services vms.
where gets muddy server 2008 hyper-v role - iti s technically hypervisor, parent parittion looks full operating system. however, parent partition functions full os - no longer has full access hardware (that hypervisor in-between).
this gives local gui configuration environment - easier complex configurations - don't think can have expereince if use regular windows server.
in mind depends on need, , why.
if talking production - use hypervisor. there independant tests speak raw power of each.
if talking test , demo - use fits , interface of.
brian ehlert (hopefully have found useful)
Windows Server > Hyper-V
Comments
Post a Comment