Running hyper-v and vmare on same windows install.

Does it work with the Server 2012 R2 or 2016?

Hyper V is corrupting my drives when it shuts down so might try VMWare

I may give it a try. I need to update my old Exchange server and I was thinking of Exchange 2013 as stable but I now find out by trial it does not install under Server 2016 just because the GUI is no longer available in 2016. Would have to go for Ex2016 if I wanted to updated to Server 2016. Sounds very expensive so might give it a miss now. Would still love to find out why Hyper V under 2012 R2 and 2016 is corrupting my drives on the Hypervisor shutdown.

Hi there

This has been posted several times -- OK I agree it's better than having to uninstall / re-install HYPER-V each time - but this actually is one of the (VERY RARE) cases where I WOULD suggest a Dual boot. That way you can keep the HYPER-V system totally separate from the one running VMware. You won't pay extra for software licences you've already installed on Windows.

Note -- the same principles apply to VirtualBox as well as VMware - these products don't run when HYPER-V is enabled (and vice-versa).

Depending on what you need to do on the HYPER-V system you could make that a minimal windows install if most of your main work is done on the other system - or even on the VM's.

I'm actually running 2 concurrent Windows VM's with HYPER-V running on both of them -- with a decent processor and fast (Hardware RAID 0) HDD setup the performance of the 2nd level VM is fine !!!!!! (Host --Linux CENTOS 7-->VM Windows 10 Pro X-64, running HYPER-V---Windows 7 VM

2nd VM also Windows 10 PRO X64 running HYPER-V with XP as the VM.

TIP though --for people encouraged to try this sort of stuff out (2nd level VM's --i.e a VM running on a VM) you need to ensure :

1) Host is as efficient as possible -- Windows 10 is not really suitable for this since it's essentially designed as a Non server single user system -but it CAN be done.

2) You need PLENTY of RAM -- at least 16 GB - better 32 or even 64 GB RAM.

3) decent processor -- ideally something like dual Xeon - or anything with HYPER THREADING --although the average i7's will work.

4) Above all FAST HDD's -- about 85% of the bad performance I've seen with most people's computers is usually the appalling SLOW consumer grade HDD's they have in them -- FAST HDD's with a decent size cache and of course some type of hardware RAID.

5) The HOST OS should ideally run headless and act simply as the server - but provided you aren't doing too much work on it then you can of course have a GUI etc. Put the HOST OS on an SSD if at all possible.

Cheers
jimbo