Opened 7 years ago
Last modified 7 years ago
#17832 new enhancement
Vt-x is not available. What tool will identify the problem?
Reported by: | superdml | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 5.2.12 |
Keywords: | Vt-x not available | Cc: | |
Guest type: | other | Host type: | Windows |
Description
Failed to open a session for the virtual machine GreyCampus Big Data and Hadoop Developer Virtual Machine.
VT-x is not available (VERR_VMX_NO_VMX).
Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
I am trying to complete an online course in Hadoop that has a Virtualbox VM as part of the course. My computer is a Dell XPS 15 (2017) and it has run VirtualBox VMs before. The Bios has this turned on and Hyper-V in the Windows 10 OS is turned off. I also have Visual Studio 2017 installed but have gone in and uninstalled any features in it I can find that might use this. Perhaps there still is something, but it is like finding a needle in a haystack. There should be a tool or a log description can point a finger at precisely what has captured the virtualization so I can fix this.
Attachments (2)
Change History (4)
by , 7 years ago
Attachment: | VBoxHardening.log added |
---|
by , 7 years ago
comment:1 by , 7 years ago
Replying to superdml:
Perhaps there still is something, but it is like finding a needle in a haystack. There should be a tool or a log description can point a finger at precisely what has captured the virtualization so I can fix this.
Good luck finding such a tool!!! Or (if you feel like it) write and provide such a tool.
And if you're the one that's trying to find a needle, imagine us, that we're not sitting in front of your computer and can't possibly know what you have or haven't done to your system!
It's usually better and faster, if issues get first addressed in the VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is not a bug and someone from the developers has to deal with it and close it as "Invalid".
Please read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues for some generic guidelines/ideas. Those are guidelines, you have to use your judgement, but I'd start with MalwareBytes...
If you still have a problem after reading through the whole thing, please head to the forums, and open a new thread. That's where the disussions are taking place, not in the bug tracker!
Please be sure to mention that you came from the bug tracker and include the ticket number.
comment:2 by , 7 years ago
Certain security software might also make use of VT-x for behavioral analysis of potential malware.
ignore Vbox.2.log and Vbox.3.log (duplicates)