Hi Victor, I'm not sure if you're looking at the newly generated disk image since the files are identical to those in the spec2017 disc.
The spec-2017-image/spec-2017 file is the disk image file, which can be mounted using "mount -o offset=1048576" without converting to ISO. The log should be in [mountpoint]/home/gem5/spec/result/. Regards, Hoa Nguyen On Thu, May 20, 2021, 2:33 PM Victor Kariofillis via gem5-users < gem5-users@gem5.org> wrote: > Hi Hoa, > > I tried the changes you proposed. After running the packer build command, > the only thing that's in the spec-2017-image directory is a binary file. > Shouldn't the disk image be a .img file or something like that? How can I > look into the file system of the vm and check the build logs? > > I tried converting the binary file to an .iso and mounting that, but I'm > seeing the exact same files as if I'm mounting the SPEC2017 iso. > > Thanks > > On Wed, 19 May 2021 at 07:09, Hoa Nguyen via gem5-users < > gem5-users@gem5.org> wrote: > >> Hi Victor, >> >> I'm not sure what caused the errors of building the spec benchmarks. >> >> Also, I'm not sure how to prevent the vm from being closed after the >> builds fail. However, there are a few steps can be done to exterminate >> the disk image after the builds fail: >> - In the file src/spec-2017/disk-image/spec-2017/install-spec2017.sh, >> the last line "rm -f /home/gem5/spec2017/result/*" should be removed >> to keep the log generated by spec during benchmark compilation time. >> - When running packer, you can run "./packer build -on-error=abort >> spec-2017/spec-2017.json" to keep the disk image if the disk image >> building process fails. >> - After that, you can mount the disk image and check the log file >> generated by spec. >> >> packer fails due to "output directory already exists". In this case, >> you'll need to remove the "spec-2017/spec-2017-image" folder before >> starting packer again. >> >> Regards, >> Hoa Nguyen >> >> On 5/17/21, Victor Kariofillis via gem5-users <gem5-users@gem5.org> >> wrote: >> > Hi, >> > >> > I've tried running the SPEC2017 benchmarks in FS mode of gem5 using the >> > instructions/files provided by the gem5 resources page. >> > >> > >> https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/spec-2017 >> > >> > I've also followed the step by step instructions in the git repo for >> > gem5-art. >> > >> > https://github.com/darchr/gem5art-experiments/blob/master/README.md >> > >> > Everything works as intended until the benchmarks are supposed to be >> built. >> > All of them fail with one of the two following errors: >> > >> > 1) Error with make! >> > 2) Error with fdo_make_pass1! >> > >> > First of all, why is this happening? Secondly, the vm closes after the >> > builds fail. I don't have the opportunity to check the make.out files >> that >> > have more information about the errors. Is there a way to prevent the >> > connection from closing or reopening it again? Running it again with >> packer >> > fails due to the directory existing already. >> > >> > I'd appreciate any help, >> > Victor >> > >> _______________________________________________ >> gem5-users mailing list -- gem5-users@gem5.org >> To unsubscribe send an email to gem5-users-le...@gem5.org >> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s >> > _______________________________________________ > gem5-users mailing list -- gem5-users@gem5.org > To unsubscribe send an email to gem5-users-le...@gem5.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
