#5605 closed defect (worksforme)
ThinkPad Core 2 Duo - VT-x not recognized
Reported by: | enalposi | Owned by: | |
---|---|---|---|
Component: | guest smp | Version: | VirtualBox 3.1.0 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description
Hello, I have been sent here my the Mod as a follow up to the thread (http://forums.virtualbox.org/viewtopic.php?f=6&t=25243&start=0)
In summary VB doesn't recognize VT-x on my ThinkPad T61p with T7500 processor (supports VT-x: http://ark.intel.com/VTList.aspx) In the end I did a very simple test. I created a new XP client VM.
- Setting 2 client processors: Error - No VT-x
- Switch down to 1 client processor. Starts fine.
I am attaching relevant log and settings files.
Thanks.
Attachments (1)
Change History (6)
by , 15 years ago
comment:1 by , 15 years ago
Looks like I cannot edit the form. Host OS: Windows 7. VT has been enabled in BIOS. I think system config details are all in log and settings files. Thanks.
comment:2 by , 15 years ago
OK, vbox4me2 pointed me at a FAQ and this tip appears to have the issue resolved:
Another hint: after enabling VT-X/AMD-V in the BIOS you might need to switch the PC off completely, unplug it, or remove laptop battery for a minute. Ea: Reboot the Host and go into the BIOS disable vt-x, save BIOS settings, pause machine after bios boot messages power down the Host (unplug power cord!) start the Host and go into the BIOS enable vt-x, save BIOS settings, pause machine after bios boot messages power down the Host (unplug power cord!) Boot the Host.
comment:3 by , 15 years ago
This is a BIOS bug on your host, not a VirtualBox bug. Please use Forum for such problems.
VBox team: Please close it as invalid.
-Technologov
comment:4 by , 15 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Try to find an update for your BIOS. We can't fix BIOS bugs.
comment:5 by , 15 years ago
Thank you for explaining that it is a bios bug after I spent tedious time figuring out that it is a bios issue with help from vbox4me2... ;-)
Maybe could add this to a trouble shooting section in the docs as it doesn't seem to be an isolated thing.
Log and Settings