What Is Hardware Virtualization? VT-x and AMD-V Explained

Most people meet hardware virtualization the same way: an Android emulator, Docker Desktop, or WSL 2 refuses to start and throws an error mentioning VT-x, AMD-V, or "virtualization is not enabled". This page explains what the feature actually is, how to check whether you have it, what depends on it, and what your options are if you don't.

Verified against Intel, AMD, Microsoft, Google and Riot documentation as of August 2026.

What is hardware virtualization?

Hardware virtualization is CPU support for running one operating system inside another without pretending.

Start with the problem it solves. An operating system expects to own the machine. It expects to control the memory map, install interrupt handlers, and execute privileged instructions. If you want to run Android, Linux, or a second copy of Windows inside your current OS, something has to convince that guest OS it is in charge when it isn't.

There are three ways to do that, and they are not equally fast:

• Emulation. Software reads each guest instruction and reproduces its effect. Maximum compatibility — you can emulate an ARM phone on an x86 laptop this way — and dramatically slow, often 10× or worse.
• Binary translation / paravirtualization. The hypervisor rewrites dangerous instructions on the fly, or the guest kernel is modified to cooperate and call the hypervisor deliberately. Much faster than emulation, but complex and, in the paravirtual case, requires a patched guest.
• Hardware-assisted virtualization. The CPU itself gains a new operating mode. Guest code executes natively on the silicon at full speed, and the processor automatically traps out to the hypervisor only when the guest does something that needs supervision.

That third option is what VT-x and AMD-V provide. Intel's model splits execution into VMX root operation (where the hypervisor runs) and VMX non-root operation (where the guest runs). Moving between them is a VM exit and a VM entry. Because the hypervisor sits at a privilege level effectively beneath the guest kernel's ring 0, people informally call it "ring −1". That phrase is shorthand, not an architectural term — but it captures the idea accurately.

The practical consequence: with hardware virtualization on, a virtual machine runs at close to native speed. With it off, a hypervisor either refuses to start or falls back to software emulation that is slow enough to be unusable for an Android emulator or a container runtime.

What are Intel VT-x and AMD-V?

They are the same idea implemented independently by the two x86 vendors. Intel shipped VT-x in 2005 (project codename Vanderpool); AMD shipped AMD-V in 2006 (codename Pacifica). They are not compatible at the instruction level — a hypervisor must implement both — but from a user's point of view they do the same job.

The confusing part is the naming. Every vendor uses a different label in BIOS, and the CPU feature set has grown several extensions since 2006. This table maps what you see to what it means:

The short version for most readers: you need VT-x or AMD-V. You almost certainly do not need VT-d. Modern CPUs that have the first also have SLAT (EPT or RVI), so if your processor supports virtualization at all, it supports the parts emulators and containers need.

How do I check if my PC has virtualization enabled?

There are two separate questions — does the CPU support it, and is it turned on in firmware — and the good tools answer both.

Windows

Fastest check: open Task Manager (Ctrl+Shift+Esc) → Performance → CPU. On the right there's a Virtualization row reading Enabled or Disabled.

More detailed check, in Command Prompt:

systeminfo

Scroll to the Hyper-V Requirements block at the bottom and read the two lines that matter:

In PowerShell, the same facts come back as typed properties:

Get-ComputerInfo -Property "HyperV*"

Microsoft documents HyperVRequirementVirtualizationFirmwareEnabled as returning False specifically when virtualization is not enabled in the BIOS, and HyperVRequirementVMMonitorModeExtensions as the CPU-capability flag. A $null for both usually means a hypervisor is already running.

macOS

Macs have no virtualization toggle — it is on permanently at the firmware level, on both Intel and Apple Silicon. To confirm the hypervisor interface is available:

sysctl kern.hv_support

kern.hv_support: 1 means Apple's Hypervisor framework is usable — this is the check that matters, and it works on Apple Silicon too. On Intel Macs you can additionally look for the raw CPU flag:

sysctl -a | grep machdep.cpu.features

Look for VMX in the feature list. Note that the flag being present does not by itself mean macOS will let you use it — kern.hv_support is the authoritative answer.

Linux

# Human-readable: prints "VT-x" on Intel, "AMD-V" on AMD
lscpu | grep -i virtualization

# Raw flag count: 0 means no support (or disabled in firmware)
grep -Ec '(vmx|svm)' /proc/cpuinfo

# The definitive KVM readiness check (Debian/Ubuntu: apt install cpu-checker)
sudo kvm-ok

kvm-ok is the most useful of the three because it distinguishes the two failure modes explicitly: it will tell you whether KVM acceleration can be used, or whether the extensions exist but are disabled in your BIOS.

What software actually needs hardware virtualization?

More than most people expect — including parts of Windows itself.

If you're here because an Android emulator failed to start, the Android emulators complete guide covers which engines tolerate which configurations.

Why is hardware virtualization disabled by default?

Two honest reasons, one historical and one bureaucratic.

The security history. In August 2006, security researcher Joanna Rutkowska demonstrated Blue Pill at Black Hat — a proof-of-concept rootkit that used AMD-V (and was later ported to VT-x) to slide a thin malicious hypervisor underneath a running operating system. The OS keeps running normally, unaware it has been demoted to a guest. That demonstration landed a year after VT-x shipped and made OEMs cautious about leaving a brand-new, poorly-understood privilege level switched on for users who would never knowingly use it. In practice, modern Secure Boot, TPM measurement and hypervisor-launch protections make that specific attack far harder — but the default stuck.

The bureaucratic reason. BIOS defaults are conservative and rarely revisited. Enterprise fleets are the other factor: some corporate images and vPro management policies deliberately lock virtualization off so employees can't spin up unmanaged VMs. If your work laptop shows the toggle greyed out, that's usually policy, not hardware.

The direction of travel has now reversed. Windows 11 enables virtualization-based security by default on qualifying hardware, and — as covered below — at least one major anti-cheat now requires it.

What if my CPU or BIOS doesn't support virtualization?

Be clear-eyed here, because this is where bad advice lives.

Hardware virtualization is a silicon feature. VT-x and AMD-V are physical CPU capabilities. No software, patch, driver, registry tweak or downloadable "VT enabler" can add them to a processor that lacks them. Anything advertising that it can is at best useless and at worst malware. There is no exception to this.

What you genuinely can do, in order of preference:

1. Confirm it's really unsupported. Far more often the CPU supports it and the toggle is simply off or hidden. Update your BIOS first — several 6th/7th-gen Intel laptops shipped without the option and gained it in a later firmware release. Some Acer and older Toshiba models hide the toggle until a Supervisor Password is set.
2. Ask IT if it's a managed device. A greyed-out toggle on a corporate laptop is a policy lock. Citing WSL 2, Docker or test automation as the use case usually works.
3. Use software that doesn't require it. Several Android emulators ship no-VT engines that fall back to software rendering — slower, but functional. We maintain a working list in how to run an Android emulator without virtualization and a ranked comparison in the best emulators without VT.
4. Move the workload off the machine. A cloud VM, a remote dev container, or a device farm sidesteps the problem entirely and is usually the right answer for CI and test work.

Does hardware virtualization slow down my PC or affect gaming?

This question gets a bad answer everywhere, so here is the precise one.

Enabling VT-x or AMD-V in BIOS costs nothing on its own. The extensions are dormant instructions. Until a hypervisor executes VMXON (or the AMD equivalent), the CPU behaves exactly as before. There is no measurable penalty for leaving the toggle on.

What people actually measure is virtualization-based security. When Windows turns on VBS and memory integrity (HVCI), the Windows hypervisor starts and the OS you use becomes a guest. That is real overhead, and it lands hardest on CPU-bound and memory-latency-sensitive workloads — which is exactly what games are. Microsoft is explicit about the mechanism: memory integrity "works better with Intel Kabylake and higher processors with Mode-Based Execution Control, and AMD Zen 2 and higher processors with Guest Mode Execute Trap"; older CPUs "rely on an emulation of these features, called Restricted User Mode, and will have a bigger impact on performance." So the size of the hit depends heavily on your CPU generation.

If you are chasing frames, the lever is memory integrity (Windows Security → Device security → Core isolation), not the BIOS virtualization toggle. Turning off memory integrity while leaving VT-x enabled gets you the frame rate back and keeps your emulators and containers working.

Anti-cheat is the wrinkle, and it has flipped. Kernel anti-cheat historically treated virtualization as hostile: Riot's Vanguard blocks Valorant inside VMware, Hyper-V and VirtualBox by design, since a VM can hide cheat tooling. But on 24 June 2026, Riot shipped Vanguard On-Demand, which loads the anti-cheat driver only while a Riot game is running instead of at every boot — and it requires Windows 11 25H2 with UEFI mode, Secure Boot, TPM 2.0, VBS, HVCI and IOMMU all enabled simultaneously. Riot said roughly 35% of players met every requirement at launch. The old advice to "turn virtualization off for gaming" is now actively wrong for at least one very large title.

How do I enable hardware virtualization?

In outline: reboot into UEFI firmware settings, find the toggle under CPU Configuration (Intel: Intel Virtualization Technology; AMD: SVM Mode), enable it, save with F10, and boot back into Windows.

The details differ per manufacturer, and the failure modes — missing option, greyed-out option, change not applying until a cold boot, Hyper-V then claiming the feature and breaking your emulator — are where people get stuck. Rather than duplicate it here, use the step-by-step guide: How to enable Intel VT-x or AMD-V in BIOS on Windows 10/11. It has the exact BIOS path for ASUS, Dell, HP, Lenovo, MSI, Acer, Gigabyte and ASRock, plus the checklist for when the toggle isn't there.

So what should you actually do?

A decision rule, in three lines:

• If you develop, test, or run containers: enable VT-x / AMD-V and leave it on permanently. It costs nothing idle and every relevant tool needs it.
• If you game and chase frame rates: still leave VT-x on. Turn off memory integrity instead — unless you play a Riot title on Windows 11 25H2, where VBS and HVCI are now a requirement rather than a tax.
• If your CPU genuinely lacks it: stop looking for a software fix, because there isn't one. Switch to a no-VT emulator or move the workload to a machine or cloud instance that has the feature.

FAQ

What is hardware virtualization?

Hardware virtualization is a set of CPU extensions that let a hypervisor run a guest operating system's code directly on the physical processor, instead of emulating it in software. The CPU gains a separate execution mode for guests and automatically traps out to the hypervisor for sensitive operations. Intel's implementation is VT-x; AMD's is AMD-V.

What is Intel VT-x?

Intel VT-x is Intel's hardware virtualization feature set, technically called VMX (Virtual Machine Extensions), introduced in 2005. In BIOS it usually appears as "Intel Virtualization Technology" or "VTx". It adds VMX root and non-root operating modes so guest code executes natively. Modern VT-x also includes Extended Page Tables (EPT) for hardware-assisted memory translation.

What is AMD-V?

AMD-V is AMD's equivalent of Intel VT-x, technically called SVM (Secure Virtual Machine), introduced in 2006. Most AMD motherboards label the BIOS toggle "SVM Mode" rather than "AMD-V", which is why people often can't find it. AMD's nested-paging equivalent of Intel EPT is called Rapid Virtualization Indexing (RVI), formerly Nested Page Tables.

How do I know if virtualization is enabled on my computer?

On Windows, open Task Manager → Performance → CPU and read the "Virtualization" row, or run systeminfo and check the Hyper-V Requirements block. On macOS run sysctl kern.hv_support — a value of 1 means yes. On Linux run lscpu | grep -i virtualization or sudo kvm-ok, which also tells you whether it's disabled in firmware.

Is it safe to enable hardware virtualization?

Yes. It is a CPU capability, not a security setting, and most business laptops ship with it already on. The historical concern was hypervisor rootkits like Blue Pill (2006), which Secure Boot and modern hypervisor-launch protections largely address. Enabling it also lets Windows security features like memory integrity and Credential Guard run.

Does virtualization affect gaming performance?

Enabling VT-x or AMD-V in BIOS has no performance cost by itself — the instructions are dormant until a hypervisor uses them. What people measure is virtualization-based security (VBS) and memory integrity, which put Windows itself under a hypervisor. That overhead is real, and worse on pre-Kaby Lake Intel and pre-Zen 2 AMD CPUs that lack MBEC/GMET.

What's the difference between VT-x and VT-d?

VT-x virtualizes the CPU — it lets guest instructions run natively under a hypervisor. VT-d virtualizes I/O via an IOMMU, providing DMA and interrupt remapping so a virtual machine can safely own a physical PCIe device such as a GPU or network card. Android emulators, Docker and WSL 2 need VT-x only; VT-d is for passthrough setups.

Can I add virtualization support to a CPU that doesn't have it?

No. VT-x and AMD-V are physical silicon features. No driver, patch, registry edit or downloadable tool can add them to a processor that lacks them, and software claiming otherwise should be treated as malicious. Your real options are a BIOS update (in case the toggle is merely hidden), a no-VT emulator, or different hardware.

Why does Windows say virtualization is enabled but my emulator still fails?

Usually because Hyper-V has already claimed it. Once Hyper-V, WSL 2, Windows Sandbox or memory integrity is running, the Windows hypervisor owns VT-x and third-party hypervisors must go through Windows Hypervisor Platform instead. Either use a Hyper-V-aware emulator build, or disable the Hyper-V and Virtual Machine Platform Windows features and reboot.