Found the solution!
You have to edit menu.lst file. Here is how:
boot in debug mode (usually the second option in boot menu)
when booting stops (for me it just hangs there with flashing cursor and without any prompt) enter mount -o remount,rw /mnt
enter cd /mnt/grub
enter vi menu.lst
right under the first boot entry find the line starting ...
I'd like to extend and improve @Jay Smith answer based on personal experience.
He is right in the core thing that the cause of the issue is VGA resolution used by Android, but he is wrong in his assumption it is disposable fix and should be typed at each boot.
It can be made persistent, and should be! And I show you how:)
First of all, install the Android ...
This does not seem to possible, I have looked for it for years and found nothing. This is probably because these points:
Android devices have a tiny amount of ram, which cannot be extended. With just 3 GB of RAM, you can forget to run pretty much any VM, as any normal OS needs at least 4 GB by now. A typical PC has 8 GB by now, or even 16. Virtualization is ...
You need to follow the instructions. Specifically:
You have to change your virtual disk type to be IDE because the default type in VMware is SCSI, and [the] Android-x86 kernel is not configured to support SCSI. You can follow these steps:
Create a virtual machine.
Edit [the] virtual machine settings after the virtual machine [is] created.
Choose the hard ...
At first I had the same issue. But I changed the Display settings and now it works.
Go to the VM settings's
Go to Display settings
Check the Accelerate 3D graphics
Set the graphics memory to 1GB (if possible)
Start your VM!
I also had problems with Android x86 vitual box on a Windows 7 Pro x64 AMD machine. I suppose we are all going to have slightly different issues depending on our architecture/hardware but they all seem to be similiar root causes. I think more emphasis should be on the architecture/hardware then the host OS. Try 32bit without/with EFI set in System, leave ...
Some progress here, but not the real thing. The following allowed me to boot Android x86 6.0 under VirtualBox correctly - but only once:
1) When booting the installation image, the initial screen gives you four options. Move the cursor to the last one: Installation - Install Android-x86 to harddisk".
2) Press the [Tab] key for edit options.
3) Immediately ...
Select "Yes" when it asks "Do you want to install boot loader GRUB".
Now you can boot into Android. (Works even rebooted)
Here is a YouTube video showing how to set VESA mode in Grub.
My other post was deleted for some reason, but if you want to find out if VESA/VIDEO is the reason your gui isn't coming up after install, then boot from the Android x86 ISO and select VESA mode (Live boot) and if you get a gui, then check out that ...
On windows, installing the recommended iso for vmware (android-x86_64-9.0-r2-k49.iso) let you stuck at command prompt.
And if you try the debug startup, you might get stucked with a confusing message
random: 7 urandom warning(s) missed due to ratelimiting
Since the live boot vesa start mode works, the urandom error is not the problem.
Rather, the ...
I've been able to run it in Windows 8.1 Pro within VM Ware 10. This was when I was used ADT though for eclipse. When I switched over to Android Studio I haven't been able to get a AVM to start yet. Granted I've spent about 30 minutes working on it, so I haven't exhausted all options just yet.
I imagine speed will always be an issue though. While the ...