Hi, on commit 96fce476785a834f102ae69a895e661cf08e47cd, I can run the following command and the simulation runs without errors: ./build/ARM/gem5.opt configs/example/fs.py --checkpoint-dir=m5out/ -r 0 --restore-with-cpu=DerivO3CPU --cpu-type=DerivO3CPU --disk-image="$IMG_ROOT/disks/linaro-minimal-aarch64.img" --disk-image="$IMG_ROOT/disks/parsec3.img" --kernel="$IMG_ROOT/binaries/vmlinux.arm64" --caches
The problem is that the script won't actually use both disk images (I want to mount the second in image in-simulation). I read in some thread that this feature became available in the script out of the box at some point, so I decided to try it out with the last stable commit (0d703041fcd5d119012b62287695723a2955b408). However, with it I am no longer able to start simulations with fs.py. I get the following error: "fatal: Can't unserialize 'system.cpu.xc.0:_debugStep'". A similar problem, if not exactly the same, occurs when I use the starter_fs.py script. Is this a bug or do I have to change something in the script options?
_______________________________________________ gem5-users mailing list -- [email protected] To unsubscribe send an email to [email protected] %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
