Dear Heng,
Thank you very much for the quick answer!!
However, I would like to save a number of files. Finally, I manage to
save the changes by replacing the following lines in starter_fs.py:
FROM:
image = CowDiskImage()
image.child.image_file = SysPaths.disk(name)
TO:
image = RawDiskImage(read_only=False)
image.image_file = SysPaths.disk(name)
Best regards,
Nikos
Quoting HENG ZHUO <hzh...@wisc.edu>:
Hi Nikos,
I think the unsaved changes are intended behavior, so same disk
image can be used to repeat experiment.
As for saving files, you can do this : m5 writefile fileToSave , and
files will be saved into your run folder. It is similar to how " m5
readfile" at the beginning.
Best,
Heng
On May 17, 2022, at 09:59, Νικόλαος Ταμπουρατζής
<ntampourat...@ece.auth.gr> wrote:
Dear gem5 community,
I simulate the official ubuntu 18.04 image using FS simulation
($GEM5/build/ARM/gem5.fast -d $GEM5/node0
$GEM5/configs/example/arm/starter_fs.py --kernel=vmlinux.arm64
--num-cores=8 --disk-image=ubuntu-18.04-arm64-docker.img)
However, I see that the changes inside the simulated image are not
saved after the correct gem5 termination (m5 exit).
I run a benchmark that saves a number of files during execution.
How can I keep that files after gem5 execution?
Thanks in advance!
Best regards,
Nikos
_______________________________________________
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
_______________________________________________
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
_______________________________________________
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
