-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
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
qemu-user-i386 error #6141
Comments
I've just tested these binaries on armv7l device and it seems like QEMU is working fine:
I will not do tests "distribution-wide", considering as QEMU user mode is usually less stable that system variant and v5.2.0 upstream can have regressions. Emulation errors are not subject for debugging & fixing by me. Complexity of QEMU's Tiny Code Generator is quite beyond my skills. Reverting to previous version will not be done as well. Closing. |
This comment has been minimized.
This comment has been minimized.
Downloaded packages are kept in
They are no longer stored in $PREFIX to be preserved when
@SDRausty Don't get me wrong, but I only pointed on that |
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
Start with these:
Boot downloaded image (basic):
Modified to boot from URL with no local image:
In both cases output is printed directly to console as image supports serial line emulated by QEMU. Extending command line by switching to VirtIO devices (rng, nic, drives), increasing TCG cache (e.g. by Arch Linux can be booted too, yet it is slower and ISO will require many RAM (1-2 GB, maybe more). Probably will have issues with text-only mode and you will need a VNC. |
The following packages will be upgraded:
apt bash curl libcurl openssl pulseaudio qemu-user-i386
Newly arisen error:
Steps to reproduce:
Install Arch Linux 32 on armv7l with qemu support. Command
setupTermuxArch v
attempts to install and configure Arch Linux 32 on armv7l architecture.Expected behavior:
PRoot with QEMU enabled run correctly like it did before this last upgrade.
The text was updated successfully, but these errors were encountered: