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 required video acceleration seems to be missing from vmware.
As a result you need to configure grub to start androïd in vesa mode.
This can be accomplished following a procedure described here with some mistakes or incompletness or a little outdated.
After the standard install, you need to
- On grub boot choice (white text on black background), keep first choice and type 'e'
After that, you can see existing boot commands in the boot sequence.
- Select the upper item and
- press e once more
To edit the boot command for GRUB, Use arrows to reach the right position
- replace the word "quiet" by "nomodeset xforcevesa", you should have:
kernel /android-?.?-r?/kernel nomodeset xforcevesa root=/dev/ram0
presse enter to save. then b to boot.
For the grub configuration to persist upon restart,
edit its configuration file:
mkdir /mnt/sda mount /dev/block/sda1 /mnt/sda vi
Press "i" to use insertion mode:
- replace the word "quiet" by "nomodeset xforcevesa",
escape to go back to command mode.
ZZ or :wq!
to save and quit
You now can restart your vm using your custom configuration.
If ever you wait too long without any action,
your screen might turn black, entering the sleep mode.
Use your keynoard's menu key to recover a usable screen.