No 64 bit Guest Options Appear on creating VM

[rjmonteiro]

Hello guys,

I've just downloaded VBox (64bit) into my laptop and installed it using "Run as Administrator".

When trying to create a Virtual Machine I have no 64 bit Guest's to choose from, only 32bit.

My Laptop is a Toshiba Tecra Z40 with Windows 10 64bit installed. I've looked into the BIOS and I have VT-X enabled. I've noticed that, in the BIOS, I have the option to enable not only VT-x but also VT-D (don't know if this will be of any help).

Do you guys have any idea why this might be happening ?

Thanx in advance,
Ricardo Monteiro

[mpack]

FAQ: I have a 64bit host, but can't install 64bit guests.

[rjmonteiro]

Thank you mpack for your reply.

1. Note your exact CPU model or part number, then go online and check its capabilities. The CPU must have 64bit capability and support either Intel or AMD virtualization technologies: VT-x or AMD-v.

Already done. laptop has a 64bit CPU and support for VT-X and VT-D

2. You usualy need to enable VT-x/AMD-v in the host PC BIOS. You need to check with your PC manual or support forum to find out how to boot into the BIOS screen. This is probably not something we here at the VirtualBox forums can help you with. Once you get there you need to look for something buried in a menu, perhaps in the security category. The option may be called something like "Enable Virtualization Technology". If you see "Virtual Directed I/O" then that is a different thing. Remember to reboot your host PC after making BIOS changes - in this case a full restart from power off is required, just resuming from a hibernated state may not do the job.

In the BIOS, I have the option "VT-X only" option enabled.

3. If (1) and (2) are already taken care of, then make sure that no other host apps are already using VT-x/AMD-v. The usual culprits are system level debuggers, other VM platforms, and some resident anti-virus applications. This has become a particular issue with 64bit Windows desktop and server hosts - especially Win8/Win2k12/Win10, since these may enable Microsoft's Hyper-v VM platform by default: this grabs ownership of VT-x and won't play nice with VirtualBox.

This, sorry for my noobness , but how can I see if the VT-x is being used ?

4. When creating a VM, make sure you choose the 64-bit version of the guest OS template in <VM Settings> | General | Basic | Version, e.g. choose "Ubuntu (64 bit)" and not "Ubuntu" or "Ubuntu (32bit)". This has become more important since VirtualBox 4.3.x, because choosing the correct template also allows other modern processor features to be visible to the guest - it's not just about 64bit capability any more.

That is my problem, when creating a VM, I'd love to choose a 64-bit version of the guest OS but none appears, only 32bit versions appear.


The Vbox version I have is 5.0.8 r103449

Thank you.

[mpack]

Go over the checklist carefully. Don't skim.

[rjmonteiro]

mpack, I think I didn't skim .

to verify point 4, do you know how can I see if VT-x is being used by other app ?

[loukingjr]

Certain anti-viral/anti-malware programs such as bitdefender do if I remember correctly.

[rjmonteiro]

None installed. I'm using the one that comes with windows

[scottgus1]

Does your host OS have hyper-v turned on by default? If it is merely enabled in the OS, even if it is not used, VT-x will be taken. If it is on, turn it off and fully power down the host, then restart & try again.

Also, I believe a full power down is necessary to change the BIOS VT-x settings properly, not just a reboot. Further, your BIOS may have a typo - it's happened before. Try using VT-d only or VT-x & VT-d together. Full power offs between changes.

[mpack]

It can't be Hyper-v, because the FAQ mentions that one explicitly, and the OP assures us that he read the FAQ carefully.

[loukingjr]

Further, your BIOS may have a typo - it's happened before.

Really? That's two things I've never heard of today. Still learning.

[scottgus1]

I remember reading once of someone trying to turn something on in the BIOS and finding that when it was on it was off, and vice-versa. Not a common happening, true, but BIOS writers are human, too

[mpack]

I remember reading once of someone trying to turn something on in the BIOS and finding that when it was on it was off, and vice-versa. Not a common happening, true, but BIOS writers are human, too

Yes, but that was a report that I didn't believe. My guess is that the change didn't take until they rebooted the PC, which they hadn't previously done.

[rjmonteiro]

Tonight I'll try with the other options in the BIOS and let you know

[mpack]

There should only be one relevant option in the BIOS (again, the FAQ mentions this). Randomly playing with BIOS settings wouldn't be the best idea ever.