If it is set to off, then VMX support will be enabled. When the Chrome OS kernel boots up, it will look for the disablevmx= option on the kernel command line. Otherwise, they'd have to resort to modifying the firmware and that's always a tricky proposition (make a mistake and you have a brick). This keeps things secure during initial boot, but doesn't lock out people from enabling things themselves in the kernel. This means that support is disabled, but it is not locked such that runtime cannot change things. The firmware on Chrome OS devices will clear the VMX bits during boot. What we'd most prefer is to get this patch series into Chrome OS, so we have qemu as part of a 'real' build.įWIW, this particular instance of qemu was built on arch Linux, lost, sadly, when my Air was stolen. The setup sounds a bit kludgy but works well for me nevertheless, we welcome improvements. Access to devices, where needed, is provided via bind-mounts. It's a bit hard to get Qemu built in the Chrome OS build system at present, so I've got a directory containing Qemu, its libraries and BIOS files, and scripts to chroot to that directory and run Qemu. I have booted both Windows and different versions of Linux and the 9front version of Plan 9.

I've replaced my Macbook Air with a Chromebook, and run the standard Chrome OS software on VT01, and virtual machines on VT02. The Chromebooks with Intel processors are fast.

4 Checking VMX Support on Unofficial Hardware.

Chrome os emulator mac