Termux•7d ago

qemu-system-i386 segfault error

Today I found out that

qemu-system-i386

qemu-system-i386

qemu-system-i386

qemu-system-i386 was removed from my phone somehow. I dont know why, i dont recall uninstalling it. I tried to start up my tinycorelinux distrubition after i installed it back. With the prompt i always used:

qemu-system-i386 \

-cdrom Core-current.iso \

-hda core.img \

-hdb /data/data/com.termux/files/home/tce_disk.qcow2 \

-boot d \

-m 128 \

-net nic \

-net user,hostfwd=tcp::2222-:22 \

-vnc :0

Although it keeps giving me a segfault error and i have no idea why.

7//ELiTEs.resOP•12/15/25, 1:20 PM

~ $ qemu-system-i386 \
-cdrom Core-current.iso \
-hda core.img \
-hdb /data/data/com.termux/files/home/tce_disk.qcow2 \
-boot d \
-m 128 \
-net nic \
-net user,hostfwd=tcp::2222-:22 \
-vnc :0
Segmentation fault qemu-system-i386 -cdrom Core-current.iso -hda core.img -hdb /data/data/com.termux/files/home/tce_disk.qcow2 -boot d -m 128 -net nic -net user,hostfwd=tcp::2222-:22 -vnc :0
~ $

7//ELiTEs.resOP•12/15/25, 1:25 PM

There is not much instaled in the disk, just openssh, nasm, and ld

7//ELiTEs.resOP•12/15/25, 1:26 PM

I can somehow boot it up on the terminal but the screen stays completely black when i do, and i recall thats why i've been using vnc this whole time

7//ELiTEs.resOP•12/15/25, 1:27 PM

~ $ qemu-img check tce_disk.qcow2
No errors were found on the image.
1387/4096 = 33.86% allocated, 3.32% fragmented, 0.00% compressed clusters
Image end offset: 91226112
~ $
~ $ ls -lh tce_disk.qcow2
-rw-------. 1 u0_a245 u0_a245 87M Dec 1 16:30 tce_disk.qcow2
~ $ file Core-current.iso
Core-current.iso: ISO 9660 CD-ROM filesystem data 'Core' (bootable)

7//ELiTEs.resOP•12/15/25, 1:29 PM

owokitty•12/15/25, 1:44 PM

@7//ELiTEs.res hi,

owokitty•12/15/25, 1:44 PM

could you use this command and show me the result ? (outside of qemu)

owokitty•12/15/25, 1:45 PM

uname -muname -m

7//ELiTEs.resOP•12/15/25, 1:46 PM

~ $ uname -m
aarch64

7//ELiTEs.resOP•12/15/25, 1:47 PM

It used to work before i dont even know how it dissapeared

owokitty•12/15/25, 1:49 PM

hmm i will check in a 64-bit arm device and check if i can reproduce it. i could not really reproduce this as described in a 32-bit arm device but i did not try in a 64-bit arm device yet

7//ELiTEs.resOP•12/15/25, 1:51 PM

I think my disks may be corrupted but im not really sure

owokitty•12/15/25, 1:52 PM

corrupted guest disk should probably not cause segmentation fault of the host program

7//ELiTEs.resOP•12/15/25, 1:52 PM

I shared them with a curious friend on whatsapp once

owokitty•12/15/25, 1:54 PM

could you show the result from this command?

owokitty•12/15/25, 1:54 PM

termux-infotermux-info

owokitty•12/15/25, 1:57 PM

i used this command on my 64-bit ARM Android 14 device and i see tiny core linux

owokitty•12/15/25, 1:57 PM

owokitty•12/15/25, 1:57 PM

qemu-system-i386 \
  -cdrom Core-current.iso \
  -m 128 \       
  -net nic \                                              
  -net user,hostfwd=tcp::2222-:22

qemu-system-i386 \
  -cdrom Core-current.iso \
  -m 128 \       
  -net nic \                                              
  -net user,hostfwd=tcp::2222-:22

7//ELiTEs.resOP•12/15/25, 2:10 PM

Termux Variables:
TERMUX_API_VERSION=0.53.0
TERMUX_APK_RELEASE=F_DROİD
TERMUX_APP_PACKAGE_MANAGER=apt
TERMUX_APP_PID=14624
TERMUX_APPDATA_DIR=/data/user/0/com.termux
TERMUX_APPLEGACY_DATA_DIR=/data/data/com.termux
TERMUX_APPSE_FILE_CONTEXT=u:object_r:app_data_file:s0:c245,c256,c512,c768
TERMUX_APPSE_INFO=default:targetSdkVersion=28:complete
TERMUX_IS_DEBUGGABLE_BUILD=0
TERMUX_MAIN_PACKAGE_FORMAT=debian
TERMUX_VERSION=0.118.3
TERMUXHOME=/data/data/com.termux/files/home
TERMUXPREFIX=/data/data/com.termux/files/usr
TERMUXROOTFS_DIR=/data/data/com.termux/files
TERMUXSE_PROCESS_CONTEXT=u:r:untrusted_app_27:s0:c245,c256,c512,c768
TERMUX__USER_ID=0
Packages CPU architecture:
aarch64
Subscribed repositories:

sources.list

deb https://packages-cf.termux.dev/apt/termux-main stable main

x11-repo (sources.list.d/x11.list)

deb https://packages-cf.termux.dev/apt/termux-x11 x11 main

root-repo (sources.list.d/root.list)

deb https://packages-cf.termux.dev/apt/termux-root root stable
Updatable packages:
All packages up to date
termux-tools version:
1.45.0
Android version:
13
Kernel build information:
Linux localhost 5.4.274-qgki-g31f2484d2934 #1 SMP PREEMPT Thu Mar 6 11:10:15 CST 2025 aarch64 Android
Device manufacturer:
HONOR
Device model:
RMO-NX1
Supported ABIs:
SUPPORTED_ABIS: arm64-v8a,armeabi-v7a,armeabi
SUPPORTED_32_BIT_ABIS: armeabi-v7a,armeabi
SUPPORTED_64_BIT_ABIS: arm64-v8a
LD Variables:
LD_LIBRARY_PATH=
LD_PRELOAD=/data/data/com.termux/files/usr/lib/libtermux-exec-ld-preload.so
Installed termux plugins:
com.termux.api versionCode:1002
com.termux.tasker versionCode:1002
com.termux.x11 versionCode:15
com.termux.boot versionCode:1000

owokitty•12/15/25, 2:12 PM

ok thanks,

Oowokitty ```bash qemu-system-i386 \ -cdrom Core-current.iso \ -m 128 \ -net ...

owokitty•12/15/25, 2:13 PM

and i wondered does the same crash happen if you use this command i tried and use the

qemu-system-i386

qemu-system-i386

package instead of the qemu-system-i386-headlessqemu-system-i386-headless package?

owokitty•12/15/25, 2:14 PM

so that the normal GUI appears? or does it only happen when you use the specific arguments and the specific drive images that you use normally?

owokitty•12/15/25, 2:14 PM

i tested this tiny core linux

owokitty•12/15/25, 2:14 PM

http://www.tinycorelinux.net/16.x/x86/release/Core-current.iso

7//ELiTEs.resOP•12/15/25, 2:14 PM

owokitty•12/15/25, 2:17 PM

hmm it looks like it is working with that test that i did

owokitty•12/15/25, 2:17 PM

now

owokitty•12/15/25, 2:17 PM

could you try adding the arguments back that you need one by one so you can check which one causes the crash for you?

owokitty•12/15/25, 2:18 PM

so you could try this next

owokitty•12/15/25, 2:18 PM

qemu-system-i386 \
  -cdrom Core-current.iso \
  -hda core.img \
  -hdb /data/data/com.termux/files/home/tce_disk.qcow2 \
  -boot d \
  -m 128 \
  -net nic \
  -net user,hostfwd=tcp::2222-:22

qemu-system-i386 \
  -cdrom Core-current.iso \
  -hda core.img \
  -hdb /data/data/com.termux/files/home/tce_disk.qcow2 \
  -boot d \
  -m 128 \
  -net nic \
  -net user,hostfwd=tcp::2222-:22

owokitty•12/15/25, 2:18 PM

and then if that works then you could add the vnc argument and check if that makes it crash for you

7//ELiTEs.resOP•12/15/25, 2:39 PM

Sorry for the delay

7//ELiTEs.resOP•12/15/25, 2:39 PM

I ran into an issue with discord

7//ELiTEs.resOP•12/15/25, 2:40 PM

It worked after i ran it in x11

7//ELiTEs.resOP•12/15/25, 2:40 PM

Then i tried again with termux terminal

7//ELiTEs.resOP•12/15/25, 2:40 PM

It worked again somehow

owokitty•12/15/25, 2:40 PM

hmm

7//ELiTEs.resOP•12/15/25, 2:40 PM

And i was able to connect with vnc

7//ELiTEs.resOP•12/15/25, 2:40 PM

Now i restarted my phone

7//ELiTEs.resOP•12/15/25, 2:41 PM

I will try it again

7//ELiTEs.resOP•12/15/25, 2:41 PM

Without starting x11

Oowokitty `termux-info`

owokitty•12/15/25, 2:41 PM

i have a question did you upgrade your termux with pkg upgradepkg upgrade in between when i said this and when you showed the print out from termux-infotermux-info command?

7//ELiTEs.resOP•12/15/25, 2:41 PM