Android 5.1 rc1 virtualbox stuck on Splash screen

[Eric C]

Hello all, I was wondering what I was doing wrong installing 5.1-rc1 in Virtualbox on Windows. I get as far as the splash screen saying "android"

The release notes http://www.android-x86.org/releases/releasenote-5-1-rc1 says "Support VM including Qemu, VirtualBox and VMware"

Is this an ex-filesystem problem with virtualbox?

I will run the install option and format the disk (ext 3) and install the system and Grub boot loader. It will say that Android is installed and will give the option to run Android X86 or reboot. either option I choose I get
stuck on the Splash-screen.


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). Running it in vesa mode did not help, nor did running the live disk.

I'm presuming it isn't a problem with openGL, because older builds from this project work in virtualbox. If i am wrong though, what can I do to fix this?

Virtualbox Specs: 1024mb Ram
1 Cpu
32 bit linux 2.6/3X (OS type)

changing the chipset from ICH to Pix or checking hardware acceleration had no effect.

[Episteme PROMENEUR]

same pb for me

see

https://groups.google.com/forum/#!topic/android-x86/z7EDzuBg-NI

[rbg]

try installing on ext4 & add additional 1GB mem

5.1-rc1 disk installed....ext4 / 2GB memory min.

[pa...@cieniek.com]

This problem seems to be related to AMD hosts only. Tried same VBox image under Intel host (both Linux) and it works fine.

[Eric Clark]

I did up the ram to two gigs in Virtualbox, this did not work. I would be more interested in learning about Android's affliction with AMD processors. The windows machine I use, has an AMD processor. I did however get the 5.1 (32 bit) ISO to run on Ubuntu 14.04 (Trusty Tahr) on an Intel powered Dell laptop. 

the specs for the VM installation on Ubuntu were

Virtualbox 4.3.30 for Ubuntu with expansion pack (even though its useless for android x86). 

2 GB of Ram 

8 GB Hard drive 

32 MB video 

32 bit Linux 2.6/3X (same OS type I used for Virtualbox on Windows 

two processor cores 

using the same 32 bit 5.1 rc1 ISO file. 

I will have to try formatting the disk with ext 4 on the AMD windows host. 

How come the 4.4.4 rc3 ISO will boot on AMD hosts, but not the 5.1 rc1 ISO?  

 
On Saturday, October 10, 2015 at 4:19:00 PM UTC-4, Eric Clark wrote:

[pstglia]

Hi

Em sábado, 31 de outubro de 2015 14:05:49 UTC-2, Eric Clark escreveu:

I did up the ram to two gigs in Virtualbox, this did not work. I would be more interested in learning about Android's affliction with AMD processors. The windows machine I use, has an AMD processor. I did however get the 5.1 (32 bit) ISO to run on Ubuntu 14.04 (Trusty Tahr) on an Intel powered Dell laptop. 

the specs for the VM installation on Ubuntu were

Virtualbox 4.3.30 for Ubuntu with expansion pack (even though its useless for android x86). 

2 GB of Ram 

8 GB Hard drive 

32 MB video 

32 bit Linux 2.6/3X (same OS type I used for Virtualbox on Windows 

two processor cores 

using the same 32 bit 5.1 rc1 ISO file. 

I will have to try formatting the disk with ext 4 on the AMD windows host. 

Try using older Vbox release (4.2.x)

I also have an AMD machine (A10 5800K). I'm only able to boot Android-x86 iso (using hw virtualized) on this version. Newer versions gives me kernel panics during startup + reboot

Regards,

Pstglia

[Jeff Mezzanotte]

On Saturday, October 10, 2015 at 4:19:00 PM UTC-4, Eric Clark wrote:

I ran a console trace via ctrl+alt+F3 and the reason the that the boot loop occurs is that it is getting hung up on hardware verification in my case a mod probe for no existent Ethernet equipment specifically net-pf-16-proto-5 this tells me that it was something to do with ect/modprobe.d/Aliases either not being generated or not generating Aliases properly at install...Hope this helps

[Jeff Mezzanotte]

The only thing I can suggest is to run Linux live over your installation and repair the ect/modprobe.d/Aliases file.

--
You received this message because you are subscribed to a topic in the Google Groups "Android-x86" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-x86/vGn9jdtrc48/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-x86...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.