08-22-2014 10:13 AM
I am trying to enable virtualization on a Lenovo Thinkpad T410 laptop at my workplace. I have read elsewhere that I need to initialize Virtualization in my laptop's BIOS (in VMware, I am told I need to "enable Virtualization Technology intel VT-X").
In the BIOS, under Config -> CPU (I have looked in other parts of the BIOS already, but there are no other Virtualization options except in this directory), I see the following options
Intel(R) Virtualization Technology.....Disabled
Intel(R) VT-d Feature........................Disabled
Now, you would think I should simply be able to scroll down to the last two to enable ... that's not the case. I can scroll up and down (with up and down arrows) between Multiprocessing and Hyper-Threading, but not the last two.
I have read this thread: http://forum.thinkpads.com/viewtopic.php?f=45&t=113817&p=731447#p731447
The solution described does not help me as I can't even scroll down to Virtualization to attempt to enable it.
Does anyone know of a solution?
08-25-2014 07:19 AM - edited 08-25-2014 07:56 AM
Is there no one that can help me with my problem? Lenovo Customer Support is a joke, has no idea what they're talking about and refuses to help me because my company can't afford to keep their hardware under warranty.
11-17-2014 02:55 AM
I have the same Problem with a x240. In the Bios the options Virtualization and VT-d Feature are disabled and can not be changed – unfortunately I can not find any support by lenovo.
11-17-2014 07:55 PM
01-09-2015 02:26 PM
I have this identical problem on my T410 with an i5 520M. The processor definitely supports VT-x but the BIOS prevents its selection. The BIOS is at v. 1.28 which is old. Do you know how to fix it mate?
01-09-2015 04:21 PM - edited 01-09-2015 04:43 PM
I'd try to update the BIOS first, and see if the option works. Upgrade with the ISO method (use a USB instead of a CD if you want) to be safe.
01-09-2015 06:22 PM
Thanks mate, I just have one concern, from
It says the bootable iso supports various Windows Oses, but I run Linux (Manjaro 32-bit). I don't see how a BIOS upgrade would be connected to the OS since they're separate systems, but I'm not an expert here and I really don't want to mess anything up. Is everything going to be ok with my Linux system if I just boot from iso to upgrade?
01-09-2015 06:59 PM - edited 01-09-2015 07:00 PM
Yeah I don't know why the ISO is specified as Windows only. ThinkWiki has a few articles on using the ISO without actually having to burn a CD, including one on loading directly with GRUB.
01-10-2015 09:46 PM - edited 01-10-2015 10:06 PM
So I managed to update the BIOS to the newest v. 1.45 using the iso without any difficulty. Unfortunately, everything looks the same as it did before, it again doesn't let me scroll down to select the Virtualization options.
I did some digging through a lot of forums and it seems that the issue is that I'm entering the BIOS setup in "usermode," while to change certain settings I need to be in supervisor mode. I never set a supervisor password or any password for the BIOS before this, and while I bought it used I don't think the previous owner set any passwords either. However, in passwords settings, it does say that a Supervisor password is enabled, and in usermode the only thing I'm able to change is the Hard disk password.
In one forum post, it said that if you enter the first 7 characters of your hard disk password upon entering setup, you'll enter as the supervisor. So, I decided that maybe I should set a hard disk password. When I did, it allowed me to enter two passwords, one user password and another user + master password, so I set two different 9-character passwords and saved/exited.
Upon reboot and entering the setup utility, it now prompts me for one password first, for which the only one that works is my user password (the user+master and first 7 characters of either do not work). It then prompts me for another password, and the only thing that works here is a blank password (I tried everything else and no dice), and it takes me into user mode again
So, my guess here is that I might be missing the supervisor password that would enable me to get into setup as supervisor. Is there any default password or something that I can use to get in?
Thanks a lot for your help
01-13-2015 06:49 PM