Install Chrome OS in VMware: Step-by-Step Guide

This guide walks you through installing Chrome OS (the open-source Chromium OS build) inside a VMware virtual machine, letting you test Google’s lightweight operating system on your existing hardware without wiping your main drive. You’ll need a VMware product (Workstation Pro, Workstation Player, or Fusion), a Chromium OS image file, and about 30 minutes of setup time.

What You’ll Need

A computer running VMware Workstation Pro, Workstation Player, or Fusion (version 15 or newer recommended).
A Chromium OS disk image (IMG or BIN file) from a trusted open-source build like ArnoldTheBat or Neverware’s CloudReady (now Flex) — these are the most common community builds.
At least 8 GB of free disk space on your host machine for the virtual disk.
At least 4 GB of RAM available to allocate to the VM (2 GB minimum works, but 4 GB is smoother).
Basic familiarity with VMware’s New Virtual Machine wizard.

Step-by-Step

Download a Chromium OS image. Go to the build provider’s site (e.g., ArnoldTheBat.com or Neverware’s download page) and grab the latest stable 64-bit image. The file will be a large .bin or .img file, typically 1–3 GB. Save it to a folder you can easily find.
Open VMware and start the New Virtual Machine wizard. In Workstation Pro or Player, click File → New Virtual Machine. In Fusion, click File → New.
Choose the installation method. Select I will install the operating system later (not the “Installer disc image” option, because Chromium OS isn’t a standard installer). This lets you customize the VM before booting.
Select the guest operating system. Pick Linux as the guest OS type, and then choose Other Linux 5.x kernel 64-bit or Other Linux 4.x kernel 64-bit depending on your build. If that exact option isn’t available, any 64-bit Linux option will work.
Name the VM and set the disk size. Give it a name like “Chrome OS Test”. In the disk size step, choose at least 16 GB (the default is usually 20 GB). Select Store virtual disk as a single file for better performance.
Finish the wizard, then edit VM settings. Before powering on, click Edit virtual machine settings. Under Memory, set at least 2048 MB (4096 MB recommended). Under Processors, give it 2 cores if your host has them.
Add a second SATA disk for the Chromium OS image. In the settings, click Add (Workstation/Fusion) → Hard Disk → SATA → Use an existing virtual disk. Browse to the .img or .bin file you downloaded. If VMware complains about the format, choose “Keep existing format” and select OK.
Connect the second disk as a CD/DVD drive (alternative method). If the above doesn’t work, remove the second hard disk and instead add a CD/DVD drive → Use ISO image and point it to your .bin file. This is a common workaround because VMware can read .bin as an ISO.
Boot the VM. Power on the virtual machine. You’ll see a boot menu. If you used the hard disk method, select the second disk (usually “SATA Port 2”) as the boot device. If you used the CD/DVD method, it should boot automatically from the image.
Wait for Chromium OS to boot. The first boot can take 2–5 minutes. You’ll eventually see the Chrome logo and then the setup screen. Choose your language, network, and sign in with a Google account (or click “Browse as guest” to skip).
Install to the virtual disk (optional). After booting from the live image, you can press Ctrl+Alt+T to open a terminal and type install to run the installer. Follow the prompts to install to the first virtual disk (the 16 GB one). This makes the OS persistent, so your changes save between reboots.
Reboot and remove the image disk. Once installed, shut down the VM, remove the second disk or CD/DVD drive from settings, and boot again. Chrome OS will now run from the virtual hard disk.

Common Mistakes

Choosing the wrong guest OS type. Selecting “Chrome OS” in the guest OS dropdown (if available) can cause boot issues. Always use Linux 64-bit.
Using the image as the primary disk. If you set the .img file as the first SATA disk, the VM won’t boot because it’s not a standard virtual disk format. It must be a secondary disk or a CD/DVD.
Not enabling virtualization in BIOS. If your host CPU has virtualization disabled, the VM will be extremely slow or fail to start. Check your BIOS settings.
Insufficient RAM. Giving the VM less than 2 GB can cause Chrome OS to crash or freeze during setup.
Forgetting to remove the image after installation. If you leave the .img attached, the VM may try to boot from it again instead of the installed disk.

Tips

Use a 64-bit Chromium OS build for better performance and compatibility with modern hardware.
Enable 3D acceleration in VM settings (under Display) to get smoother graphics in the Chrome browser.
Allocate at least 4 GB of RAM and 2 processor cores for a responsive experience.
Take a snapshot of the VM right after a clean install. That way, if you break something, you can revert instantly.
If you’re only testing, skip the installation step and just run the live image — it works fine for casual browsing.
Keep the Chromium OS build updated by downloading new images periodically; the open-source builds don’t auto-update reliably.

Troubleshooting

VM won’t boot from the image. Double-check that the image file is attached as a secondary SATA disk or CD/DVD. In the VM’s BIOS (press F2 during boot), ensure the boot order tries the correct device. Also verify the image file isn’t corrupted — redownload it if necessary.
Black screen after boot. This often means the graphics driver isn’t compatible. In VM settings, try disabling 3D acceleration, or switch the display to “VGA” mode. Also make sure you allocated enough RAM (2 GB minimum).
Keyboard or mouse not working. Click inside the VM window to capture input. If the mouse is stuck, press Ctrl+Alt to release it. In VMware, go to Edit → Preferences → Input and ensure “Grab keyboard and mouse on click” is enabled.
Chrome OS is extremely slow. Increase the VM’s RAM to 4 GB and give it 2–4 CPU cores. Also make sure your host has enough free resources. Disable any background processes on the host.
Cannot install to the virtual disk. The installation command might be install or chromeos-install depending on the build. If it fails, check that the first virtual disk is at least 8 GB and that you’re running the command as root (type sudo -i first).
No Wi-Fi in the VM. VMware’s virtual network adapter should work, but if not, try switching the network adapter type from NAT to Bridged in VM settings. Also check that the Chromium OS build includes the necessary drivers.

Frequently Asked Questions

Is Chrome OS the same as Chromium OS?

No. Chrome OS is Google’s official commercial version with proprietary codecs and automatic updates. Chromium OS is the open-source base that anyone can build. VMware runs Chromium OS builds, not the official Chrome OS.

Can I install the official Chrome OS in VMware?

No. Google does not distribute Chrome OS images for general use. Only Chromium OS builds are freely available. The experience is very similar, but you won’t get Google’s automatic updates or some proprietary media codecs.

Will Android apps work in the VM?

Most Chromium OS builds do not include the Android subsystem. The official Chrome OS on Chromebooks supports Android apps, but the open-source builds for VMware typically don’t. You’ll be limited to web apps and Linux (Crostini) if enabled.

How much disk space does the VM use?

The virtual disk is set to a fixed size (e.g., 16 GB), but it only consumes as much space as is actually used on your host. A fresh install with a few apps might use 4–6 GB.

Can I use a USB drive or external device in the VM?

Yes. In VMware, go to VM → Removable Devices and connect your USB device. The Chromium OS build should detect it, but compatibility may vary depending on the build’s drivers.

Is it safe to run Chrome OS in a VM?

Yes, it’s isolated from your host system. The VM acts as a sandbox, so any malware or crashes inside Chrome OS won’t affect your main operating system. Just make sure you download the image from a reputable source.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →