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
There is explicit network support on the QEMU patches, but either it is buggy or we are not using the correct magic options.
7060
7073
7074
+
Solved on unmerged c42634d8e3428cfa60672c3ba89cabefc720cde9 from https://github.com/ispras/qemu/tree/rr-180725
7075
+
7061
7076
TODO `arm` and `aarch64` only seem to work with initrd since I cannot plug a working IDE disk device? See also: https://lists.gnu.org/archive/html/qemu-devel/2018-02/msg05245.html
I had the same error previously on x86-64, but it was fixed: https://bugs.launchpad.net/qemu/+bug/1762179 so maybe the forgot to fix it for `aarch64`?
7078
7092
7093
+
Solved on unmerged c42634d8e3428cfa60672c3ba89cabefc720cde9 from https://github.com/ispras/qemu/tree/rr-180725
7094
+
7095
+
===== QEMU reverse debugging
7096
+
7097
+
TODO get working.
7098
+
7099
+
QEMU replays support checkpointing, and this allows for a simplistic "reverse debugging" implementation proposed at https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg00478.html on the unmerged link:https://github.com/ispras/qemu/tree/rr-180725[]:
7100
+
7101
+
....
7102
+
./run -F '/rand_check.out;/poweroff.out;' -r
7103
+
./run -F '/rand_check.out;/poweroff.out;' -R -d
7104
+
....
7105
+
7106
+
On another shell:
7107
+
7108
+
....
7109
+
./rungdb start_kernel
7110
+
....
7111
+
7112
+
In GDB:
7113
+
7114
+
....
7115
+
n
7116
+
n
7117
+
n
7118
+
n
7119
+
reverse-continue
7120
+
....
7121
+
7122
+
and we are back at `start_kernel`
7123
+
7079
7124
==== QEMU trace multicore
7080
7125
7081
7126
TODO: is there any way to distinguish which instruction runs on each core? Doing:
0 commit comments