Android KitKat Won't Install, Restarts

[Daiwuff]

So I've created my drive and attempted to boot off of the ISO I just downloaded (android-x86-4.3-20130725.iso). It boots initially and I get to the first selection screen where I can select to install the OS, I do so, and the machine just restarts and returns to the same screen again. It does this if I try to run it as a Live CD live as well.

This problem is especially bizarre to me, as minutes earlier I JUST installed from the exact same ISO on my laptop. It installed, booted, and ran perfectly fine. However after realizing my laptop doesn't quite have the resources to accommodate the VM, I decided to install it on my PC... NOTE: I used the SAME iso, the SAME version (newest, 5.0) of Virtual Box, and both laptop and PC are running Win 8.1. I followed all the same steps and used all the same settings for the virtual drive, and I even compared the settings in VB and everything is the same... what the heck?!

I even copied over the virtual drive with Android installed from my laptop to my PC, and attempted to start it and the boot selection screen comes up as normal, I press enter to run the OS, and still the same problem- it just restarts back to the same screen.

Any idea as to what is different about my PC from my laptop that would cause this? I can run other VM's just fine on my PC, I have a Win7 and Linux OS which still boot perfectly fine.

[BillG]

That usually indicates that the ISO file is still assigned to the drive in the vm, so it boots from that. Releasing the ISO file should fix it.

[dlharper]

That usually indicates that the ISO file is still assigned to the drive in the vm, so it boots from that. Releasing the ISO file should fix it.

I do not think that can be OP's problem, since he is talking about two separate physical machines (assuming that "SAME iso" means he has a copy of the same file on each machine).

If all their settings are the same, then almost all aspects of two VMs on different machines will appear identical, but there are one or two ways that differences can show up. One is CPU speed. This shouldn't make any diffeence, but occasionally it can lead to race conditions where two processes complete in a different order. Another is the network, because if one machine is on WiFi and the other is wired then VBox handles them slightly differently.

This doesn't give any solutions, I'm afraid, but might help explain how what you are finding is possible. It might be worth reducing the Execution Cap on the desktop VM, but that is only a suggestion of something to try out.

[Ramshankar]

Please post VBox.log for the working VM and for the VM where you say it doesn't work. At the very least, we would need the VBox.log for the VM where it doesn't work as expected.

[Daiwuff]

I do not think that can be OP's problem, since he is talking about two separate physical machines (assuming that "SAME iso" means he has a copy of the same file on each machine).

If all their settings are the same, then almost all aspects of two VMs on different machines will appear identical, but there are one or two ways that differences can show up. One is CPU speed. This shouldn't make any diffeence, but occasionally it can lead to race conditions where two processes complete in a different order. Another is the network, because if one machine is on WiFi and the other is wired then VBox handles them slightly differently.

This doesn't give any solutions, I'm afraid, but might help explain how what you are finding is possible. It might be worth reducing the Execution Cap on the desktop VM, but that is only a suggestion of something to try out.

WELL, it seems I've solved my own problem... figures! After you mentioned lowering the execution cap, I noticed my PC has the Acceleration tab available after it, while my laptop does not. So I un-ticked Hardware Virtualization, and it works now! How funny.

Thank you for the indirect solution.