Hot answers tagged

30

What solved my issue was using less than 3 GB of ram in the virtual box session. I was originally attempting to utilize roughly 6 GB. You are trying to allocate >3GB of RAM to the VM. This requires: (a) a 64 bit host system; and (b) true hardware pass-through ie VT-x.


6

You don't have to uninstall/reinstall HyperV I ran into this same issue using the new Visual Studio 2015 Android emulator and Windows Phone emulator, while also trying to run VirtualBox clients. Unfortunately you can't run VBox at the same time as the other emulators; you just have to setup a new boot option and reboot to switch back and forth. Open an ...


2

This is not a duplicated question. What OP is trying to do is something like this: Host A(with VT-X support)->virtual machine B-->some applications need VT-X and getting VT-X support inside B so applications -- may be another VM or emulator -- running inside B, can take advantage of vt-x. Its called "Nested Hardware Virtualization", supported by ...


2

To use Hyper-V you have to upgarde to at least Windows 10 Pro. The Home Edition doesn't support it.


2

Reducing RAM in VirtualBox from 4gb to 2gb worked for us when we had only RDP to host machine so couldn't access BIOS.


1

I think you copied the two commands from a blog that automatically turned a "-" character (U+002D HYPHEN-MINUS) into a "–" character (U+2013 EN DASH). You must use "-" rather than "–". Here are the corrected commands: VBoxManage modifyvm <VM_NAME> --hwvirtex off VBoxManage modifyvm <VM_NAME> --vtxvpid off


1

Hyper-V is only supported on the Pro and Enterprise editions. The following prerequisites are required to successfully run Client Hyper-V on Windows 10: Windows 10 Pro or Enterprise 64 bit Operating System 64 bit processor with Second Level Address Translation (SLAT) 4GB system RAM at minimum BIOS-level Hardware Virtualization support ...


1

There's nothing surprising about this. Windows 10 is using the virtualization feature of the CPU, as it says it is. CPU-Z is therefore running on a virtual CPU which does not itself support virtualization. Before, your OS wasn't using the virtualization feature of the CPU. So that left it available for programs like CPU-Z to detect and use. Unless nested ...


1

Just ran this on my box at home and I can confirm the latest version of CPU-Z directly from the website works correctly on Windows 10. It detected that my CPU supported VT-x and listed it in the instructions section. Without checking if you have VT-x enabled in the BIOS, everything is probably just guessing.


1

Actually sometimes vendors of motherboards (mostly notebook ones - a 2430M seems to be a notebook processor, so I can assume that you have a notebook) lock this option - hide it from the BIOS menu. There could be three ways to enable it - first one there MAY be an utility from the notebook or motherboard vendor which could enable or disable it. Second one - ...


1

Open Avast, go to -> Settings -> Troubleshooting -> "Enable hardware-assisted virtualization", and uncheck Avast's "Enable hardware-assisted virtualization". Source: https://forum.avast.com/index.php?topic=162445.0


1

I had the same issue with an i7-4790 CPU and an ASRock Z97 Extreme6 motherboard. My BIOS reported that VT-x was enabled, however the Intel Processor Identification Utility showed that it was disabled. Turned out to be the Hypervisor conflicting with the Intel tool. Using bcdedit to prevent the hypervisor from automatically starting allowed the Intel tool to ...


1

I had a similar issue. VT-x features locked or unavailable in MSR. VERR_VMX_MSR_LOCKED_OR_DISABLED. I run the VMBox for years and not this... I checked all the Forums and nothing helped me, than I realised there was an update of my antivirus software. So problem came from the new AVAST antivirus software. In AVAST Options-> Troubleshooting->Disable Hardware ...



Only top voted, non community-wiki answers of a minimum length are eligible