So, I'm having this issue with VMware Workstation when I'm running the New Virtual Machine Wizard and on the Guest operating system option it will show 64-bit guest operating systems are not supported by this host and will not run. So what I did first thing is to make sure that Virtualization Technology is turned on in the BIOS setting and it is then power cycle the server boot to OS still no luck so I went back to BIOS roam around the BIOS setting flipping settings on/ off that may have something to do with VT and still no luck, I then roam around on different forums and still didn't found a solution for my issue then I thought what if I turn off the Virtualization Technology.... after doing that the 64-bit guest operating systems are not supported by this host and will not run doesn't show up anymore! so at this point I'm not sure which one should I follow, my BIOS setting or VMware Workstation. Please help, any input would be greatly appreciated.
System Spec
Dell R730
Dual Intel Xeon E5-2630 v3 2.4Ghz
64GB RAM
I want to run a nested VM and create a lab for ESXi
Hi,
Please note that power cycle might not have been enough to actually change the setting on VT.
You need to actually unplug the power sometimes.
VT should be set to on.
Please see this document for more details:
Trouble-shooting Intel VT-x Issues
Your hardware should run 64 bits guests just fine.
--
Wil
Thanks for the reply will, I'll give that a try and see what happens, it's just super odd that when I turn it off VMworkstation 64bit will start to work and if I turn it off 64bit guest OS will not work.
Please post your vmware.log files for the two configurations (as attachments).
I my case, I had Hyper-V enabled. After removing Hyper-V role the vmware workstation did not show that warning.
Hi, were you able to solve the problem ? It suddenly happened the same to me. I already checked Hyper-V not installed. Also set "hypervisorlaunchtype Off". Already checked virtualization in BIOS is ON. Don't know more what to do. Thanks
I was able to get around this issue by deleting all VMs and removing the host-server from Hyper-V then disabling Hyper-V under Windows Features. After restarting my PC, all was good.