init: execv(“/system/bin/init”) failed / No such file or directory / cyclic reboots while trying to virtualize android on my jetson nano
Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
init: execv(“/system/bin/init”) failed / No such file or directory / cyclic reboots while trying to virtualize android on my jetson nano
Hello.
I want to virtualize correctly Android 10 on top of my Jetson nano (arm64) using qemu and kvm on ubuntu 18.04. This is the tutorial that I'm following :
Unfortunately it ends with an error that it is a bug. It does not depend on my poor knowledge,even if I have it. There is another user on the nvidia forum that ended the tutorial with the same error. You can see the full log here :
I have compiled the Android files "system-rw.img" and "Image" and "following the instructions on the github and the other files that I have used (cache.img ; userdata.img ; ramdisk.img) are provided by the repo (no need to compile them). I've compiled everything on my Ubuntu 20.10 os. On my jetson nano is running with :
Someone said to me : As you can see, it tries to boot the system by using the "fstab method". it maybe should be in the /system/etc/fstab. You have to populate the fstab correctly. Any help to understand how to do that ?
init: execv(“/system/bin/init”) failed / No such file or directory
is logged by the init running in your initrd when it tries to start the init in your actual user space. It can't find that file. Unfortunately, there are a lot of things that can go wrong during boot.
Loop mount the root filesystem and verify that /system/bin/init is present, readable and executable. It has to be in the root filesystem, since fstab hasn't run yet and mounted the other filesystems.
You could also unpack the initrd and look at init, which is likely a shell script or program that should load any needed modules, mount the new root filesystem and pivot to it. The last thing it does is the exec of the new init found on the new root (which fails).
Another possibility is an error in the kernel command line.
Forget the old error. I've followed the part 2 of the tutorial and this time the error has been different :
Quote:
[ 1.074939] EXT4-fs (vda): couldn't mount RDWR because of unsupported optional features (4000)
[ 1.078049] init: [libfs_mgr]__mount(source=/dev/block/vda,target=/system,type=ext4)=-1: Invalid argument
[ 1.081515] init: Failed to mount /system: Invalid argument
[ 1.084120] init: Failed to mount required partitions early ...
[ 1.096129] init: #00 pc 00000000000e90a0 /init
[ 1.097856] init: #01 pc 000000000006c4d8 /init
[ 1.099631] init: #02 pc 000000000006e930 /init
good. So,I should modify the right python script which build the system.img file. Anyway I don't know which is the right one. BTW I copied all the python files that have been used to build the android images on my google drive,here :
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.