Installation freezes at GRUB installation

[mishaor2005]

Hello! I have a problem with Android-x86-5.1-rc1 installation in VMware virtual machine. When I try to install GRUB, a installer will freezes.

--- Real computer ---
Computer:Compaq Presario CQ-57 383-SR
CPU:2 Cores Intel Pentium 4 B950 at 2.10 GHz
Memory:4 GB, but I have access only to 2 GB :(
GPU:Intergated Intel HD Graphics
OS:Windows 7
VMware version:Workstantion 10.0

--- Virtual machine ---
VM Name:Android x86
CPU:2 cores
Memory:1 GB
HDD:8 GB SATA

[Beau Steward]

I found this happens if I try to do the install directly on the drive without partitioning, and the solution was to create a GPT partition table and have at least one partition. I recommend 2 partitions, 1 smaller one (250mb should suffice) and the rest to another partition. Run the install on the second partition. When it asks to format the boot partition, it will point to the first partition. It should go past the grub install with this setup.

[Aaron Osborne]

Hello, The reason why you only have access to 2GB of ram is due to the fact that you have a 32 bit version of Windows 7. 32 bit versions only support up to 2GB, try upgrading to 64 bit to start using all of the avail ram.

[Drake x]

Having the same issue but using Virtual Box. 

Host Machine:

OS: Win 7 x64

RAM: 8GB

Using Virtual Box 5.0.10 (w/ extension pack installed)

VM OS: Linux 2.6/3.x/4.x (tried both x86 and x64)

VM RAM: 1GB

Enabled PAE/NX (Which host CPU supports)

Enabled VT-x (Which host CPU supports)

Enabled 3D Video Accel (Doesn't matter for problem)

What I've tried:

Situation #1

Set VM OS as Linux 2.6/3.x/4.x (x64) in Virtual Box
Run Android x86 5.1RC1, format virtual disk as ext4

Let LiveCD automatically do the formatting and partitioning (That is, not using cgdisk to manually set the partition tables)

Try to install GRUB

Result: Installer hangs at trying to install GRUB

Situation #2

Same as #1 except don't install GRUB or GRUB2 (don't think it's needed as this is a single OS VM)

Result: "Installs" and boots into Android x86. Upon trying to reboot the VM (without the Android x86 iso mounted) Virtual Box immediately throws the error: "FATAL: No bootable medium found! System halted."

Situation #3

Same as #1 except, follow Beau's suggestion below and use cgdisk to create two different partitions and write the partition table. Use LiveCD to format the large partition as ext4.

Try to install GRUB

Result: Same as #1

Situation #4

Same as #1 except skip GRUB and try to install GRUB2.

Result: Installer hangs at trying to install GRUB2

Situation #5

Set VM OS as Linux 2.6/3.x/4.x in Virtual Box
Run Android x86 5.1RC1, format virtual disk as ext4

Let LiveCD automatically do the formatting and partitioning (That is, not using cgdisk to manually set the partition tables)

Install GRUB but not GRUB2

Result: Same as #2

Situation #6

Same as #5 except install both GRUB and GRUB2.

Result: "Installs" but immediately fails to load into Android with error at command line (See attached screenshot)

I've had no problem before, I've set up many Android x86 4.4r2 VMs with no problems whatsoever.

Thanks very much for any suggestions. If I can provide any more information to assist or try other recommendations I'd be happy to do so.

[Chih-Wei Huang]

2015-12-03 15:02 GMT+08:00 Drake x <dr4...@gmail.com>:
> Having the same issue but using Virtual Box.
>
> Host Machine:
> OS: Win 7 x64
> RAM: 8GB
>
> Using Virtual Box 5.0.10 (w/ extension pack installed)
> VM OS: Linux 2.6/3.x/4.x (tried both x86 and x64)
> VM RAM: 1GB
> Enabled PAE/NX (Which host CPU supports)
> Enabled VT-x (Which host CPU supports)
> Enabled 3D Video Accel (Doesn't matter for problem)
>
> What I've tried:
>
> Situation #1
> Set VM OS as Linux 2.6/3.x/4.x (x64) in Virtual Box
> Run Android x86 5.1RC1, format virtual disk as ext4
> Let LiveCD automatically do the formatting and partitioning (That is, not
> using cgdisk to manually set the partition tables)

I'm not sure what you meant "automatically".
The install doesn't automatically do that for you.

Actually you NEED to partition (using cfdisk/cgdisk or any similar tool)
a new created virtual disk. At least one partition is necessary.
If you format the whole disk as ext4, it won't work.

> Try to install GRUB
> Result: Installer hangs at trying to install GRUB
>
> Situation #2
> Same as #1 except don't install GRUB or GRUB2 (don't think it's needed as
> this is a single OS VM)
> Result: "Installs" and boots into Android x86. Upon trying to reboot the VM
> (without the Android x86 iso mounted) Virtual Box immediately throws the
> error: "FATAL: No bootable medium found! System halted."

You need a bootloader - GRUB(2) or any similar stuff.
Otherwise it surely won't boot.
If you skip GRUB installation, you need to
install other bootloader yourself.

> Situation #3
> Same as #1 except, follow Beau's suggestion below and use cgdisk to create
> two different partitions and write the partition table. Use LiveCD to format
> the large partition as ext4.
> Try to install GRUB
> Result: Same as #1

Not sure if you have a typo.
cgdisk is for GPT partition table,
while GRUB only supports legacy partition.
You can't mixed them.

Use cfdisk instead.
(that is, say No to "Do you want to use GPT?")

> Situation #4
> Same as #1 except skip GRUB and try to install GRUB2.
> Result: Installer hangs at trying to install GRUB2

I believe the Virtual Box uses legacy BIOS by default.
So you should choose GRUB.

> Situation #5
> Set VM OS as Linux 2.6/3.x/4.x in Virtual Box
> Run Android x86 5.1RC1, format virtual disk as ext4
> Let LiveCD automatically do the formatting and partitioning (That is, not
> using cgdisk to manually set the partition tables)
> Install GRUB but not GRUB2
> Result: Same as #2
>
> Situation #6
> Same as #5 except install both GRUB and GRUB2.
> Result: "Installs" but immediately fails to load into Android with error at
> command line (See attached screenshot)

About GRUB or GRUB2, it depends on your BIOS.
For legacy BIOS, use GRUB. For UEFI BIOS, choose GRUB2.
(note the GRUB2 used in android-x86 supports EFI only.
The normal GRUB2 from a linux distro should support both)
Installing both doesn't make sense.

> I've had no problem before, I've set up many Android x86 4.4r2 VMs with no
> problems whatsoever.

Sounds very mysterious to me.
The installer doesn't have significant change
since 4.4-r2 to 5.1.
If you know how to do it before,
surely it should just work now.

> Thanks very much for any suggestions. If I can provide any more information
> to assist or try other recommendations I'd be happy to do so.

--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[Mike]

Not sure if I understood completely, But I was just working with a User
Yesterday (Matter Fact Had a Hell of a time getting my Wi-Fi Driver
back, Was doing testing, And was trying to recreate what I did before),
But I had Issues with the Install also, What I did, Was go into the
Installers options, and format the VDI, To ext changed the format to
85?!??! (The Linux EXT in the list) and it installed, but didn't boot
up, I ran into the Issue with the Wi-Fi Driver on my host and pretty
much aborted testing, 4 Hours Later got my Wi-fi back.... I Have heard
set Vbox to Windows install..

If I'm off, Sry, Just trying to help as I was just doing this yesterday
with the Latest Vbox and Additions.... I was trying to figure the
Bridged network connection, A year agi I had it Working, But as I said,
I googled and did stuff the messed MY main system trying to Recreate
what I did before....

Mike

[Михайло Оришич]

Oops...i need to upgrade Workstantion!

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, 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.