Happy that you figured it out. If you don't synchronize the nodes before
starting the communication between nodes, you may get a panic message
indicating that the simulated cluster is out of sync. Like this message
that you get in your log.switch:
"panic: panic condition recv_tick <= curTick()
Hi,
I have solved the problem becasue I added a command into the command
line, which is "--dist-sync-start=10t". However, I can
checkpoint in aarch64-linux.img without this command by dist-gem5. I
have not known why yet. If you guys knows it, please tell it. Thanks a
lot！
On 2018-07-02
Hi Ciro,
Thanks for your suggestion. I should have given more details.
The .rcS script I use to take checkpoint is as follow. I downloaded it
from dist-gem5 official website and did not modify it.
> #!/bin/bash
> # Authors: Mohammad Alian
> # boot gem5 and take a checkpoint
> #
> # The idea
Just saw the attachments now.
I would recommend in-lining them as much as possible in the email, and
selecting the most interesting part if they are huge.
This will make it more likely that people will look at them, and allow
search engines to index them.
On Sun, Jul 1, 2018 at 9:56 AM, Ciro
How did you try to take the checkpoint? Manually or with some init script?
How did you try to restore it, and how did it fail.
Did the init actually script run? Add prints or set -x to it.
On Sun, Jul 1, 2018 at 7:45 AM, Boyang Xu <6172...@gmail.com> wrote:
> Hi everyone,
>
>
> I failed to
Hi everyone,
I failed to take a checkpoint with aarch32-ubuntu-natty-headless.img by
dist-gem5, but succeeded to do it with aarch64-ubuntu-trusty-headless.img.
The input and output files are attached.
My command line is as follow:
> build/ARM/gem5.opt
> -d m5out.0
> --debug-flags=DistEthernet
