Why Virtual Box won't give me option to create 64 bits guests?

276,641

Solution 1

I ran into the same issue.

Turning off Hyper-v temporarily solved my problem and all 64bit options were available:

I use hyper-v on my laptop. When I know I don't need VMs for the day, I can squeeze a bit more performance out of the machine by turning hyper-v off with:

bcdedit /set hypervisorlaunchtype off

and a reboot. To turn it back on:

bcdedit /set hypervisorlaunchtype on (or auto start)

and reboot.

Source

Solution 2

I had the same issue (compatible hardware, options enabled - no way to create a 64 bit VM), and gave up with VirtualBox and gave VMWare Workstation a try. Fortunately, I had a similar yet explicit error asking me to uninstall Hyper-V. Deactivating it is not enough, you have to remove the component from your system. This post was helpful for me : Uninstalling HyperV from Windows 8

To remove the component simply run this command from and admin cmd (credits to @levi-botelho):

Dism /online /disable-feature /featurename:Microsoft-Hyper-V

Solution 3

VT-x/AMD-v cpus are the way to go.

See this post for more detail.

I successfully enabled this capability in my Thinkpad T420.

Solution 4

Because the VT-x setting is typically locked at power on, it is necessary to fully power down the system after changing any VT-x options in the firmware (BIOS/EFI). A simple reboot is not sufficient!

It may be related only for Intel processors

Solution 5

I had a similar issue. Post VT-x in your BIOS and restart, can you try reinstalling VirtualBox? For some reason, the 64-bit option doesn't show up unless you reinstall VirtualBox. I did that and it solved the issue for me.

Share:
276,641
Edy Bourne
Author by

Edy Bourne

Updated on September 18, 2022

Comments

  • Edy Bourne
    Edy Bourne over 1 year

    My host is x64 bits Windows 8.1.

    I downloaded the latest Virtual Box (4.3) and I'm trying to create a VM with a 64 bits Ubuntu OS (ubuntu-12.04.3-desktop-amd64).

    When I go to New VM wizard, it doesn't give me option to select "Ubuntu (x64)" as I have seen in other people's screenshots, only just "Ubuntu". As a result, the ISO can't boot. I tried in another PC and Virtual Box gives the x64 variants to most listed OS...

    Control Panel shows x64 OS, x64 processor. My host laptop is a Sony Vaio VPCZ22UGX/N, Intel® Core™ i7-2640M processor. CPUz shows Vx-t is available on my processor, of course.

    Here is what I tried so far:

    • I enabled IO APIC as required in the docs.

    • I have virtualization enabled in the BIOS. It works fine in VMware.

    • Check that Hyper-V is not running or even installed on my Windows. Same for VMware.

    • I also tried running the command:

      VBoxManage modifyvm [vmname] --longmode on

    for that VM, but no change.. I think the issue is really that I can't select x64 variant of the Ubuntu OS for that VM. Other people seem to indicate that's a requirement, but I don't get that option for some reason.

    I spent a lot of time and can't find what's wrong... Anyone knows what could be missing here?

    Thank you very much!!

    Eduardo

    • Admin
      Admin over 10 years
      What happens if you create a Ubuntu (x84) machine, then go into its settings, basic page and look at the options?
    • Admin
      Admin over 10 years
      From what you've attempted so far, I suspect you've seen this, but in case not: forums.virtualbox.org/viewtopic.php?f=6&t=57926
    • Admin
      Admin over 10 years
      @JohnLBevan I get only the x86 options.. can't change it to x64. I think you're right, I'm hitting that issue.. except that the guy fixed it by disabling hyper-v and I don't have it uninstalled.
    • Admin
      Admin over 10 years
      Have a look at this post: superuser.com/questions/367290/… - different computer, but possibly similar solution?
    • Admin
      Admin over 10 years
      Hi @JohnLBevan, thanks for your reply! Unfortunately I already enabled VT-x in the BIOS, no change.. I'm considering coming back to VMware and trying again with a newer version of VirtualBox sometime in the future..
    • Admin
      Admin over 10 years
      Did you try Securable mentioned on the above link - grc.com/securable.htm - that may help to hint where the issue is?
    • Admin
      Admin over 10 years
      Indeed I tried it... it says it VT-x is supported, but then there is a link underneath explaining that because my PC is 6 bits it cannot run VT-x code to check if the motherboard supports it. So it recommends installing a 32 bits OS to run the test again. :/ But anyways it checks for the instruction in the processor and it is available. CPUz confirmed that.. thank you!
    • Admin
      Admin over 10 years
      Other software may use and lock the VT-x modes. I had for example some issues with Intel HAXM.
    • Admin
      Admin over 10 years
      Can you show a screenshot (or register dump) of CPU-Z, please?
    • Admin
      Admin over 6 years
      This link's accepted answer fixed my version of this problem. superuser.com/q/866962/294356
  • Edy Bourne
    Edy Bourne over 10 years
    Thanks for your response. I have a Intel® Core™ i7-2640M processor. CPUz shows Vx-t is available on my processor... the mystery continues.. hehe at this point I'm back with VMware, but I will switch to Virtual box if a solution for this is encountered.
  • Kane
    Kane over 10 years
    @EduardoBorn You might need check the options in BIOS. I enabled this hardware feature via BIOS.
  • arka mandal
    arka mandal almost 10 years
    For me, key to get this working and 64-bit options to show up was to enable Config -> CPU -> "Intel (R) Virtualization Technology" and "Intel (R) Vt-d Feature" from BIOS. After that the options appeared, no need to reinstall VirtualBox.
  • derFunk
    derFunk almost 10 years
    That helped me as well.Quote: "I use hyper-v on my laptop. When I know I don't need VMs for the day, I can squeeze a bit more performance out of the machine by turning hyper-v off with: bcdedit /set hypervisorlaunchtype off and a reboot. To turn it back on: bcdedit /set hypervisorlaunchtype on (or auto start) and reboot."
  • ub3rst4r
    ub3rst4r over 9 years
    Not sure what Hyper-V has to do with it nor why it was enabled, but disabling it fixed it for me. Now there's 64-bit options for guest operating systems.
  • Ramhound
    Ramhound over 9 years
    This really isn't an answer to the author's question
  • Rafe
    Rafe over 9 years
    It's a potential solution for anyone experiencing the problem of vt-x not working and as a result not having x64 options. So thanks for the hate @ramhound.
  • Ramhound
    Ramhound over 9 years
    Its not personal. Your question was in the review because of the low quality.
  • Wes Sayeed
    Wes Sayeed over 9 years
    How does this answer apply to the question?
  • George
    George over 9 years
    excellent! finally found the solution. couldn't recall enabling hyper-v and definitely din't know this would have caused the 64 bit options to be hidden on virtualbox
  • AlikElzin-kilaka
    AlikElzin-kilaka over 9 years
    Is there a solution without reboot?
  • AlikElzin-kilaka
    AlikElzin-kilaka over 9 years
    What's VT-x/AMD-v cpus? Where can I find it?
  • AlikElzin-kilaka
    AlikElzin-kilaka over 9 years
    If this answer said to to enable visualization in the bios, than it worked for me. The bios option was VTx.
  • Xitcod13
    Xitcod13 about 9 years
    didnt work for me. running windows 8.1 Whats more i cannot set it on after i turned it off. I get "The integer data is not valid as specified. Run "bcdedit /?" for command line assistance. The parameter is incorrect."
  • Xitcod13
    Xitcod13 about 9 years
    no result with reinstall after disabling Hyper-V
  • Milson
    Milson about 9 years
    This means we can't use Windows Phone Emulator for life! :( to use 64 bits virtual guest OS ?
  • Theraot
    Theraot almost 9 years
    Removing HyperV just solved this from me, although I removed it from control panel. I didn't enable it, I guess some tool, driver or windows update did. I had 64x machines already made, they wouldn't run until I got rid of HyperV.
  • Jdbaba
    Jdbaba over 6 years
    This solution worked for me after 3 days of frustration. Thanks a lot.