How to turn on hardware virtualization efficiently

Table of Contents
- Understanding Hardware Virtualization Basics
- Core Concepts of CPU-Level Virtualization
- Hardware Components Required for Virtualization
- Comparison of Virtualization Technologies
- Checking System Compatibility for Hardware Virtualization
- Verifying CPU Support for Virtualization
- Examining BIOS/UEFI Settings for Virtualization
- Common Pitfalls in Compatibility Checks
- Enabling Virtualization in BIOS/UEFI
- Accessing BIOS/UEFI Across Manufacturers
- Locating and Enabling Virtualization Settings
- Configuring the Operating System for Virtualization
- Enabling Nested Virtualization in Linux and Windows
- Installing and Configuring Virtualization Software with Hardware Virtualization
- Kernel-Level Configurations for Virtualization
- Testing and Validating Virtualization Functionality
- System-Level Verification of Virtualization Support
- Benchmarking Virtualization Performance
- Common Validation Errors and Solutions
Hardware virtualization represents a cornerstone of modern computing, enabling seamless execution of multiple operating systems on a single physical machine while optimizing performance and resource allocation. By leveraging CPU-level technologies such as Intel VT-x, AMD-V, and ARM Virtualization Extensions, systems achieve near-native speed for virtual machines, reducing overhead and enhancing scalability. This capability is critical for developers, IT administrators, and enterprises deploying cloud infrastructure, testing environments, or legacy applications. However, enabling virtualization often requires navigating complex BIOS/UEFI settings, verifying hardware compatibility, and configuring operating system parameters—steps that demand precision to avoid pitfalls like disabled flags or firmware limitations.
The process begins with a thorough assessment of system architecture, where identifying supported virtualization extensions and interpreting CPU flags like `vmx` or `svm` sets the foundation. From there, accessing manufacturer-specific BIOS menus and enabling the appropriate settings—whether labeled as "Virtualization Technology" or "AMD-V"—becomes essential. Subsequent steps involve configuring the operating system to recognize and utilize these hardware capabilities, whether through Linux kernel parameters, Windows Hyper-V policies, or virtualization software like VirtualBox. Each phase introduces unique challenges, from troubleshooting "VT-x disabled by BIOS" errors to validating functionality through benchmark tests and VM deployment. Mastering these steps ensures not only the activation of hardware virtualization but also the optimization of its performance for diverse use cases.

Understanding Hardware Virtualization Basics
Hardware virtualization enables the abstraction of physical computing resources—primarily the CPU—to create isolated virtual environments. This technology is foundational to modern cloud computing, server consolidation, and development environments, where multiple operating systems or applications run concurrently on a single physical machine. At the CPU level, virtualization relies on dedicated hardware extensions, such as Intel VT-x, AMD-V, and ARM Virtualization Extensions, which partition resources while maintaining performance and security. These extensions interact with firmware (BIOS/UEFI) and system software (hypervisors) to isolate guest virtual machines (VMs) from the host system, ensuring efficient resource allocation and compatibility.The implementation of hardware virtualization depends on three critical hardware components:
1. CPU Virtualization Support: Modern processors include flags (e.g., `vmx` for Intel VT-x, `svm` for AMD-V) that signal the presence of virtualization extensions.
2. Chipset and Firmware Compatibility: The motherboard’s chipset and BIOS/UEFI must recognize and enable these CPU flags, often through dedicated configuration menus.
3. Hypervisor or Virtualization Software: Tools like VMware ESXi, Microsoft Hyper-V, or KVM rely on these hardware features to create and manage VMs.
The interplay between these components ensures that virtualization operates efficiently. For example, the CPU’s virtualization flags allow the hypervisor to trap sensitive instructions (e.g., context switches, memory management) and redirect them to the host, while the chipset ensures stable communication between the CPU and other hardware. Without firmware support, even a CPU with virtualization extensions may remain unusable for virtualization tasks.
Core Concepts of CPU-Level Virtualization
CPU-level virtualization introduces mechanisms to isolate guest operating systems from the host hardware. Key principles include:Hardware virtualization extensions reduce the need for full-system emulation, which traditionally required significant CPU cycles. Instead, these extensions delegate critical tasks to the CPU, improving performance by up to 90% for compatible workloads (Intel, 2020).The efficiency of these mechanisms depends on the CPU’s architecture. For instance, Intel VT-x and AMD-V share similar goals but differ in implementation details, such as the handling of interrupt remapping or support for nested virtualization. ARM Virtualization Extensions, while newer, prioritize power efficiency and are increasingly adopted in mobile and embedded systems.
Hardware Components Required for Virtualization
Enabling hardware virtualization requires verification and configuration of three primary hardware layers:-
The CPU must include virtualization extensions, identifiable via:
- Intel Processors: Check for the `vmx` flag in the `cpuid` instruction output (e.g., `cpuid 0x1` returns bit 5 set for VT-x support).
- AMD Processors: Look for the `svm` flag (bit 2 in the same `cpuid` output).
- ARM Processors: Confirm the presence of `HYP` mode support (e.g., ARMv7+ with Virtualization Extensions or ARMv8-A with virtualization features).
- I/O Memory Management Unit (IOMMU): Isolates device memory access (e.g., Intel VT-d, AMD-Vi).
- APIC Virtualization: Enables efficient interrupt handling for VMs (e.g., Intel VT-x with APICv).
- Advanced > CPU Configuration (e.g., "Intel Virtualization Technology" or "AMD-V").
- Security > Virtualization (some systems hide settings under security menus). Warning: Disabling virtualization in BIOS/UEFI may prevent certain operating systems (e.g., Windows 10/11, Linux with KVM) from booting or functioning optimally.
- Hardware-assisted memory management via Extended Page Tables (EPT).
- Support for nested virtualization (VT-x with EPT).
- APIC virtualization (APICv) for reduced interrupt overhead.
- Integration with Intel SGX for secure enclaves in VMs.
- Near-native performance for compatible workloads (overhead <5%).
- EPT adds ~1-3% overhead for memory-intensive tasks.
- APICv reduces interrupt latency by ~40% in virtualized environments.
- Enterprise server virtualization (VMware ESXi, Hyper-V).
- Cloud infrastructure (AWS Nitro, Azure virtual machines).
- Development/testing of x86 operating systems.
- Rapid Virtualization Indexing (RVI) for faster context switching.
- Nested Paging (NPT) as an alternative to EPT.
- Support for Secure Virtual Machines (SVM) for trusted execution.
- AMD-Vi (IOMMU) for direct device assignment to VMs.
- Similar to VT-x; overhead <3% for most workloads.
- NPT may offer slight advantages in memory-heavy scenarios.
- SVM adds minimal overhead for security-focused VMs.
- Open-source virtualization (KVM, Xen).
- High-performance computing (HPC) clusters.
- Legacy x86 application compatibility layers.
- Stage-2 translation for guest physical-to-host physical address mapping.
- Hyp mode (Hypervisor mode) for lightweight VM management.
- Support for TrustZone integration for secure virtualization.
- Low-power optimizations for mobile/embedded use.
- Overhead comparable to x86 (~2-5% for ARMv8).
- Stage-2 translation adds minimal latency (~1-2% vs. x86 EPT).
- Ideal for battery-powered devices (e.g., Raspberry Pi 4 with virtualization).
- Mobile virtualization (Android with virtualization support).
- Embedded systems (e.g., QEMU/KVM on ARM).
- Edge computing and IoT gateways.
- Look for `svm` for AMD CPUs.
- Example output for an Intel CPU with VT-x:
- Example output:
- Press Win + R, type `msinfo32`, and navigate to: Components > Processor.
- Under Processor Features, check for:
- Virtualization (VT-x) for Intel.
- Virtualization (AMD-V) for AMD.
- Example screenshot description:
- The Processor Features section lists flags in a table. If `vmx` or `svm` is present, the CPU supports virtualization.
- Navigate to:
- Advanced > CPU Configuration (ASUS, Gigabyte).
- Security > Virtualization Technology (Dell, HP).
- Advanced > CPU Settings (MSI).
- The setting may appear as:
- Intel Virtualization Technology (VT-x).
- Intel VT for Directed I/O (VT-d) (optional, for I/O virtualization).
- Locate under:
- Advanced > CPU Configuration (ASUS, ASRock).
- Security > AMD-V (Lenovo, HP).
- The setting is often labeled:
- AMD-V (SVM Mode).
- AMD-Vi (Virtualization).
- Advanced > CPU Configuration or Security menus. 3. Locate the virtualization setting (e.g., Intel VT-x or AMD-V) and set it to Enabled.
- ASUS BIOS:
- Path: Advanced > CPU Configuration > Intel Virtualization Technology.
- Setting: Toggle between [Disabled] [Enabled].
- Gigabyte BIOS:
- Path: M.I.T. > Advanced CPU Core Settings > Intel VT-x.
- Setting: [Disabled] [Enabled] with a checkmark icon.
- Dell UEFI:
- Path: Security > Virtualization Technology.
- Setting: [Disabled] [Enabled] with a dropdown menu.
- Disabled CPU Flags:
- Some CPUs ship with virtualization flags disabled by default in the BIOS, even if the hardware supports them. Always verify both CPU and firmware settings.
- Example: An Intel Core i7-9700K may list `vmx` in `cpuid` but fail to enable virtualization if the BIOS setting is overlooked.
- Older BIOS/UEFI versions may lack support for newer virtualization features (e.g., Intel VT-x with EPT or AMD-V with RVI).
- Solution: Update BIOS/UEFI to the latest version from the motherboard manufacturer’s website.
- Certain chipsets (e.g., very old Intel 9-series or AMD 7-series) may not fully support virtualization extensions, even on compatible CPUs.
- Example: A 2012-era ASUS P8Z77-V motherboard supports Intel VT-x, but some budget models lacked proper I/O virtualization (VT-d).
- If another hypervisor (e.g., a pre-installed VMware or Hyper-V) is active, it may lock the virtualization extensions, preventing other software from using them.
- Solution: Disable conflicting hypervisors or use tools like `bcdedit` (Windows) to remove them.
- Some systems with Secure Boot or Trusted Platform Module (TPM) enabled may block virtualization features unless explicitly configured.
- Example: A Lenovo ThinkPad with TPM 2.0 may require TPM Virtualization Support to be enabled in BIOS.
- Even with hardware support, the operating system may not expose virtualization capabilities if not configured properly.
- Example: Windows
- Key combinations must be pressed immediately after power-on or system restart.
- Some systems (e.g., modern Windows 10/11 with Secure Boot) may require disabling Fast Boot or Secure Boot temporarily.
- Laptops with fingerprint readers or Windows Hello may override traditional BIOS entry methods.
-
Key Shortcut Variations by Manufacturer
The following table lists default BIOS/UEFI entry keys, though some systems may require alternative methods (e.g., pressing `Esc` first, then selecting BIOS from a boot menu). -
Troubleshooting Non-Responsive BIOS Entry
If the system ignores key presses, attempt the following:- Restart the system and press the key repeatedly within the first 2–3 seconds of boot.
- Check for manufacturer-specific documentation (e.g., Dell’s BIOS Setup Guide or Lenovo’s Vantage software).
- Disable Fast Boot in Windows (if applicable) via:
- Open Control Panel > Power Options > Choose what the power buttons do.
- Click Change settings that are currently unavailable and uncheck Turn on fast startup.
- For laptops with Windows Hello/Fingerprint Login, boot into Advanced Startup (hold `Shift` while clicking Restart in Windows) and select UEFI Firmware Settings.
- Reset BIOS settings to default via the BIOS Setup Utility (look for Load Default Settings or Reset to Default).
- Intel VT-x (Virtualization Technology for x86) may appear as: Intel Virtualization Technology (VT-x) Intel-VT Hardware Virtualization
- AMD-V (AMD Virtualization) may appear as: AMD-V SVM Mode (Secure Virtual Machine)
- Intel VT-d (Direct I/O Virtualization) is unrelated to CPU virtualization but may appear in Chipset menus.
-
General Navigation Steps
Virtualization settings are rarely in the main BIOS screen; they require traversing submenus. Use the following approach:- Navigate to Advanced > CPU Configuration or Northbridge/Chipset Settings.
- Look for submenus like Security, Virtualization, or Performance.
- If unavailable, check System Agent (SA) Configuration (Intel) or FCH (Fusion Controller Hub) Settings (AMD).
-
Manufacturer-Specific Paths
The table below outlines the typical menu hierarchy for enabling virtualization, including setting names and their locations. - CPU with Intel VT-x with EPT (Extended Page Tables) or AMD-V with RVI (Rapid Virtualization Indexing).
- Kernel compiled with KVM nested virtualization support (`CONFIG_KVM_INTEL` or `CONFIG_KVM_AMD` with nested features).
- BIOS/UEFI must enable VT-x/AMD-V and Virtualization Extensions (e.g., Intel VT-x with EPT, AMD-V with RVI).
- A Windows Pro, Enterprise, or Datacenter edition (not Home).
- Virtualization-Based Security (VBS) and Hyper-V enabled in Windows Features.
- CPU with SLAT (Second Level Address Translation) support.
- Open Hyper-V Manager > Virtual Switch Manager > External Virtual Switch.
- Right-click the VM > Settings > Processor > Check "Enable virtualization extensions". 4. For Group Policy enforcement (on domain-joined systems), set:
- Performance Overhead: Nested virtualization adds latency due to double translation of memory and I/O operations. Benchmarking shows 10–30% degradation in guest OS performance compared to non-nested setups.
- Security Risks: Nested VMs increase the attack surface. A compromised guest VM could exploit vulnerabilities in the host hypervisor or BIOS. Mitigate risks by:
- Isolating nested VMs in separate networks.
- Using Hardware-Assisted Virtualization (HVT) with Secure Boot and Trusted Platform Module (TPM).
- Restricting guest OS permissions via User Account Control (UAC) and AppLocker.
- Enable Nested Paging (reduces overhead for 64-bit guests).
- Enable VT-x/AMD-V (if disabled, the VM will fall back to software emulation). 4. For nested virtualization, use the `--enable-nested-vt-x` flag when starting the VM:
- VMware Workstation: Right-click VM > Settings > Processors > Check "Use Intel VT-x/AMD-V" and "Enable virtualization of the virtualized machine".
- VMware Player: Use the `.vmx` file to add:
- EPT (Intel) / RVI (AMD) enabled in BIOS.
- VMware Tools installed with the `vhv.enable` flag.
- Open Hyper-V Manager > Virtual Switch Manager > External Virtual Switch.
- Right-click the VM > Settings > Processor > Check "Enable virtualization extensions". 3. For nested Hyper-V, ensure the host VM has:
- SLAT support (check via `systeminfo`).
- Hypervisor-Enhanced Mode (HEM) enabled in Group Policy:
- "VT-x disabled by BIOS":
- Verify BIOS/UEFI settings for Intel VT-x or AMD-V.
- Check for BIOS updates (some older versions disable VT-x by default).
- On Linux, ensure the `kvm-intel` or `kvm-amd` kernel module is loaded:
- Run virtualization software as Administrator (Windows) or with sudo (Linux).
- On Linux, add the user to the `kvm` and `libvirt` groups:
- `intel_iommu=on` (for Intel systems with VT-d).
- `amd_iommu=on` (for AMD systems with IOMMU).
- `kvm-intel.nested=Y` or `kvm-amd.nested=Y` (enables nested virtualization). -
- VirtualBox:
- Navigate to Settings > System > Acceleration.
- Enable Enable VT-x/AMD-V.
- VMware Workstation:
- Go to VM > Settings > Processors.
- Check Virtualize Intel VT-x/AMD-V.
- KVM/QEMU:
- Use `-cpu host` flag to pass through CPU features: ```bash
- Linux: `perf stat`, `vmstat 1`, or `sar -u` (for CPU utilization).
- Windows: Resource Monitor (`resmon`) or Performance Monitor (`perfmon`).
- ESXi: `esxtop` or vSphere Client for real-time metrics.
- Reboot and enter BIOS/UEFI to enable Intel Virtualization Technology (VT-x) or AMD-V.
- Update BIOS/UEFI to the latest version.
- Disable Hyper-V on Windows (if using another hypervisor): ```powershell
- For ESXi, enable nested virtualization: ```bash
- In VM settings (e.g., VMware), enable "Expose hardware-assisted virtualization to the guest OS".
- On Linux guests, install `kvm_amd` or `kvm_intel` modules if using nested KVM.
- Temporarily disable antivirus during VM operations.
- Add exclusions for hypervisor processes (e.g., `vmware-vmx`, `qemu-system-x86_64`).
- Update antivirus definitions to ensure compatibility with virtualization.
- Verify CPU model supports VT-x/AMD-V (e.g., Intel Core i5/i7/i9 post-2010, AMD Ryzen/EPYC).
- Check manufacturer documentation for CPU specifications.
- Consider upgrading hardware if virtualization is critical.
- Allocate fewer vCPUs to the VM or enable hyperthreading in BIOS.
- Use CPU pinning to assign specific cores to the VM (e.g., in VMware or KVM).
- Monitor host CPU usage with `htop` or Task Manager to identify bottlenecks.
Verification Command (Linux):The chipset must support the CPU’s virtualization features, often through:
`egrep -c '(vmx|svm)' /proc/cpuinfo`
A non-zero output indicates virtualization support.
The BIOS/UEFI must expose virtualization settings, typically under:
Comparison of Virtualization Technologies
The following table contrasts the primary CPU-level virtualization technologies, highlighting architectural differences, performance implications, and use cases.| Name | Supported Architectures | Key Features | Performance Impact | Common Use Cases |
|---|---|---|---|---|
| Intel VT-x | x86 (Intel Core 2 Duo and later, Xeon, Atom) | |||
| AMD-V | x86 (AMD Athlon 64 and later, Ryzen, EPYC) | |||
| ARM Virtualization Extensions | ARMv7+ (with Virtualization Extensions), ARMv8-A |

Checking System Compatibility for Hardware Virtualization
Hardware virtualization relies on CPU and firmware support to enable features like Intel VT-x (Virtualization Technology for x86) or AMD-V (Secure Virtual Machine). Before enabling virtualization, verifying system compatibility ensures seamless integration with hypervisors (e.g., VMware, VirtualBox, or Hyper-V). This involves examining CPU specifications, interpreting virtualization flags, and confirming BIOS/UEFI settings. Misconfigurations or unsupported hardware can lead to performance degradation or complete failure to launch virtual machines.Verifying CPU Support for Virtualization
Modern CPUs from Intel and AMD include hardware-assisted virtualization extensions, identifiable through specific flags in their instruction sets. These flags must be enabled in both the CPU and BIOS/UEFI to function.Intel CPUs expose virtualization support via the `vmx` flag in the `CPUID` instruction. This flag appears when querying leaf 1 of the `CPUID` instruction (EAX=1). Similarly, AMD CPUs use the `svm` flag (also queried via `CPUID`, leaf 1). Below are methods to check these flags across operating systems:
#### Linux: Using `cpuid` Command
The `cpuid` utility (part of the `cpuid` package) decodes CPU feature flags, including virtualization support.
1. Install the tool if unavailable:
sudo apt install cpuid # Debian/Ubuntu
sudo dnf install cpuid # Fedora/RHEL
2. Run the command to check for `vmx` (Intel) or `svm` (AMD):
cpuid
- Look for `vmx` in the `Feature Flags` section for Intel CPUs.
Feature Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid
- Key Flag: `vmx` (Intel) or `svm` (AMD).
#### Windows: Using `systeminfo` or `msinfo32`
Windows provides built-in tools to inspect CPU virtualization support without third-party utilities.
1. Via Command Prompt (`systeminfo`):
Open Command Prompt as Administrator and run:
systeminfo | findstr /B /C:"Hyper-V Requirements"
- If Virtualization Enabled In Firmware appears as `Yes`, the CPU supports hardware virtualization.
Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.
- For detailed CPU flags, use:
wmic cpu get Name,ExtendedFeatures
- Look for `vmx` (Intel) or `svm` (AMD) in the `ExtendedFeatures` column.
2. Via `msinfo32` (System Information):
#### macOS: Using `sysctl`
On macOS, virtualization support is limited to Intel-based systems (Apple Silicon uses a different architecture). To check:
sysctl -a | grep machdep.cpu.features
- Look for `VMX` in the output (indicates Intel VT-x support).
Examining BIOS/UEFI Settings for Virtualization
Even if the CPU supports virtualization, the feature must be explicitly enabled in the BIOS/UEFI firmware. Disabled settings are a common cause of virtualization failures.Typical Locations for Virtualization Settings:
1. Intel VT-x (Virtualization Technology):
2. AMD-V (Secure Virtual Machine):
Steps to Enable Virtualization in BIOS/UEFI:
1. Restart the system and enter BIOS/UEFI by pressing the manufacturer-specific key (e.g., Del, F2, F12, or Esc).
2. Use the arrow keys to navigate to:
4. Save and Exit (typically F10).
Example BIOS/UEFI Menu Descriptions:
Common Pitfalls in Compatibility Checks
Misconfigurations or hardware limitations can prevent virtualization from functioning correctly. Below are frequent issues encountered during compatibility verification:
- Outdated or Incompatible Firmware:
- Unsupported Motherboard Chipset:
- Hypervisor Conflicts:
- Secure Boot or TPM Interference:
- Virtualization Not Enabled in OS:
Enabling Virtualization in BIOS/UEFI
Hardware virtualization requires explicit activation within the system firmware (BIOS/UEFI) to allow the CPU to offload virtualization tasks. This process varies by manufacturer, as each implements unique key combinations for accessing BIOS/UEFI and distinct menu structures for virtualization settings. Below are standardized procedures for major manufacturers, including troubleshooting for systems that fail to enter BIOS/UEFI, along with a structured reference table for quick navigation.The BIOS/UEFI interface serves as the foundational layer for hardware-level configurations, including virtualization support. Enabling virtualization typically involves locating settings related to CPU virtualization extensions (e.g., Intel VT-x, AMD-V) within nested menus such as Advanced CPU Settings, Security, or Chipset Configuration. Terminology may differ between manufacturers, requiring careful verification of setting names to avoid misconfigurations.
Accessing BIOS/UEFI Across Manufacturers
The method to enter BIOS/UEFI depends on the system manufacturer, as each uses proprietary key combinations during the boot sequence. Below are the default key shortcuts for major manufacturers, along with troubleshooting steps for systems that fail to respond to these keys.Important Note:
| Manufacturer | Default Key(s) | Alternative Method | Notes |
|---|---|---|---|
| Dell | F2 |
Press Esc during boot, then select BIOS Setup. |
Some models (e.g., XPS, Latitude) may use F12 for boot menu first. |
| Lenovo (ThinkPad) | F1 |
Hold Novideo (between Ctrl and Alt) during boot. |
Legacy systems may require F2. |
| ASUS | Del |
Press Esc during boot, then select BIOS. |
ROG/ZenBook models may use F2. |
| HP | F10 (BIOS) / Esc (Boot Menu) |
For some Pavilion/Envy models, press F6 during boot. |
F10 may also access System Recovery. |
| MSI | Del |
Some gaming laptops (e.g., Raider) require F2. |
Check for MSI ClickBIOS in Windows for alternative access. |
| Acer | F2 or Del |
Press Alt + F10 during boot. |
Switched-mode systems (e.g., Predator) may use F12. |
| Gigabyte | Del |
Press F12 for boot menu, then select BIOS. |
Some motherboards support Q-Flash (Ctrl + F8) for BIOS updates. |
| Intel NUC | F2 |
No alternatives; requires immediate key press. | UEFI-only systems (no legacy BIOS). |
Locating and Enabling Virtualization Settings
Once BIOS/UEFI is accessed, virtualization settings are typically nested within CPU, Security, or Chipset menus. Terminology varies by manufacturer and CPU architecture (Intel vs. AMD), requiring precise navigation. Below are structured paths for enabling virtualization, including common setting names and their Intel/AMD equivalents.Critical Terminology Clarifications:
AMD-Vi (Virtualization for I/O)
| Manufacturer | Menu Path | Setting Name (Intel) | Setting Name (AMD) | Default State |
|---|---|---|---|---|
| Dell | Advanced > CPU Configuration > Intel Virtualization Technology |
Intel (R) Virtualization Technology |
AMD-V |
Disabled (may require enabling in Security > Virtualization Support). |
Leave a Comment
Comments are moderated before appearing. The data you submit is processed according to the Privacy Policy of www.linuxunplugged.com.