Virtualbox amd v error

VirtualBox – замечательный программный инструмент, позволяющий устанавливать и запускать операционные системы и приложения в изолированной безопасной среде, а также выполнять различные тестирования их функций. Но может случится так, что в один момент при запуске виртуальной машины вы получите ошибку «Аппаратное ускорение (VT-x AMD-V) недоступно в вашей системе» и установленная на VirtualBox система не сможет запуститься.

В таких случаях пользователи нередко начинают искать причины неполадки в самом VirtualBox, изменять его настройки, переустанавливать и тому подобное, но корень проблемы обычно скрывается глубже. Если вы зайдете в настройки виртуальной машины в разделе «Система», то увидите, что вкладка «Ускорение» неактивна. Указанная ошибка редко возникает вдруг, «ни с того ни с сего», обычно ей предшествуют критические сбои, изменения системных настроек или аппаратные неполадки.

Наиболее часто встречающаяся причина ошибки «Аппаратное ускорение (VT-x AMD-V) недоступно в вашей системе» заключается в сбое настроек BIOS. Обязательно проверьте эту настройку, если она будет отключена, виртуализация в системе работать не будет. Обычно эта опция находится в разделе Advanced или Advanced → CPU Configuration. Называться она может Secure Virtual Machine Mode, Intel Virtualization Technology, Virtualization Extensions или AMD-V. Значение ее должно выставлено Enabled.

Отдельно стоит сказать о ноутбуках, владельцем которых пришлось столкнуться с аппаратными неполадками в системе энергообеспечения. Ошибка аппаратного ускорения в VirtualBox наблюдалась после извлечения аккумулятора (переход на работу только от сети), после повреждения питающего кабеля и т.п. Любопытно, но ошибка может наблюдаться и при активной опции виртуализации в BIOS. В таких случаях все обычно решается правильной перезагрузкой, то есть выполненной через интерфейс или командную строку.

Также обратите внимание на следующий момент. Если на ноутбуке используется гибернация, в BIOS после выключения лэптопа вы можете не попасть, вместо этого у вас начнется загружаться система. Причина — изменение параметров электропитания, а именно, действия кнопок питания. Используйте перезагрузку или измените действие таким образом, чтобы при нажатии «Завершении работы» компьютер действительно выключался.

Схему управления питанием при этом лучше выбрать «Сбалансированная».

Некоторые пользователи сообщают о восстановлении работы VirtualBox после отключения в BIOS опции Execute Disable Bit. Используйте этот способ в крайнем случае, если ничего другое не помогает. Функция Execute Disable Bit обеспечивает дополнительную защиту ПК от вирусов, поэтому отключать ее не рекомендуется. В разных версиях BIOS она может называться по-разному: XD Technology, NX Technology, NX BIOS Control, Intel XD Bit, No-Execute Memory Protect. Располагается она в разделе Advanced.

Но есть и другая причина, по которой VirtualBox может не видеть аппаратного ускорения. Такое бывает, если на ПК активен системный компонент Hyper-V. Откройте окно управления компонентами Windows, отыщите пункт Hyper-V и, если напротив него установлены галочки, снимите их, примените новые настройки и перезагрузите компьютер.

После этого созданные в VirtualBox машины должны начать запускаться. Ну и напоследок не помешает проверить настройки аппаратной виртуализации в самом виртуалбоксе. Галочки VT-x AMD-V и Nested Paging на вкладке «Ускорение» должны быть установлены.

Several users are getting the ‘VT-x/AMD-V hardware acceleration is not available on your system’ error when trying to install or launch a virtual machine in Oracle VM Virtualbox. The issue is not specific to a certain Windows version as it’s reported to occur with every recent Windows release.

We investigated this particular issue by looking at various user reports and the repair strategies that they used to get the issue resolved. Based on what we gathered, there are several common scenarios that will trigger this particular error message:

If you’re currently struggling to resolve the ‘VT-x/AMD-V hardware acceleration is not available on your system’ error, this article will provide you with a collection of verified troubleshooting steps. Down below, you’ll find several popular methods that other users in a similar situation have used to resolve the error message.

In order to spare yourself from trying out unnecessary fixes, follow the methods below in the order that they are presented. You should eventually find a method that resolves (or at least provides an answer for) your problem.

Before continuing, try performing an SFC scan.

Method 1: Verifying if your CPU supports virtualization

Before trying out anything else, it’s important that you take the time to investigate whether your computer is equipped to use VT-X or AMD-V. All the newer CPUs will support virtualization nowadays (including the ones in the low-range). However, if you’re working with an older CPU, you should start by verifying if your CPU support virtualization.

There are a couple of ways to verify whether your CPU is equipped to use virtualization – you either use a dedicated program that will tell you if virtualization is supported on your CPU or do things manually.  Follow whichever guide is closer to your preferred approach.

How to verify if your CPU supports Virtualization automatically

One of the easiest ways to find out if your computer supports virtualization is to use a dedicated tool called SecurAble. Among other things, this tool will analyze the presence of operational model process features including virtualization. Here’s a quick guide on using SecurAble:

1. Visit this link (here) and click on Download now to download the latest version of Securable.
2. Open the SecurAble executable and click Yes at the UAC (User Account Control) prompt.
3. If your computer is equipped to support hardware virtualization, you will see a green Yes above Hardware Virtualization.

If the answer is Yes, it means that your computer’s CPU is equipped to support virtualization and one of the next methods below will allow you to resolve the error message. If you determined that hardware virtualization is not supported, follow the other methods below will not resolve the error message.

How to verify if your CPU supports Virtualization manually

If you prefer to do things manually, you can verify whether your CPU supports VT-x (on Intel) or AMD-V (on AMD) by investigating the specifications of your CPU manually. To do this, follow one of the two guides below (according to your CPU manufacturer):

Intel

With Intel processors, you can see whether Virtualization is supported by looking at the Processor Documentation which can be found on ARK.INTEL.COM.  Once you get there, use the search function to search for your specific CPU model.

Then, scroll down to the Advanced Technologies tab and see the status of Intel® Virtualization Technology for Directed I/O (VT-d) and Intel® Virtualization Technology (VT-x). If any of them is labeled as No, then virtualization technology is not supported by your processor model.

AMD

If you have an AMD processor, you can verify if it supports virtualization by looking at the specifications on AMD’s website. Use the search function to find your specific model or choose it from the list. Once you arrive at the webpage dedicated to your CPU model, expand the Key Features drop-down menu and see if Virtualization is among the Supported Technologies.

If you found that virtualization is supported, proceed with the next methods below in order to get the issue resolved.

Method 2: Disabling Hyper V

Hyper-V (formerly known as Windows Server Virtualization) is Microsoft’s proprietary virtualization technology. Hyper-V is perfectly capable of creating virtual machines on x86 and x64 system running Windows, but it’s not used by VirtualBox or VMware for stability reasons.

However, the most recent Windows versions are programmed to prioritize Hyper-V over VT-X or AMD-V. And since Hyper-V will conflict with similar virtualization technology, VT-x or AMD-V will be disabled by default whenever Hyper-V is enabled.

As you can imagine, this will create errors with Virtualbox, VMware or similar software, since most of them are not designed to work with Hyper-V.

Fortunately, disabling Hyper-V will resolve the ‘VT-x/AMD-V hardware acceleration is not available on your system’ error if the issue. There are multiple methods that you can follow to disable Hyper-V and allow VT-x or AMD-V to take over. Feel free to follow whichever one you feel more comfortable with.

Disabling Hyper-V via Command prompt

The easiest way to disable Hyper-V is by typing a command inside an elevated Command Prompt window. Here’s what you need to do:

1. Press Windows key + R to open up a Run dialog box. Then, type “cmd” and press Ctrl + Shift + Enter to open up an elevated Command Prompt. When prompted by the UAC (User Account Control), click Yes to grant administrative privileges.
2. In the elevated Command Prompt, type/paste the following command and press Enter to disable the Hyper-V function:

   dism.exe /Online /Disable-Feature:Microsoft-Hyper-V

   As soon as you’ve finished running this command, Hyper-V will be disabled and the virtualization technology provided by your processor will be reinforced.

Disabling Hyper-V via GUI

Another method that will enable you to disable Hyper-V technology is to use the Control Panel interface. This method is slower but should be preferred if you’re not comfortable with running commands via the terminal. Follow the steps down below to disable Hyper-V via the Programs and Features screen:

1. Press Windows key + R to open up a Run dialog box. Then, type “appwiz.cpl” and press Enter to open up the Programs and Features screen.
2. Inside the Programs and Features screen, click on Turn Windows features on or off from the left-hand pane.
3. From the Windows Features menu, expand the Hyper-V folder and make sure to uncheck Hyper-V Management Tools and Hyper-V Platform before clicking OK.
4. Restart your computer and see if the error has been resolved at the next startup.

If you’re still encountering the ‘VT-x/AMD-V hardware acceleration is not available on your system’ error, move down to the next method below for steps on ensuring that virtualization is enabled from BIOS/UEFI.

Method 3: Enabling virtualization withing BIOS/UEFI

Another reason why you might get the ‘VT-x/AMD-V hardware acceleration is not available on your system’ error is due to virtualization being disabled from your BIOS settings. Although virtualization is enabled by default on most computer configurations, this is quite a common occurrence. For a lot of affected users, a BIOS update is what ended up disabling the virtualization technology in BIOS.

Fortunately, you can write this wrong quite easily by accessing your BIOS/UEFI settings and re-enabling the virtualization technology from there.

Note: Motherboard released prior to the release of Windows 8 are likely to use BIOS, while most modern PC builds are using UEFI.

On a BIOS-powered computer, you’ll need to press the Setup key during the initial startup screen. The Setup key is usually one of the F keys (F2, F4, F6, F8) or the Del key. If you can’t identify the setup key specific to your motherboard, do an online search on the ‘motherboard model + setup key‘.

On a UEFI-based computer, boot into the Advanced Startup options menu. From there, you can access the UEFI firmware settings.

Once you gain entry into your BIOS/UEFI settings, start looking for an option labeled Intel VT-x, AMD-V, Intel Virtualization Technology, Vanderpool, etc. You can typically find the option under Processor,  Security, Chipset, Advanced, Advanced Chipset Control, Advanced CPU configuration, etc.

When you manage to find the option, make sure you enable it.

Note: The settings you’ll find inside your BIOS/UEFI will be different depending on your motherboard and CPU manufacturer. If you can’t find the option yourself, search online for specific steps on enabling hardware virtualization on your configuration.

Once you manage to enable virtualization, save the changes and restart your computer. At the next startup, the ‘VT-x/AMD-V hardware acceleration is not available on your system’ error should no longer occur when you try to install or run a virtual machine.