casdirty.blogg.se

You can even deploy a few VM's in HyperV with adequate performance.

Iscsi for storage and you have got a 2 (or more) node cluster for testing. You deploy two Virtual Machines, install HyperV and the necessary roles (like Failover Clustering, MPIO etc), add a few virtual Nic's, configure teaming, maybe use

Our company is using mainly HyperV and i wanted to be able to experiment at home without spending to much money.īuilding a cluster in VMWare Workstion is not much different from using physical blades. My main reason for using VMWare Workstation was to experiment with MS Failover clustering. That means you will lose performance on your host OS as it's resources are subject to the same sharing that other Hyper-V VM's on your box will have to handle so overall performance will be down. Just bear in mind that when you install Hyper-V it places the visualization layer beneath the host OS not on top like VM Workstation does, Visualization products like VM Workstation enable us to create labs we could only dream about 10 years ago in our home environments, when it comes to testing visualization products however, I found you still need physical boxes.Īlternatively is you are running certain versions of Windows 8, they come with Hyper-V already and just need enabling. I got mine populated with 16GB of memory for around £320 UK pounds. I would look at getting a cheap second machine, like one of the HP micro servers. I found that I could not run Hyper-V within a VM Workstation environment.

It's unsupported and totally pointless as it give you no advantages.

No company uses nested hypervisors in this way in production. My requirement is to simply use Hyper-V to create VMs to start labbing. I think it is sort of nested VMs but not sure if companies practice it in production. Installing Hyper-V inside a VM then creating VMs in Hyper-V (which is inside a VM already) is confusing and doesn't reflect real environments.