Ok so i had 64 bit working with a distro of centos 7 (64 bit of course) last night. I closed it down, shut down my pc and today when i booted up my machine, virtualbox doesn't recognize my machine as 64bit anymore. I removed and reinstalled vbox to see if that was the issue, it isnt. im running avast with hardware assisted virtualization enabled. virtualization is still enabled in my motherboard settings. hyper-v is also not installed. I have run out of ideas as to what could be causing this..any help would be appreciated.
my system:
windows 7 pro
i7 4790k
asus z97 sabertooth board
nvidia gtx980ti
32 gb ram
***EDIT: i also booted into safemode and it detects it just fine
Virtualbox not recognizing 64bit anymore.
-
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: Virtualbox not recognizing 64bit anymore.
That's your problem. See: viewtopic.php?f=6&t=76191dark_controller wrote:im running avast with hardware assisted virtualization enabled.
Does that mean that it worked? Maybe Avast drivers didn't load in safe mode?dark_controller wrote:i also booted into safemode and it detects it just fine
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: Virtualbox not recognizing 64bit anymore.
I'm quite certain that is the case. But, at least that does serve to prove that the BIOS feature is enabled, and it is something in the host OS (i.e. Avast) which is grabbing VT-x.socratis wrote:Maybe Avast drivers didn't load in safe mode?