Virtualbox only 32 bit linux

Linux Mint Forums

Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.

farkas Level 5
Posts: 550 Joined: Mon Sep 21, 2015 6:10 pm Location: Oregon

VirtualBox 32 bit only (Solved)

Post by farkas » Wed Nov 14, 2018 12:50 am

In a previous post «viewtopic.php?f=231&t=281175» my problem was solved!
After disabling Secure Boot I ran:

«apt purge virtualbox* && apt install virtualbox-5.2»

Decided to give it a test run. With a 64 bit Mint 18.3 ISO install DVD, which I used for my original Mint install.
To test it I booted the DVD and it worked.

My problem is that VB will only run 32 bit installs no matter what OS is selected.

In the drop down boxes there are only 32 bit choices.

On that post it was suggested to download VB from
https://www.virtualbox.org/wiki/Linux_Downloads
I found the install Debian based instructions confusing.
Looked around in their documentation and community pages and online couln’t find any clarity on how to install it.

Looking around in Mint VB forums found a possible solution:
viewtopic.php?f=231&t=279038

To make sure I removed all VB in Software Manager.

Ran the following code to insure all instances VB was gone:

wget -q -O — http://download.virtualbox.org/virtualb . x_2016.asc | sudo apt-key add —
sudo sh -c ‘echo «deb http://download.virtualbox.org/virtualbox/debian bionic non-free contrib» >> /etc/apt/sources.list.d/virtualbox.org.list’
sudo apt update && sudo apt install virtualbox-5.2 virtualbox-ext-pack

It installed
Version 5.2.22 r126460 (Qt5.9.5)

I thought it would get me the version that will run a 64 bit OS.
When I start ‘Oracle VM VirtualBox’ from Application Menu or ‘virtualbox’ in Terminal, I get the same result. 32 bit only. Clicking on check for updates in VB it says I already have the most recent version.
What should I do next?

Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.

If your query has been resolved, edit your first post and add [SOLVED] to the subject line.
If you found a solution on your own please post it.
A generation which ignores history has no past and no future.

catweazel Level 19
Posts: 9763 Joined: Fri Oct 12, 2012 9:44 pm Location: Australian Antarctic Territory

Re: VirtualBox 32 bit only

Post by catweazel » Wed Nov 14, 2018 12:59 am

«There is, ultimately, only one truth — cogito, ergo sum — everything else is an assumption.» — Me, my swansong.

farkas Level 5
Posts: 550 Joined: Mon Sep 21, 2015 6:10 pm Location: Oregon

Re: VirtualBox 32 bit only

Post by farkas » Wed Nov 14, 2018 1:04 am

OK, I am a novice LM user .
Can you or someone else show me how to execute a step by step set of commands to do that.
That way I’d learn what it each command does.
I’d appreciate it!

If your query has been resolved, edit your first post and add [SOLVED] to the subject line.
If you found a solution on your own please post it.
A generation which ignores history has no past and no future.

Re: VirtualBox 32 bit only

Post by gm10 » Wed Nov 14, 2018 2:26 am

I strongly doubt you’ve got a 32 bit version installed, there isn’t even one for LM19, but run apt policy virtualbox-5.2 to check.

Instead check your BIOS settings and make sure you’ve got the Intel virtualization and Intel VT-d options all enabled.

farkas Level 5
Posts: 550 Joined: Mon Sep 21, 2015 6:10 pm Location: Oregon

Re: VirtualBox 32 bit only

Post by farkas » Wed Nov 14, 2018 2:46 am

 apt pvirtualbox-5.2: Installed: 5.2.22-126460~Ubuntu~bionic Candidate: 5.2.22-126460~Ubuntu~bionic Version table: *** 5.2.22-126460~Ubuntu~bionic 100 100 /var/lib/dpkg/status steolicy virtualbox-5.2

I really don’t want to mess with BIOS, unless absolutely necessary.
Is there a way to check via terminal if they are.

If your query has been resolved, edit your first post and add [SOLVED] to the subject line.
If you found a solution on your own please post it.
A generation which ignores history has no past and no future.

Re: VirtualBox 32 bit only

Post by gm10 » Wed Nov 14, 2018 2:50 am

It is necessary or I wouldn’t have said so. If virtualization is disabled in the BIOS you cannot address 64-bit VMs.

That apt policy output is interesting as well. You’ve got the right version installed but for some reason you removed the virtualbox repository again after installing? Why? You should re-enable/re-add that in order to be able to receive updates.

Pierre Level 21
Posts: 12958 Joined: Fri Sep 05, 2008 5:33 am Location: Perth, AU.

Re: VirtualBox 32 bit only

Post by Pierre » Wed Nov 14, 2018 4:05 am

interestingly, and up to quite recently, it does seem that I’ve been using both 32bit & 64bit ISOs
— in a 32bit VirtualBox AKA ubuntu_trusty_i386.deb
all I’ve been doing, is to check some options, in the Guest system properties list,
but even then, there are both 32 bit & 64 bit VBs that can be selected.

Please edit your original post title to include [SOLVED] — when your problem is solved!
and DO LOOK at those Unanswered Topics — — you may be able to answer some!.

Re: VirtualBox 32 bit only

Post by gm10 » Wed Nov 14, 2018 4:16 am

Pierre wrote: ⤴ Wed Nov 14, 2018 4:05 am interestingly, and up to quite recently, it does seem that I’ve been using both 32bit & 64bit ISOs
— in a 32bit VirtualBox AKA ubuntu_trusty_i386.deb
all I’ve been doing, is to check some options, in the Guest system properties list,
but even then, there are both 32 bit & 64 bit VBs that can be selected.

That’s working as intended. As long as you’ve got 64-bit hardware with hardware virtualization support you can run 64-bit guests, the architecture of the virtualbox application doesn’t matter.

Pierre Level 21
Posts: 12958 Joined: Fri Sep 05, 2008 5:33 am Location: Perth, AU.

Re: VirtualBox 32 bit only

Post by Pierre » Wed Nov 14, 2018 4:44 am

and which, continues to confirm my theory, that all PCs
from Vista onwards — are 64Bit based CPUs
( my PCs are all Ex Vista )
— — great for recycling .. .

so — what type of machine does stevep3129 have ?.
— it should be a 64bit machine, so it seems.

Please edit your original post title to include [SOLVED] — when your problem is solved!
and DO LOOK at those Unanswered Topics — — you may be able to answer some!.

farkas Level 5
Posts: 550 Joined: Mon Sep 21, 2015 6:10 pm Location: Oregon

Re: VirtualBox 32 bit only

Post by farkas » Wed Nov 14, 2018 10:43 pm

Looked around in BIOS and found what I think VT-d might be in CPU setup, Intel Virtualization Technology, it was disabled, enabled it.
My machine is home build a little over three years old.
Here is my system info:

steve@steve ~ $ inxi -Fxz System: Host: steve Kernel: 4.15.0-39-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Cinnamon 3.8.9 (Gtk 3.22.30-1ubuntu1) Distro: Linux Mint 19 Tara Machine: Device: desktop System: ASUS product: All Series serial: N/A Mobo: ASUSTeK model: Z97-A-USB31 v: Rev 1.xx serial: N/A UEFI: American Megatrends v: 2501 date: 06/24/2015 Battery hidpp__0: charge: N/A condition: NA/NA Wh model: Logitech Wireless Mouse M325 status: Discharging CPU: Quad core Intel Core i5-4690K (-MCP-) arch: Haswell rev.3 cache: 6144 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 27996 clock speeds: max: 4300 MHz 1: 1077 MHz 2: 984 MHz 3: 978 MHz 4: 1130 MHz Graphics: Card: NVIDIA GM206 [GeForce GTX 950] bus-ID: 01:00.0 Display Server: x11 (X.Org 1.19.6 ) drivers: nvidia (unloaded: modesetting,fbdev,vesa,nouveau) Resolution: 1920x1080@60.00hz OpenGL: renderer: GeForce GTX 950/PCIe/SSE2 version: 4.6.0 NVIDIA 390.77 Direct Render: Yes Audio: Card-1 NVIDIA Device 0fba driver: snd_hda_intel bus-ID: 01:00.1 Card-2 Intel 9 Series Family HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 Sound: Advanced Linux Sound Architecture v: k4.15.0-39-generic Network: Card: Intel Ethernet Connection (2) I218-V driver: e1000e v: 3.2.6-k port: f040 bus-ID: 00:19.0 IF: eno1 state: up speed: 100 Mbps duplex: full mac: Drives: HDD Total Size: 1256.3GB (35.7% used) ID-1: /dev/sda model: MKNSSDRE256GB size: 256.1GB ID-2: /dev/sdb model: WDC_WD10EZEX size: 1000.2GB Partition: ID-1: / size: 219G used: 58G (28%) fs: ext4 dev: /dev/sda2 ID-2: swap-1 size: 17.11GB used: 0.00GB (0%) fs: swap dev: /dev/sda3 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 0.0:28C Fan Speeds (in rpm): cpu: 0 Info: Processes: 205 Uptime: 1 min Memory: 1102.1/15977.3MB Init: systemd runlevel: 5 Gcc sys: 7.3.0 Client: Shell (bash 4.4.191) inxi: 2.3.56 steve@steve ~ $ 

If your query has been resolved, edit your first post and add [SOLVED] to the subject line.
If you found a solution on your own please post it.
A generation which ignores history has no past and no future.

Источник

Why does virtualbox only have 32-bit option, no 64-bit option on Windows 7?

I have downloaded and installed the newest virtualbox 4.3.20 for my Windows 7 (64-bit OS) , but when I want to install 64-bit Linux , the New->Create Virtual Machine only displays 32-bit option, no 64-bit option. Could anyone give any clues about this issue? Thanks very much in advance!

To remedy this on my Win10 machine I needed to go into Control Panel\All Control Panel Items\Programs and Features and Turn Windows Features on or off. From here I needed to UNCHECK the Hyper-V feature that was installed. After rebooting the machine, the 64bit options were displayed

In addition to disabling the Hyper-V feature in the Windows features, I additionally had to go to the Task Manager and manually stop all running «Hyper-V . » services and the «HV Host Service» from the «Services» tab. After rebooting, the 64bit options were finally displayed.

7 Answers 7

If VirtualBox is only showing 32-bit versions in the Version list make sure:

• You have an x64 CPU installed. (Optimally, a 64-bit OS should also be installed to receive acceptable virtualization performance.)
• Hardware virtualization is enabled in the BIOS. (Your CPU must support it.)
  • For Intel x64: VT-x (Intel Virtualization Technology) and VT-d are both enabled
  • For AMD x64: AMD SVM (Secure Virtual Machine) is enabled

  @Tonny On top of this, as far as I remember, if you try to start something like XP Mode when you have VirtualBox VMs running, it will shut down your VirtualBox VMs abruptly without warning.

  Any technical reason as to why Hyper-V be disabled? I mean, Virtual box gives the option of 32 bit virtualization even when Hyper-v is enabled; so why not 64 bit?

  If you want to emulate 64 bit apps on a 64 bit host, your cpu needs a feature for that. Which duDE says, is an intel-specific copy-paste. The same support exists on AMDs too, there its name is AMD-v — maybe he forgot to mention.

  If your cpu doesn’t have this support, it won’t ever work. If it has, maybe you need to switch this on in your bios.

  There are bad BIOSes which can’t turn this feature on. Sometimes a BIOS upgrade can in this case help.

  Had the same problem, only seeing 32-bit versions for the host OS’s. Started working after updating asus p8z77-v pro bios to latest and enabling virtualization support. Before the bios update, virtubox showed only 32-bit OS’s.

  Windows 10 creators update needed a restart to show the 64 bit OS options in VirtualBox 5.1.22 for my AMD Phenom ™ II.

  Also, the problem might be that you need to TURN OFF the computer after changing the Virtualization options in BIOS, not just restart it.

  On Windows 1903 and Dell laptop, disabling Device Guard using group policy helped to enable 64 bit OS in VirtualBox.

  Using the guidance in the answer by @Leo Chapiro I was able to install Debian Buster 10 with Gnome on Windows 10 on a Lenovo ThinkPad. Here’s the step-by step way I enabled the 64 bit option in VirtualBox:

  • Restart PC and access BIOS with F1
  • Play with arrow keys and enter to access ‘Security > Virtualization’ section
  • Check the following options are enabled then F10 to save and exit:

  

  When Windows boots, windows key, type ‘Turn windows features on or off’, open it and disable HyperV:

  

  Open VirtualBox, it should now allow you to specify a 64bit version.

  (I followed this guide to install on VirtualBox)

  Источник