virtualbox.org

Hello,

I have the following problem with newest VB, that it doesnt detect my CPU correctly. It is an Intel i7-3770, Intel Virtualization and vt-d are activated in bios.

Make sure the 64bit template is selected in the guest settings.

There are no 64bit templates selectable... Like I said. It seems VB doesnt recognizes the cpu as 64bit. Look at the picture, options for more than 1 core is greyed out, and virtualization option tab is also greyed out.

Make sure Virtualization is enabled in the BIOS and Hyper-V is not installed, or any other product using Virtualization is running.

Thank you noteirak for your hint. You were right, the reason was Hyper-V was installed, and that blocked VB from working. Maybe it would be better if VB would pop up a warning message that something like this is installed and blocking somehow VB from working properly. How should someone know this could be the reason?

buffl wrote:How should someone know this could be the reason?

You're asking the wrong people. To us it's obvious: VBox isn't seeing VT-x therefore something must be blocking it. It wouldn't be very practical for the error dialog to mention Hyper-v specifically, since the blocker could be anything. We just happen to know that in very recent times on Win8 hosts where the user asserts that the BIOS feature is definitely enabled - then the blocker is usually Hyper-v.

responsibility ping pong? I cant agree on this "simple" argumentation, that it "can be anything", because Hyper-V mostly is the only virtualisation under Windows which seems to lurk in the system istelf, and gets automatically run at Windows start, which is bad, because there can just be one vt-x aplication running at the same time. Therefor it is the logical task of any other virtulization app (VB in this case), to warn or give a hint, that it can't access vt-x, and therefor it isnt enabled (sure there can be a way of polling if enabled but blocked), or, it is blocked by another vt-x application (another hint, that it's most likely Hyper-V under Windows (8), and again, most likly there is a way of polling if hyper-v is installed).

That might seem logical to you but there are a number of problems with it. There really are a lot of things which can use hardware virtualization apart from Hyper-V. Another major problem is that VirtualBox also runs on Linux and OS-X which could not possibly be running Hyper-V.

In any case it's an open source project, so I'm sure the devs will accept a code contribution from you if it makes sense.