Running a mobile operating system on a personal computer opens up great opportunities for application developers, testers and ordinary users who want to use Android games on the big screen. Virtualization allows you to isolate your environment without affecting the main system and safely experiment with different versions operating system. The most popular solution for emulation in this context is Oracle VM VirtualBox, due to its freeness and cross-platform.
Unlike heavy emulators like BlueStacks or NoxPlayer, installing “pure” Android on a virtual The machine gives full access to system settings and the file system. This method is often used for debugging APK files or testing the operation of software on different versions of Android without the need to have a physical device at hand.
The setup process requires attention to detail, especially when choosing virtual machine hardware parameters. Improper resource allocation can result in the system either not starting or running with critical delays. Below we will analyze in detail each stage, from downloading the image to the first boot of the desktop.
Preparing the system image and host machine
The first step is to select an Android distribution that is compatible with the x86 architecture, since standard images for ARM processors will not run on a regular PC without complex instruction emulation. The most stable and proven solution is considered to be the project Android-x86, which is regularly updated and supports a wide range of equipment. You need to go to the official website of the project and download the latest stable version in the format .iso.
Also make sure that virtualization technology is enabled on your computer. For processors Intel this function is called VT-x, and for AMD — AMD-V. Without enabling this option in the BIOS/UEFI, the virtual machine will generate errors when trying to start 64-bit systems or run extremely slowly.
⚠️ Attention: If you are using a laptop, check your power settings. In power saving mode, the processor can reset frequencies, which will critically affect the performance of the virtual machine. It is recommended to select the "High Performance" mode.
After downloading the image, check its integrity by checking the checksum, if one is provided by the developer. A damaged file when written can lead to unpredictable failures during installation, which are difficult for a beginner to diagnose.
To check the integrity of an image in Windows, use the command in PowerShell: Get-FileHash "path_to_file.iso" -Algorithm SHA256. Compare the resulting hash with what is indicated on the developer’s website.
Creating and setting up a virtual machine
Run VirtualBox and click the "Create" button to initialize the new machine. In the name field, enter any name that you understand, for example, "Android_Test". Select the operating system type Linux, and specify the version Other Linux (64-bit), even if you install Android, since the system kernel is based on Linux.
Pay special attention to the allocation of RAM. For comfortable operation of modern versions of Android (from 9.0 and higher), it is recommended to allocate at least 2048 MB, and preferably 4096 MB, if your host’s resources allow. The disadvantage RAM will lead to constant interface freezes and application crashes.
At the stage of creating a virtual hard disk, select the type VDI (VirtualBox Disk Image) and storage format Dynamic virtual hard disk. This will allow the image file to occupy on the real disk only the space that is actually used by the system, saving space.
- 🖥️ The minimum disk size should be 8 GB, but for installing Google Play and heavy games it is better to set 16-32 GB.
- ⚙️ In the "System" settings on the "Processor" tab, select at least 2 cores for stable operation of the interface.
- 📺 In the "Display" section, increase the video memory to the maximum (usually 128 MB) and enable 3D acceleration support.
☑️ Pre-launch settings
Configuring the media and downloading the installer
Before starting the machine, you need to connect the previously downloaded ISO image to the virtual drive. Go to the settings of the created machine, select the "Media" section and in the IDE controller click on the disk icon labeled "Empty".
In the menu that opens, select "Select disk file..." and specify the path to your image Android-x86. After confirmation, make sure that a disk icon with the name of your file appears in the device tree to the left of the controller name.
Now you can start the virtual machine. When you start, you will see the bootloader menu. Select item Installation - Install Android-x86 to harddisk. Do not select Live CD mode if your goal is to fully install the system on a virtual disk for permanent use.
⚠️ Attention: If a black screen with a blinking cursor appears during boot, try in the virtual machine settings in the "System" -> "Motherboard" section, uncheck the "PIIX3 chipset" item and select ICH9.
Sometimes the bootloader does not see the virtual disk. In such cases, switching the storage controller from IDE to SATA in the VirtualBox media settings before restarting the installation helps.
Disk layout and installation process
After selecting the keyboard layout language, you will be taken to the partition selection menu for installation. Most likely, the disk will not be partitioned, and you will need to create a new partition table. Select Create/Modify partitions.
In the utility that opens cfdisk select the partition table type GPT (for UEFI) or DOS (for Legacy BIOS), depending on which boot mode you configured earlier. Create a new primary partition using all available space, and be sure to mark it as Bootable.
After creating the partition, select it in the list and click Writeto save the changes to disk. Confirm the action by entering yes. Then exit the utility by selecting Quit.
| File system | Recommendation | Features |
|---|---|---|
ext4 |
Recommended | The most stable and fastest for Android |
ntfs |
Not recommended | There may be problems with access rights |
fat32 |
For compatibility only | Does not support files larger than 4 GB |
btrfs |
For advanced | Requires more resources, but more reliable |
Select a file system ext4 to format the created partition. Confirm formatting by agreeing to the warning about data loss (in this case, there is no data on the virtual disk yet).
What to do if the installation is interrupted at 90%?
Most often this is due to a writing error on the virtual disk. Try re-creating the virtual machine with a SATA controller type instead of IDE and go through the partitioning process again.
Installing the bootloader and configuring the system
After formatting, the installer will ask if you need to install the bootloader GRUB. Answer in the affirmative (“Yes”), otherwise the system will not be able to start after rebooting. This is a critically important step, skipping which will make the installation useless.
Next will be the question of installing the directory /system in read-write mode (read-write). It is recommended to agree, as this will allow you to install system updates, mods, or obtain root access without rebuilding the image in the future.
When asked about installing Android-x86 as the main system, you can answer negatively if you do not plan to use it as the only OS on physical gland. For a virtual machine, this is not decisive.
The final step will be to propose creating a boot image android-x86.img. Agree with this to ensure that the system initializes correctly at startup.
Successful installation of the GRUB boot loader ensures that the virtual machine can find the system kernel and start it after the power is turned off.
First launch and initial setup
After installation is complete, select item Run Android-x86 or reboot the virtual machine, remembering to first disable the ISO image in the media settings so that the system boots from the virtual hard disk.
The first launch may take several minutes, as the system optimizes applications and configures the user profile. You'll see the familiar Android welcome screen. Select a language, connect to a Wi-Fi network (VirtualBox emulates a network adapter, and the Internet should work out of the box via NAT).
When logging into your Google account, security verification may be difficult, since the virtual device has a unique identifier. If logging in fails, try skipping this step and setting up your account later through the settings menu.
- 📶 Make sure that the connection type is selected in the VirtualBox settings for network NATso that the virtual machine has access to the Internet.
- 🖱️ For convenient mouse control, install Guest Additions (if available for your version of Android) or use the right Ctrl keyboard capture mode.
- 📱 Screen resolution can be changed in the settings of the Android system itself or through ADB commands, if the standard does not suit you.
⚠️ Attention: Virtual machines do not have access to the hardware sensors of a real computer (GPS, accelerometer, camera) without special settings for device forwarding. Applications that require these sensors may not work correctly.
Solving common problems and optimization
One of the common problems is the lack of sound. In the virtual machine settings, go to the "Sound" section and make sure the audio interface is enabled. Try changing the sound controller to Intel HD Audio or AC97if the current one does not work.
If the system is running slowly, check if 3D acceleration is enabled in the "Display" section. Also make sure that the host machine is not running too many heavy applications that are competing for CPU resources.
To install applications that are not available on Google Play, you will need to enable installation from unknown sources in the Android security settings and drag APK file to the virtual machine window (Drag-n-Drop function only works after installing guest OS additions).
In some cases, the mouse may get “stuck” inside the virtual machine window. To release the cursor, use the host key, by default it is right Ctrl. If this does not help, check the input settings in the VirtualBox menu.
FAQ: Frequently asked questions
Can I play heavy 3D games on Android in VirtualBox?
Performance in 3D games will be significantly lower than on a real device or specialized emulators like BlueStacks. VirtualBox emulates the graphics card in software and OpenGL support is limited. For games, it is better to use specialized emulators.
How to get root access on a virtual machine?
In Android x86, root access is often enabled by default in debugging mode, or it can be activated through the bootloader settings at system startup (by selecting Debug mode). You can also use standard utilities like Magisk, if the system image allows it.
Why does the Internet not work in a virtual machine?
Check the adapter’s network settings in VirtualBox. The default mode should be NAT. If the Internet does not work, try switching the adapter to the “Bridged Adapter” so that the machine receives an IP address from your router directly.
Is it possible to update Android-x86 to a new version?
There is usually no direct update over the air (OTA) for Android-x86 images. To upgrade to the new version, you need to download a fresh ISO image and perform a clean installation, having previously saved important data from the virtual disk.
How to change the screen resolution in Android on VirtualBox?
The resolution often adjusts automatically to the window size. If this does not happen, you can use the ADB commands: adb shell wm size 1920x1080. To reset, use the command adb shell wm size reset.