I'm presuming it isn't a problem with openGL, because older builds from this project work in virtualbox. Running it in vesa mode did not help, nor did running the live disk. Older posts say that 5.1 was an experiential build, but now that I downloaded the generic release, it should work? (it also lists VMs as supported in the release notes). It will say that Android is installed and will give the option to run Android X86 or reboot. I will run the install option and format the disk (ext 3) and install the system and Grub boot loader.

Is this an ex-filesystem problem with virtualbox? The release notes says 'Support VM including Qemu, VirtualBox and VMware' I get as far as the splash screen saying 'android'

Attachments log.zip Log from VM that crashed (18.88 KiB) Downloaded 14 times innarion Posts: 2 Joined: 11.Hello all, I was wondering what I was doing wrong installing 5.1-rc1 in Virtualbox on Windows. As I said before, with VirtualBox 5.1.34 and some previous versions Android x86 worked perfectly. I don't really understand what is going on in it.Īll the VMs had 2 GB of RAM, 128 MB of video RAM, 4 CPUs (Intel i7) and 3D acceleration enabled. I attach a log of one of the VMs that crashed like this. This behavior is observed at all my Android x86 machines (all 64bit, I mostly use Android 6.0 and 7.0).

No matter if I start the machine normally or use a snapshot, no matter if I turn on an old machine or make a new one, it always boots and after a few seconds the window closes and the state of the machine in the menu is Aborted. Together with the system update, VirtualBox updated to 5.2.10_Ubuntu r121806 (I had 5.1.34 before) and my VMs (I only have various versions of Android x86) started crashing. Hi, I know Android x86 is not officially supported by VirtualBox, but until recently it worked just fine.Ī few days ago I updated my Ubuntu Mate from 17 to 18.04 LTSĬode: Select all Expand view Collapse view lsb_release -a

Virtualbox android x86 5.1 freeze