I've long been running virtualbox with no problem. Had a few 64 Bit windows VMs and it was going great. Then one day after a few days of not using them, they all show up as 32 Bit and I am no longer able to select 64 bit when creating VMs. I can't start the VMs of course, as they have 64 bit windows installed. The CPU acceleration tab is greyed out and no way to select it.
I could say, oh well the system doesn't support it. But it does, as I've been running with these VMs with no problem. There's no bios option to change, so it is not there either and there has never been a bios update for my system, so it is not that either.
The system is a clevo laptop P370EM3 and the CPU is an i7-3720QM (which supports intel virtualisation)
So how do I fix this?
64 bit and intel virtuel settings gone
-
socratis
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: 64 bit and intel virtuel settings gone
Did you enable Hyper-V in your host? Or installed some other program(s) that may get an exclusive hold of the host's VT-x capabilities?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: 64 bit and intel virtuel settings gone
The host is Windows 8.1, so likely something has taken over VT-x, though is there any way to see what has? Does the virtualbox logs tell you this?
mpack: Yes, I've read the minimum requirements, but most of it doesn't apply to the situation at all, so there wouldn't be a point in including it. Other than I forgot to mention what OS the host was running.
mpack: Yes, I've read the minimum requirements, but most of it doesn't apply to the situation at all, so there wouldn't be a point in including it. Other than I forgot to mention what OS the host was running.
-
socratis
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: 64 bit and intel virtuel settings gone
You can check if Hyper-V is enabled by going to: Control Panel, Programs and Features, Turn Windows features on or off, Hyper-V. I don't know how to check for other programs or actually which programs. I've heard that Window Phone Emulator also does that, as well as some antivirus programs.
You said you can't start the VM. What's the exact error message? And yes, the logs will tell us whether or not VT-x is available.
You said you can't start the VM. What's the exact error message? And yes, the logs will tell us whether or not VT-x is available.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: 64 bit and intel virtuel settings gone
All the log will show is that VT-x locked. No way to know who locked it. For the moment, the VT-x resource is not managed the host OS, so there's no API to query.
Any log will give us many useful details about host and guest which would otherwise have to come from Q&A with you, and take considerably longer, and most likely be wrong.
Any log will give us many useful details about host and guest which would otherwise have to come from Q&A with you, and take considerably longer, and most likely be wrong.