Opened 14 years ago
Closed 14 years ago
#8068 closed defect (worksforme)
Win2008x64 on Win7x86 - No go, my friend.
Reported by: | PMC | Owned by: | |
---|---|---|---|
Component: | VMM | Version: | VirtualBox 4.0.0 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Windows |
Description
Hello -
It would be of immense help if someone could help me understand why I cannot even fire up a win2008x64 VM in my Win7x86 host...
I've turned on the VT-x, I've installed the extensions (assuming that's possible before an OS is in there), etc...
But I get the VERR_VMX_MSR_LOCKED_OR_DISABLED error, with the following below:
Result Code: E_FAIL (0x80004005) Component: Console Interface: IConsole {515e8e8d-f932-4d8e-9f32-79a52aead882}
I'm sure there's an easy explanation here, but I'm just not noticing it...
Change History (7)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
Hey, Frank -
Thanks for the suggestion, but I'm afraid I've already done that. Yeah, went in there right away to confirm I wasn't just imagining it (while hoping I did)... Nope. Really on. Still busted.
Any other possibility?
comment:4 by , 14 years ago
Huh, interesting. So, I don't know what "execute disable" is referring to... but are you saying that the Trusted Execution Platform is the issue here? (I do have it on, I know that.)
Thanks!
comment:5 by , 14 years ago
I say that it depends on the BIOS which settings to choose. Other users did what the blog says and were successful.
comment:6 by , 14 years ago
And I'd say you're on the right track to suggest it - you can close the ticket (Or can I do it too? Noob, first time, blahblahblah) - your hunch proved correct.
Turned off TxT, and off we went!
Now, of course, I've got a billion other issues that have popped up, but I'm slowly working through them. But this one is all set!
Perhaps this should be added somewhere noticeable, so as to help others in positions similar to mine... I know it would have helped me to keep that in mind instead of tearing my hair out. :o)
Thanks, Frank.
That means that VT-x is somehow not accessible on your host. Many BIOSes disable this processor extension by default. Please go to the BIOS settings and check if there is such a setting. Once disabled by the BIOS during boot it cannot be re-enabled anymore later so the BIOS must definitely enable it.