• I am running a Linux Mint 17.03 Host, 64 bit, and am trying to set up multiple 64 bit guests. When I attempt the startup, I am only given the option for 32 bit guests. I went into the BIOS and Security, it seems that virtualization is enabled.
• Virtualbox 32 Bit - downyup. VirtualBox for Windows 7 - original software that allows you to experiment with operating systems. Creates a virtual machine, allows you to set iron parameters within certain limits. The advantage is the modular architecture and the presence of internal logic. Suitable for users with an average level of skills.
• I am running a Linux Mint 17.03 Host, 64 bit, and am trying to set up multiple 64 bit guests. When I attempt the startup, I am only given the option for 32 bit guests. I went into the BIOS and Security, it seems that virtualization is enabled.
• Virtualbox guest complains system is only 32 bit. Log in to get rid of this advertisement I'm trying to use VirtualBox on a 64 bit host (Fedora 12), and install a 64 bit suse guest. I have VirtualBox installed just fine on the host, but when I try to launch the guest (booting from an iso) I get the message 'This is a 32-bit computer.

Jun 10, 2016 I am running a Linux Mint 17.03 Host, 64 bit, and am trying to set up multiple 64 bit guests. When I attempt the startup, I am only given the option for 32 bit guests. I went into the BIOS and Security, it seems that virtualization is enabled.

Run Android on your PC

VirtualBox How To

The following are instructions on how to run Android-x86 inside VirtualBox.
Note: For optimal performance, make sure you have enabled either VT-x or AMD-V in your host operating system's BIOS.
Android-x86 versions tested against Virtualbox versions.

Date Tested	Virtualbox	Host OS	Android-x86	Result
??	2.2.4	Windows XP	??	Good
??	3.0.2	Fedora 11	??	Good
Nov. 2 2017	5.2.0	Windows 10	6.0-r3 32/64 bit	Good

Downloading

Download an ISO of Android-x86 from here.

Caution

If you are using Android-x86 for debugging purposes, some binaries (gdb for example) are built for 32-bit architectures and will not support debugging 64-bit binaries such as the Android app host. Download a 32-bit distribution instead.

Create a new VM

If you have not already created a VirtualBox virtual machine for Android-x86 yet, do so as follows:

1. Click the 'New' button, and name your new virtual machine however you like. Set Type to Linux, and Version to Linux 2.6 / 3.x / 4.x. Note that you should choose the appropriate bit type for the version of Android-x86 that you downloaded.
2. Specify how much RAM will be allocated to your virtual machine when you run it. Android doesn't specify a bare-minimum requirement for memory, just keep in mind what apps you plan on running. 2GB (2048MB) is a good place to start, and you can change this later if you need to.
3. Create a new Hard disk image which will act as your machine's storage. The recommended starting size of 8GB is enough. Click through the rest of the options for creating your Hard disk.

Your virtual machine has now been created. It still needs to be initially installed at this point.

Settings

Tested on VirtualBox 64-bit for Windows, version 5.2.0. Android-x86 version 6.0-r3, both 32-bit and 64-bit.
Select your machine, then click the Settings button and refer to the below recommended configuration to make sure your settings match.

• [System]Recommended: Processor(s) should be set above 1 if you have more than one virtual processor in your host system. Failure to do so means every single app (like Google Chrome) might crush if you try to use it.
• [Display]:
  1. Optional: Video Memory may be increased beyond the minimum selected automatically. The affects of this are unknown.
  2. Mandatory: Unless guest additions are installed^[1], change the default VMSVGA to VBoxVGA.
  3. Optional: Enable 3D Acceleration may be checked. The Linux Guest Additions must (VirtualBox v6.1+) / may (VirtualBox v6.0 and below) need to be installed^[2][1] to get any benefit from this.
  Failure to do so means you won't even be able to launch Android-X86 in the first place.^[3]
• [Storage] Find the first 'Empty' item (this should have an icon of a CD). In the Attributes, click on the CD icon with a small down arrow, and pick 'Choose Optical Virtual Disk File...'. Specify the Android-x86 ISO that you downloaded.
• [Audio] Intel HD Audio seems to be natively supported in Android-x86.
• [Network] By default, your installation of Android-x86 will be able to automatically connect to the internet. If not, you can try to enable WiFi in Settings/Network & Internet, and connect to showing VirtWifi. If you do not want to connect to the internet in VirtualBox, uncheck Enable Network Adapter under the Adapter 1 tab.

Install

Click the green Start arrow to power-on your virtual machine. You'll be presented with a list of options. Use the arrow keys to pick which one you want, then press Enter once the one you want is selected.

1. If you don't want to install Android-x86 yet and just want to test it, pick one of the Live CD options (except for Debug mode).
2. Pick the Installation option if you want your system to be installed to the virtual hard drive.

If you want to use higher resolution, you can edit the boot option by pressing TAB, change vga=788 (800x600) to vga=791 (1024x768) or vga=794 (1280x1024), and press Enter. You can also use vga=ask to see all available modes. But please note Android will only work under 16-bit mode.

Partition

When you are prompted to Choose a partition:

1. If you upgrade Android-x86 from a previous version, just select the existing partition. Agree to overwrite it when prompted.
2. If this is a new VM, choose to Create/Modify partitions. Use Bootable but not GPT! This will cause the GRUB installation to fail later.

You may partition your disk however you see fit. If you just want a simple installation, create one partition taking up the entire disk and format it as ext4.

Continue through the installation. You should install GRUB when it prompts you to. You may also leave /system as read and write when prompted.
Once the installation is complete, force close/shut down the virtual machine and remove the ISO from the virtual CD drive.
Finaly, start Android-x86. If it's a new machine, once loaded you can perform the Android setup to begin using your machine.

Advanced

Custom partitions, SDCard

When booting Android-x86, you may specify which partitions represent the data and sdcard. On the boot menu, select an entry you would like to boot from, press TAB, then add the following as it suits your needs:
DATA=sda1 SDCARD=sda2 Press Enter to boot. These options specify user data (your setting, your uploaded applications, ...) go into /dev/sda1, and data saved in sdcard go into /dev/sda2.
If you build the ISO from source, you can add these options to bootable/newinstaller/boot/isolinux/isolinux.cfg.
Here is a note from David when using fdisk:

1. Create a new virtual machine with a hard disk.
2. Launch the Live ISO in Debug mode (I used android-x86-2.2-generic.iso) to get the commend prompt.
3. 'fdisk /dev/sda', then type:
   1. 'n' (new partition)
   2. 'p' (primary partition)
   3. '1' (1st partition)
   4. '1' (first cylinder)
   5. 'xx' (choose the last cylinder, leaving room for a 2nd partition)
   6. 'w' (write the partition)
4. Repeat #3, but call it partition 2, and use the remaining cylinders.
5. 'mdev -s'
6. 'mke2fs -j -L DATA /dev/sda1'
7. 'mke2fs -j -L SDCARD /dev/sda2'
8. Reboot ('reboot -f')
9. At the boot menu, choose VESA, then hit TAB and type so that the end of the line reads: 'DATA=sda1 SDCARD=sda2'. (Only need for the generic target images, for VM target images, this is not needed)
10. After booting (and of course disabling mouse integration via the machine menu), the SD card is read as unformatted, but you can format it by going to Settings > SD card & phone settings > Format SD Card, then Mount SD card.
11. The SD card should now work!

Note: for the step 7, if you want to format to vfat only, then you can do : Also remember the partition type has to be fat32 (b or c). By using vfat, the step 10 is not needed.
DevTools application has a MediaScanner which (re)indexes your SD card for cases where you manually copied media over. This ensures that you see new images and/or music in the apps without having to reboot.
If you downloaded it from within android, the application asks the relevant service to index new files.

Playing music

This section describes two ways to upload music files into Android running on a vbox so you can play them by the Music app. Of course, you can save the files to the virtual disk mounted at /sdcard, as described above.

Upload files by adb

Adb is Android Debug Bridge, a tool to debug Android system. If you compile from source, it is located in out/host/linux-x86/bin/adb. Otherwise you can get it from Android SDK. Suppose the network of your vbox is OK, you can upload a file from your host by

You need to know the ip of your vbox. You can get it by Alt-F1 and netcfg. You may also need to reboot Android to see the uploaded files. Of course in this way you have to mount /sdcard to a virtual disk partion.
For complex network settings of the VirtualBox VM, you should refer to Debug How To on how to connect adb to the VM.

Upload files by wget

You can also upload files by wget in the debug mode. In the debug mode shell, before entering Android,

Then type exit to enter Android.

Debug with adb

This section describes the way to debug Android with adb via network.

If we want to debug with adb via network, we should ensure the ip of vbox can be accessed by host machine. So we should change the Network Adapter type of vbox to Bridged Adapter. After starting the android-x86, we should follow the above Settings/[Network] section to ensure the network of android-x86 is enabled, and enable USB debugging in Settings/System/Developer Options. Then we can get the device ip from Settings/System/About tablet/IP address. For example, if we see the ip address is 192.168.0.116, then we can use following command to connect android-x86 in vbox from host machine.

Then you can use adb command to debug android-x86 such as get log, and dump system information.

References

1. ^{^ ab} VirtualBox currently has no Guest Additions for Android.
2. ^{^} VirtualBox v6.1.0 states: 'old style 3D support (with VBoxVGA) has been completely removed'
3. ^{^} VirtualBox states: 'Note that you must install the Guest Additions on the guest VM to specify the VBoxSVGA or VMSVGA graphics controller.'

This tutorial will show you step by step what to do when VirtualBox is only showing 32-bit and no 64-bit versions of operating systems as options while creating a new virtual machine.

Note: This may be obvious for most of you, but your host operating system should be 64-bit to run 64-bit guest operating systems in VirtualBox.

If VirtualBox has no 64-bit option on Windows 10, then you can try the solutions on this page to fix the problem.

Methods:

My experience with this problem

I experienced the same problem while trying to install a 64-bit version of Linux Mint inside VirtualBox.

I opened VirtualBox, clicked on NEW, entered a name for the virtual machine, choose the type of operating system, but when I wanted to choose a version, I only saw 32-bit versions and NO 64-bit versions as an option.

But:

Fortunately, I found a simple solution online and on this page, I will share that solution with you.

Note! Your host operating system (OS installed on your PC) must be 64-bit.

I was using a 64-bit version of Microsoft Windows 10 Pro while creating this tutorial.

Make sure that “Intel Virtualization Technology” and “VT-d” are enabled

Enter BIOS settings and check if “Intel Virtualization Technology” and “VT-d” are enabled.

The following steps may be slightly different on your computer.

1. Start (or restart) your PC.

2. Press the right keyboard key to enter the BIOS setup. This must be done before Windows starts, so it's best to press the key a few times directly after you start your PC.

The exact key or key combination depends on your computer manufacturer and model.

Common keys to enter the BIOS are F1, F2, F10, DEL, and ESC.

3. Look for the following settings Intel Virtualization Technology and VT-d.

4. Make sure that they're both enabled.

5. If you made changes, then you must save the settings.

Windows 10 (host) must be a 64-bit operating system

To check if your Windows 10 is a 64-bit operating system, press the [Windows] + [pause] keyboard keys.

At System type (located under System), you should see something like 64-bit Operating System, x64-based processor.

Hyper-V must be disabled

Hyper-V is Microsoft's hardware virtualization product.

It lets you create and run virtual machines (like VirtualBox).

But:

Many third-party virtualization applications (including VirtualBox) do not work together with Hyper-V.

That's why you must make sure that Hyper-V is disabled.

To check if Hyper-V is disabled, follow the following steps:

1. Right-click on the Windows start menu button.

2. Click on Run.

3. Enter optionalfeatures.exe in the Run window.

4. Click on OK or press Enter.

The Windows Features window will appear.

5. Check if the Hyper-V option is unchecked.

6. If the Hyper-V option unchecked (like in the screenshot above), then you can close the Windows Features window.

But:

If the option is checked, then you will need to uncheck it and then click on OK.

If you want to be 100% sure that Hyper-v is disabled then follow these steps:

1. Right-click on the Windows start menu button.

2. Click on Command Prompt (Admin).

3. Enter the following command:

4. Press Enter.

5. After the command is finished, you will need to power down and reboot your PC.

Solution 1: Repair VirtualBox installation

1. Right-click on the installer file (the one you used to install VirtualBox) and choose Run as administrator.

If you don't have the installer file anymore, then you will need to download it from the VirtualBox website (www.virtualbox.org). The installer file must be the same version as the version of VirtualBox that's installed on your computer.

2. When the Windows User Account Control window appears, you click Yes.

Note: You might need to enter an administrator password in the User Account Control window and then click Yes.

A setup window will appear.

3. Click on Next.

4. Click on the Repair icon.

5. Click on Repair located at the bottom right.

VirtualBox will now start the repairing process. This will only take a few seconds.

Virtualbox 64 Bit Os

6. After the repair process is finished, you click on Finish.

VirtualBox may ask you to restart your PC.

Hopefully, this simple solution will solve your problem.

Solution 2: Disable “Memory integrity” in Windows 10

1. Open Windows Security.

2. Click on Device security.

3. Under Core isolation, you click on Core isolation details.

4. Make sure that Memory integrity is turned off.

Virtualbox For Linux 32 Bit

If Memory integrity was enabled and you just disabled it, then you may need to restart your PC.

Hopefully, this simple solution will solve your problem.

Virtualbox.org • View Topic - I Can't Run 32-bit Virtual Machines

☕ Buy me a coffee

Download (M - 0.6 GB / G - 2.1 GB)

Maybe you're also interested in: