search

BUseclab / Pandawan

MIT License
5 stars 1 forks source link

Pandawan fails with errors in `/proc/sys` #2

Open reteps opened 3 months ago

reteps commented 3 months ago

The end of my bootup process looks like this:

init started: BusyBox v1.19.4 (2024-06-06 11:43:25 Europe)
/etc/rc.d/rc.sysinit: line 6: can't create /proc/sys/kernel/panic: nonexistent directory
/etc/rc.d/rc.sysinit: line 8: can't create /proc/sys/vm/panic_on_oom: nonexistent directory
Error reading execve argument
Error reading execve argument
Error reading execve argument
Error reading execve argument
Error reading execve argument
Error reading execve argument
Error reading execve argument
Error reading execve argument
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault

I tried running Pandawan with the qemu arguments firmadyne.procfs=1 and firmadyne.procfs=0, and both gave me this identical error trace. I was wondering if this was a known issue for certain firmwares.

iangelak commented 3 months ago

Does this also occur during the network configuration phase? In that case Pandawan uses stock QEMU to emulate the firmware and deduce its networking (like Firmadyne and FirmAE). Check the qemu.initial.serial.log file if the emulation progrssed beyond this point. If yes then either its (Py)PANDA's fault or Pandawan's fault. Try Pandawan's emulation without any of Pandawan's plugins enabled (i.e., -p "") and see if this occurs again. If it does, then there might be an issue with PANDA.