VirtualBox

Opened 10 years ago

Closed 8 years ago

Last modified 6 years ago

#12350 closed defect (invalid)

Hardware Virtualisation support not detected if Hyper-V installed

Reported by: Francois Nel Owned by:
Component: other Version: VirtualBox 4.3.0
Keywords: Cc:
Guest type: Windows Host type: Windows

Description

I get the following error (and yes I know this has been reported many times, but please read further): VT-x/AMD-V hardware acceleration is not available on your system. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot.

The issue is that Virtualisation *is* enabled in my BIOS and I also made sure my BIOS is upgraded to the latest version. I also confirmed it with the Coreinfo.exe (http://technet.microsoft.com/en-us/sysinternals/cc835722.aspx) tool. Here is the ouput of that tool:

Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz
Intel64 Family 6 Model 42 Stepping 7, GenuineIntel
HYPERVISOR      *   Hypervisor is present
VMX             -   Supports Intel hardware-assisted virtualization
EPT             -   Supports Intel extended page tables (SLAT)

Here is the thing: I used VirtualBox on the same machine, but with Windows 7 and I could run exactly the same x64 guest images.

Attachments (3)

VBox.log (79.6 KB ) - added by Francois Nel 10 years ago.
Log file
Coreinfo.txt (5.7 KB ) - added by tuhinchakravorty 9 years ago.
VBox.2.log (53.8 KB ) - added by tuhinchakravorty 9 years ago.

Download all attachments as: .zip

Change History (13)

by Francois Nel, 10 years ago

Attachment: VBox.log added

Log file

comment:1 by Mihai Hanor, 10 years ago

The output of Coreinfo confirms that this is not a VirtualBox issue. VMX is not available (the "minus" sign) and that a hypervisor is already present (the asterisk sign). We can assume it's not VirtualBox's hypervisor.
After enabling VT-x in the BIOS, shutdown the PC/laptop, if the BIOS doesn't do it for you. Do not use any form of standby/hibernation.

comment:2 by Francois Nel, 10 years ago

I simply un-installed Hyper-V and it works again. I would like to change this to a suggestion that VirtualBox should please warn you that another virtualisation service/application is running. This will it so much clearer why x64 Guests would not start up.

Version 0, edited 10 years ago by Francois Nel (next)

comment:3 by Frank Mehnert, 10 years ago

priority: blockermajor
Summary: x64 Hardware Virtualisation support not detected on Windows 8.1Hardware Virtualisation support not detected if Hyper-V installed

by tuhinchakravorty, 9 years ago

Attachment: Coreinfo.txt added

by tuhinchakravorty, 9 years ago

Attachment: VBox.2.log added

comment:4 by tuhinchakravorty, 9 years ago

Hi,

I am trying to install ESXi 5.1 in VirtualBox. But, I have got an error stating "hardware virtualization warning hardware virtualization is not a feature of the cpu or is not enabled in the bios". Please let me know if there anything wrong in my task. I have attached 2 files named as VBox.2.log and Coreinfo.txt.

in reply to:  4 comment:5 by Francois Nel, 9 years ago

Replying to tuhinchakravorty:

Hi,

I am trying to install ESXi 5.1 in VirtualBox. But, I have got an error stating "hardware virtualization warning hardware virtualization is not a feature of the cpu or is not enabled in the bios". Please let me know if there anything wrong in my task. I have attached 2 files named as VBox.2.log and Coreinfo.txt.

You are trying to install a virtualisation technology within another virtual machine. Hell, are you trying to setup the Matrix here ...lol I guess the VirtualBox's BIOS does not expose the hardware virtualization of the physical CPU and that the ESXi OS now reports that the virtualised CPU (provided by VirualBox VM) does not support it. But I'm just guessing. Would love to know the educated answer though...

in reply to:  4 comment:6 by Ramshankar Venkataraman, 9 years ago

Replying to tuhinchakravorty:

Hi,

I am trying to install ESXi 5.1 in VirtualBox. But, I have got an error stating "hardware virtualization warning hardware virtualization is not a feature of the cpu or is not enabled in the bios". Please let me know if there anything wrong in my task. I have attached 2 files named as VBox.2.log and Coreinfo.txt.

VirtualBox does not support nested hardware virtualization, so what you are trying to do will not work. The guest will not see any VT-x/AMD-V capabilities which is why you see that error.

comment:7 by Frank Mehnert, 9 years ago

Resolution: duplicate
Status: newclosed

Closing this as duplicate. #4032 might cover that problem.

comment:8 by HOP, 8 years ago

Resolution: duplicate
Status: closedreopened

I don't think the original report is a duplicate of #4032. The issue is that you cannot run x64 guest machine if Hyper-V is installed on the same host machine. The original request is not talking about nested virutalization, but running VirtualBox and Hyper-V on the same machine.

comment:9 by Frank Mehnert, 8 years ago

Resolution: invalid
Status: reopenedclosed

Indeed, this has nothing to do with nested virtualization. However, if Hyper-V is installed on the current system then VT-x is not available for VirtualBox. This is nothing we can fix, so the only solution is to disable Hyper-V if VirtualBox should be used on the same system.

comment:10 by FrobozzWiz, 6 years ago

The problem is Hyper-V "hogs" the VT-x in the name of security. So if you want a fix for this then you need to upvote the following MS Feedback entry --> It would be awesome if Hyper-V could coexist with other hypervisor technologies like VMWare or VirtualBox

Just launch the feedback hub on Windows by hitting Windows Key + F and then search for the above story.

Until then just uninstall Hyper-V.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use