Enable Virtualization Technology (VT) in BIOS – Updated


Virtualization Technology in BIOS

This post explains how to enable Virtualization Technology (VT) in motherboard BIOS. To run some operating systems, virtualization software and virtual machines hardware virtualization should be enabled. Mostly, operating systems which not required virtualization technology run normally when virtualization technology is enabled, but for the operating systems required this technology, it must be enabled.
All latest processors and motherboards support virtualization technology, check your motherboard vendor about this support and how to enable or disable VT in BIOS.  Operating system detects the hardware virtualization technology once it’s enabled on your motherboard.


Where to Find Virtualization Technology (VT) in BIOS?

This setting is found under ‘Advanced Chipset settings’ in AWARD BIOS. It will be different for each motherboard. Check your mother board manual.

http://www.sysprobs.com/wp-content/uploads/2009/10/virt_bios.gif


After you change the settings to disable or enable, it’s recommended to shutdown the computer for minimum 10 seconds and restart the machine (Cold Restart) to take effects. If your motherboard is latest one, it detects this change doe’s cold restart. Whenever I change this VT setting on my motherboard, it delays the next restart automatically.


How to Confirm Virtualization Technology is Enabled or Disabled?

1) If your processor is Intel, then you can use this free utility to confirm the result which operating system is sensing.
Download Intel tool to confirm virtualization technology
The result of this utility brings a screen as shown below,
Enable Virtualization Technology (VT)
2) For AMD Processors download the below utility.
3) Microsoft Tool to check hardware virtualization Technology ( VT)
Download the free tool from Microsoft here.
Installation not required, when execute the EXE file, following result appears.
Enable Virtualization Technology (VT)
The above result shown is other computer which is not having hardware enabled.


Comments

Post a Comment

Popular posts from this blog

Enterprise CA option is greyed out / unavailable

Many times, when installing Active Directory Certificate Services they cannot choose to install Enterprise Certification Authority, because it’s unavailable as in following picture: Well, you need to fulfill basic requirements: Server machine has to be a member server (domain joined). You can run an Enterprise CA on the Standard, Enterprise, or Data Center Windows Edition. The difference is the number of ADCS features and components that can be enabled. To get full functionality, you need to run on Enterprise or Data Center Windows Server 2008 /12/R2/ Editions.  In order to install an Enterprise CA, you must be a member of either Enterprise Admins or Domain Admins in the forest root domain (either directly or through a group nesting). If issue still persists, there is probably a problem with getting correct credentials of your account. There are many thing that can cause it (network blockage, domain settings, server configuration, and other issues). In al...
Read more

Rearm the Office 2013 installation

Image
There is a 25-day grace period from the time of installation of Key Management Service (KMS) clients before notifications to activate are displayed to the user. If you want to deploy an image, you must rearm your Office 2013 installation before you capture the image. If you do not rearm, users see notification dialog boxes at the time that the image is deployed, instead of 25 days after deployment. The 25-day grace period gives ample time for a KMS host to be found and activation to succeed. If activation is successful, users do not see notifications to activate. Rearm the Office installation Rearming does the following important tasks: Resets the grace timer to 30 days. Freezes the grace timer until either an Office application is run, or the ospp.vbs script is run. Resets the client computer ID (CMID). This is important because the KMS host uses the CMID to determine the num...
Read more

MP has rejected registration request due to failure in client certificate

Image
Issue:- We have System Center Configuration Manager 2012 R2 deployed on Windows Server 2008R2 host. Recently we have moved our Certification Authority to Windows Server 2012 , renewed Root CA Certificate and intermediate Certificates also migrated Hashing algorithm from 'sha1' to 'sha2'  . New Root CA and intermediate CA also present on client machines and on SCCM. However, i have discovered these errors on MP: MP has rejected registration request due to failure in client certificate (Subject Name: ) chain validation. If this is a valid client ,  Even though Newly imaged machines are getting SCCM client installed but won't see all the client cycle under 'Actions tab' and also  'client certificate shows "None".  The operating system reported error 2148204809: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.  Solution:- Register  new Certificate of Root CA    under SCCM20...
Read more