GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v86 seems to be stuck in initing a random non-blocking pool in a squashfs-based image.
Note how it is slower compared to ext4-based images.
Test instance with the test image
Checking further this seems to be v86 stuck waiting for the squashfs image.
I'm observing the same behaviour in QEMU. Can you verify that this image is supposed to be booted directly?
@copy can confirm this supposed to be booted directly. Might be a issue with how the squashfs was built?
Update: Tried a jffs2 image from the Attitiude Adjustment Release and it also has the same issue. Tried on QEMU/KVM this image should boot fine
Doesn't seem to work on qemu either. I'm running it as follows:
qemu-system-x86_64 -hda openwrt-x86-kvm_guest-combined-jffs2-128k.img -enable-kvm -m 512
The last line of the output is the same as on v86:
[ 0.463030] Waiting for root device /dev/mtdblock0...
I'll probably need to open a ticket about this on the OpenWRT mailing list, the ext4 images does work, however
Opened a tracker on OpenWRT Flyspray. Hopefully they can clarify why it doesn't work on QEMU (which also has a correlation to not work on v86)
Feel free to re-open if you find any other v86-specific issues.