You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running X86 gem5 full system simulation.
Disk image: ubuntu 22.04 (from gem5 resources)
Linux Kernel: 5.4.49 (from gem5 resources)
The simulation is started with KVM CPU and switched to Timing CPU after OS booted.
When I am trying to run some workloads through m5 readfile or directly input in interactive shell, seg faults may happen.
For example, simple "gdb -v" leads to seg fault.
The workloads successfully run if I boot the same disk image in QEMU.
I wonder if anybody know the cause and how to deal with this.
Thanks!
P.S.
GDB is installed through "apt install gdb" in QEMU.
The systemd is not enabled because systemd will directly cause seg faults.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm running X86 gem5 full system simulation.
Disk image: ubuntu 22.04 (from gem5 resources)
Linux Kernel: 5.4.49 (from gem5 resources)
The simulation is started with KVM CPU and switched to Timing CPU after OS booted.
When I am trying to run some workloads through m5 readfile or directly input in interactive shell, seg faults may happen.
For example, simple "gdb -v" leads to seg fault.
The workloads successfully run if I boot the same disk image in QEMU.
I wonder if anybody know the cause and how to deal with this.
Thanks!
P.S.
GDB is installed through "apt install gdb" in QEMU.
The systemd is not enabled because systemd will directly cause seg faults.
Beta Was this translation helpful? Give feedback.
All reactions