ML
    • Register
    • Login
    • Search
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups

    VirtualBox - No 64-bit

    IT Discussion
    6
    22
    3006
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • RojoLoco
      RojoLoco last edited by

      Install it twice? (2x32=64)

      1 Reply Last reply Reply Quote 6
      • scottalanmiller
        scottalanmiller last edited by

        But I'm going to make you sweat for a bit...

        bbigford 1 Reply Last reply Reply Quote 0
        • alex.olynyk
          alex.olynyk last edited by

          I had this issue once when I had Client Hyper-V enabled on Windows 10.

          1 Reply Last reply Reply Quote 0
          • bbigford
            bbigford @scottalanmiller last edited by

            @scottalanmiller said in VirtualBox - No 64-bit:

            But I'm going to make you sweat for a bit...

            Haha k I'll think about this one for a minute...

            1 Reply Last reply Reply Quote 0
            • scottalanmiller
              scottalanmiller last edited by

              This is because hardware virtualization is either not enabled in the BIOS, not available on the CPU or for some reason is not being passed through the OS. This is pretty common. 32bit is pretty easy to emulate in software and so VirtualBox does that. VBox predates hardware virtualization assistance just as Xen does.

              To virtualize AMD64 you need hardware assistance. So you have to have that enabled and working or VBox can't do it.

              bbigford 1 Reply Last reply Reply Quote 0
              • bbigford
                bbigford last edited by

                I've had this issue in Hyper-V when migrating hosts, but just had to go into processor compatibility... But this is nothing like that, because this is a brand new VM on a brand new installation and I'm just trying to choose a 64-bit VM template.

                1 Reply Last reply Reply Quote 0
                • bbigford
                  bbigford @scottalanmiller last edited by

                  @scottalanmiller said in VirtualBox - No 64-bit:

                  This is because hardware virtualization is either not enabled in the BIOS, not available on the CPU or for some reason is not being passed through the OS. This is pretty common. 32bit is pretty easy to emulate in software and so VirtualBox does that. VBox predates hardware virtualization assistance just as Xen does.

                  To virtualize AMD64 you need hardware assistance. So you have to have that enabled and working or VBox can't do it.

                  So I've just already gone through the BIOS, all virtualization is enabled except for some stuff regarding TPM. I know all is enabled that needs to be because I just reinstalled VB was all... and Hyper-V on my local workstation (8.1) works fine.

                  1 Reply Last reply Reply Quote 0
                  • A
                    Alex Sage last edited by Alex Sage

                    http://www.fixedbyvonnie.com/2014/11/virtualbox-showing-32-bit-guest-versions-64-bit-host-os/

                    1 Reply Last reply Reply Quote 0
                    • A
                      Alex Sage last edited by

                      Is Hyper V enabled on that computer? If so, disable it.

                      bbigford 1 Reply Last reply Reply Quote 2
                      • bbigford
                        bbigford last edited by

                        Ooooo here's an interesting one. You can't use Hyper-V and VB on the same system, if your BIOS is already setup correctly...

                        http://www.fixedbyvonnie.com/2014/11/virtualbox-showing-32-bit-guest-versions-64-bit-host-os/#.VypelXpGP1g

                        bbigford scottalanmiller 2 Replies Last reply Reply Quote 1
                        • bbigford
                          bbigford @bbigford last edited by

                          @BBigford said in VirtualBox - No 64-bit:

                          Ooooo here's an interesting one. You can't use Hyper-V and VB on the same system, if your BIOS is already setup correctly...

                          http://www.fixedbyvonnie.com/2014/11/virtualbox-showing-32-bit-guest-versions-64-bit-host-os/#.VypelXpGP1g

                          I wonder why that might be.

                          1 Reply Last reply Reply Quote 0
                          • bbigford
                            bbigford @Alex Sage last edited by

                            @aaronstuder said in VirtualBox - No 64-bit:

                            Is Hyper V enabled on that computer? If so, disable it.

                            You beat me to it.

                            1 Reply Last reply Reply Quote 0
                            • bbigford
                              bbigford last edited by

                              Probably because Hyper-V permanently takes over VT-x instead of sharing like VMware Player for instance (VB forum)... Because it's a level 1 hypervisor?

                              In either case, sharing is not caring I guess.

                              scottalanmiller 1 Reply Last reply Reply Quote 2
                              • scottalanmiller
                                scottalanmiller @bbigford last edited by

                                @BBigford said in VirtualBox - No 64-bit:

                                Probably because Hyper-V permanently takes over VT-x instead of sharing like VMware Player for instance (VB forum)... Because it's a level 1 hypervisor?

                                In either case, sharing is not caring I guess.

                                Type 1. It has nothing to do with sharing. It is because you are doing nesting. Hyper-V does not support hypervisor nesting. Why do you want to nest your hypervisors?

                                1 Reply Last reply Reply Quote 0
                                • scottalanmiller
                                  scottalanmiller @bbigford last edited by

                                  @BBigford said in VirtualBox - No 64-bit:

                                  Ooooo here's an interesting one. You can't use Hyper-V and VB on the same system, if your BIOS is already setup correctly...

                                  http://www.fixedbyvonnie.com/2014/11/virtualbox-showing-32-bit-guest-versions-64-bit-host-os/#.VypelXpGP1g

                                  Correct, because Hyper-V does not virtualize the virtualization functions.

                                  bbigford 1 Reply Last reply Reply Quote 0
                                  • StrongBad
                                    StrongBad last edited by

                                    Whatever you are wanting to install into VirtualBox you could just install directly onto Hyper-V.

                                    bbigford 1 Reply Last reply Reply Quote 2
                                    • bbigford
                                      bbigford @scottalanmiller last edited by bbigford

                                      @scottalanmiller said in VirtualBox - No 64-bit:

                                      @BBigford said in VirtualBox - No 64-bit:

                                      Ooooo here's an interesting one. You can't use Hyper-V and VB on the same system, if your BIOS is already setup correctly...

                                      http://www.fixedbyvonnie.com/2014/11/virtualbox-showing-32-bit-guest-versions-64-bit-host-os/#.VypelXpGP1g

                                      Correct, because Hyper-V does not virtualize the virtualization functions.

                                      A dev has a vmdk that I tried converting for HV but it just comes up as user: drac and no commands will execute. So basically the conversion is botched. I need to spin up that VM and grab some files that he needs to compare against others. I do everything in HV so I had just wanted to install VB with the intention I'd convert the vmdk (used to be just CLI only but now you can copy to VHD then attach in HV).

                                      So I'm just using VB again as a one time use.

                                      1 Reply Last reply Reply Quote 0
                                      • bbigford
                                        bbigford @StrongBad last edited by

                                        @StrongBad said in VirtualBox - No 64-bit:

                                        Whatever you are wanting to install into VirtualBox you could just install directly onto Hyper-V.

                                        It's an existing image that a new dev needs info from, and the previous dev saved it as a vmdk. I can probably use a Hyper-V conversion tool but I was trying the opposite.. Convert it in VBox which didn't work.

                                        1 Reply Last reply Reply Quote 0
                                        • bbigford
                                          bbigford last edited by

                                          Something like this, or via PowerShell...

                                          https://www.starwindsoftware.com/converter

                                          1 Reply Last reply Reply Quote 1
                                          • First post
                                            Last post