Creating and reloading snapshots for zynqmp with cosim about qemu

[asultan123]

I can't say I solved this one but since the issue is still open here, are my findings.
Regardless of how you snapshot via QEMU it hangs on loading a snapshot. I tried using CRIU to save the process of the QEMU Instance for both the microblaze and zynqmp instances + the SystemC side and that sort of works but for the particular kernel I was running it crashes on process reload. Unfortunately, my understanding of both QEMU and CRIU's internals isn't sophisticated enough to figure out why the kernel running in the QEMU instance crashes. The only concrete snapshotting mechanism I could get working was if I ran the qemu instance in a virtual machine but obviously that's a little bit naive. Reloading a snapshot in virtualbox takes as long as firing up a new QEMU instance so there's that. I'll eventually get back to this if I find something that makes snapshotting work. Till then, I hope this project isn't dead and someone from the dev team can help out.

[ho28]

Hi, I stumbled across this reported issue after finding out that creating and loading snapshots for simulated Versal on arm-generic-fdt machine also encounters the same problem.

I discovered that this is due to the way memory is created during the arm-generic-fdt machine's memory initialization routine (init_memory) that results in the ram not being registered with the vmstate save handler.

I believe this patch fixes the issue, please let me know if I should file a pull request.

0001-arm-generic-fdt-Save-RAM-during-snapshot.patch