Hi All
I have a PC, based on Core i7 5930K and ASUS X99-E WS. Some time ago I had various different virtual machine softwares installed and everything worked fine on windows 7 x64 and Kubuntu x64. However I reinstalled and now I run windows 10 x64. I didn't need virtual machines for some time...
I decided to try Hyper V and noticed it only allows me to install 32 bit guest systems. I thought the fault was in hyper V. Then I installed VMware - the same thing?! I thought they cut that functionality from the free version :O. But when I installed virtual box, and it too restricted me to 32 bit guest OSes only, I realized somethings wrong with my PC.
I googled the problem and it turned out I have to enable the virtualization technology in the bios. What's called VT-x, (EPT) or just "Virtualization technology" as that setting is called in my bios.
I don't remember ever disabling it and when I checked in the bios, sure enough it WAS enabled?!
I know my CPU supports this feature but I checked anyway, and yes the intel's datasheed on my processor showed that it does support it.
I have an up-to-date version of AIDA64 so I went to the CPUID section to check there. To my surprise AIDA64 said my processor does not support EPT. In fact, of like ten virtualization related features AIDA says my CPU only supports "Hypervisor"?!
Encrypted State (SEV-ES) --- Not Supported
Extended Page Table (EPT) --- Not Supported
Hypervisor --- Present
INVEPT Instruction --- Not Supported
INVVPID Instruction --- Not Supported
Nested Paging (NPT, RVI) --- Not Supported
Secure Encrypted Virtualization (SEV) --- Not Supported
Secure Virtual Machine (SVM, Pacifica) --- Not Supported
Virtual Machine Extensions (VMX, Vanderpool) --- Not Supported
Virtual Processor ID (VPID) --- Not Supported
Not just disabled! Not supported?!
And the datasheed says:
Intel® Virtualization Technology (VT-x) = Yes
Intel® Virtualization Technology for Directed I/O (VT-d) = Yes
Intel® VT-x with Extended Page Tables (EPT) = Yes
What's going on? The only major thing I've done is a bios update and my PC works fine after that.
Before the update that setting was called: "Enable VT-x/VT-d" and now it's aclled: "Virtualization Technology". That's the only visible difference and it shouldn't mater, should it?
Also, Hyper V is uninstalled.
OK that's all description I can think of right now, If you need to know something more, feel free to ask me.
Thanks in advance.
P.S. While writing this thread I notices that all those features outlined in the bios have that "‡" sign on them. This is what it means:
‡ This feature may not be available on all computing systems. Please check with the system vendor to determine if your system delivers this feature, or reference the system specifications (motherboard, processor, chipset, power supply, HDD, graphics controller, memory, BIOS, drivers, virtual machine monitor-VMM, platform software, and/or operating system) for feature compatibility. Functionality, performance, and other benefits of this feature may vary depending on system configuration.
But in my case it shouldn't mater since it worked before?!...
I have a PC, based on Core i7 5930K and ASUS X99-E WS. Some time ago I had various different virtual machine softwares installed and everything worked fine on windows 7 x64 and Kubuntu x64. However I reinstalled and now I run windows 10 x64. I didn't need virtual machines for some time...
I decided to try Hyper V and noticed it only allows me to install 32 bit guest systems. I thought the fault was in hyper V. Then I installed VMware - the same thing?! I thought they cut that functionality from the free version :O. But when I installed virtual box, and it too restricted me to 32 bit guest OSes only, I realized somethings wrong with my PC.
I googled the problem and it turned out I have to enable the virtualization technology in the bios. What's called VT-x, (EPT) or just "Virtualization technology" as that setting is called in my bios.
I don't remember ever disabling it and when I checked in the bios, sure enough it WAS enabled?!
I know my CPU supports this feature but I checked anyway, and yes the intel's datasheed on my processor showed that it does support it.
I have an up-to-date version of AIDA64 so I went to the CPUID section to check there. To my surprise AIDA64 said my processor does not support EPT. In fact, of like ten virtualization related features AIDA says my CPU only supports "Hypervisor"?!
Encrypted State (SEV-ES) --- Not Supported
Extended Page Table (EPT) --- Not Supported
Hypervisor --- Present
INVEPT Instruction --- Not Supported
INVVPID Instruction --- Not Supported
Nested Paging (NPT, RVI) --- Not Supported
Secure Encrypted Virtualization (SEV) --- Not Supported
Secure Virtual Machine (SVM, Pacifica) --- Not Supported
Virtual Machine Extensions (VMX, Vanderpool) --- Not Supported
Virtual Processor ID (VPID) --- Not Supported
Not just disabled! Not supported?!
And the datasheed says:
Intel® Virtualization Technology (VT-x) = Yes
Intel® Virtualization Technology for Directed I/O (VT-d) = Yes
Intel® VT-x with Extended Page Tables (EPT) = Yes
What's going on? The only major thing I've done is a bios update and my PC works fine after that.
Before the update that setting was called: "Enable VT-x/VT-d" and now it's aclled: "Virtualization Technology". That's the only visible difference and it shouldn't mater, should it?
Also, Hyper V is uninstalled.
OK that's all description I can think of right now, If you need to know something more, feel free to ask me.
Thanks in advance.
P.S. While writing this thread I notices that all those features outlined in the bios have that "‡" sign on them. This is what it means:
‡ This feature may not be available on all computing systems. Please check with the system vendor to determine if your system delivers this feature, or reference the system specifications (motherboard, processor, chipset, power supply, HDD, graphics controller, memory, BIOS, drivers, virtual machine monitor-VMM, platform software, and/or operating system) for feature compatibility. Functionality, performance, and other benefits of this feature may vary depending on system configuration.
But in my case it shouldn't mater since it worked before?!...