[gem5-users] Re: 答复: Re: SPEC2017 in FS mode

[Hoa Nguyen via gem5-users]

Hi Victor,

Thanks for reporting these problems! It really helps us improve the resources.

Regarding 1), I'm not sure about the cause of the error. However,
please make sure that you are using gem5/stable with
gem5-resources/stable. An alternative is to use gem5/develop with
gem5-resources/develop.

As a note, the current spec-2017 configs in gem5-resources/stable is
broken. To fix this, you'll need to cherry-pick this change
(https://gem5-review.googlesource.com/c/public/gem5-resources/+/46219).
There is a download button telling the commands could be used to
cherry-pick the change.

Regarding 2a), it seems that celery has changed since we made that
tutorials. An alternative is to use run_job_pool() as specified here
(https://gem5art.readthedocs.io/en/latest/main-doc/faq.html) and here
(https://gem5art.readthedocs.io/en/latest/main-doc/tasks.html#use-of-python-multiprocessing).

Regarding 2b), it should be "experiments_repo" that is defined earlier
in the tutorial instead of "run_script_repo".

Regards,
Hoa Nguyen

On 5/27/21, Victor Kariofillis via gem5-users  wrote:
> First of all, thanks Hoa for the help. Indeed, there was an issue with the
> gcc directory.
>
> Unfortunately, I'm having some other issues as well.
>
> 1) With the gem5 resources method, the intrate benchmarks build and train
> successfully in the vm. (Only 502.gcc_r has a problem). However, using
> run_spec.py to run them with gem5 results in an error.
>
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "build/X86/python/m5/main.py", line 457, in main
>   File "~/spec2017/gem5-resources/configs/run_spec.py", line 254, in
> 
> root, system = create_system(linux_kernel_path, disk_image_path,
>   File "~/spec2017/gem5-resources/configs/run_spec.py", line 142, in
> create_system
> system = MySystem(kernel = linux_kernel_path,
>   File "~/spec2017/gem5-resources/configs/system/system.py", line 63, in
> __init__
> self.system_port = self.membus.cpu_side_ports
>   File "build/X86/python/m5/SimObject.py", line 1277, in __getattr__
> *AttributeError: object 'SystemXBar' has no attribute 'cpu_side_ports'*
>   (C++ object is not yet constructed, so wrapped C++ methods are
> unavailable.)
>
> I know that gem5 has made some changes recently to the naming of the ports,
> but looking at SystemXBar there is definitely a cpu_side_ports object.
>
> 2) I've also tried the approach using gem5art based on this
> 
> tutorial. There are two issues.
> a) I get an error that there is no -E option for the celery command.
> Looking at the documentation of celery and at --help, there's no mention of
> an -E option.
> b) At the end of the launch_spec2017_experiment.py file, there is mention
> of run_script_repo that is not defined as an artifact beforehand. Should it
> be defined, and if yes how?
>
> Thanks,
> Victor
>
> On Tue, 25 May 2021 at 14:05, Bobby Bruce via gem5-users <
> gem5-users@gem5.org> wrote:
>
>> FYI: Hoa has a fix for this, reported here:
>> https://gem5.atlassian.net/browse/GEM5-996.
>>
>> Thanks Hoa!
>> --
>> Dr. Bobby R. Bruce
>> Room 3050,
>> Kemper Hall, UC Davis
>> Davis,
>> CA, 95616
>>
>> web: https://www.bobbybruce.net
>>
>>
>> On Mon, May 24, 2021 at 4:22 AM Hoa Nguyen via gem5-users <
>> gem5-users@gem5.org> wrote:
>>
>>> Hi Victor,
>>>
>>> I see the problem now.
>>>
>>> In install-spec2017 script line 21
>>> (
>>> https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/spec-2017/disk-image/spec-2017/install-spec2017.sh#21
>>> ),
>>> we replace the default gcc_dir so that specmake will use
>>> Ubuntu-installed gcc rather than spec's one.
>>> More specifically, it will replace
>>> gcc_dir = "/opt/rh/devtoolset-7/root/usr"
>>> by
>>> gcc_dir = "/usr"
>>>
>>> However, in your SPEC 2017 disc, it comes with devtoolset-9 and not
>>> devtoolset-7.
>>>
>>> So, one way to fix that is to change "devtoolset-7" in the line 21 to
>>> "devtoolset-9".
>>>
>>> Regards,
>>> Hoa Nguyen
>>>
>>> On 5/20/21, Victor Kariofillis via gem5-users 
>>> wrote:
>>> > Hi Hoa,
>>> >
>>> > Thanks for the help. I'm able now to look into why the builds fail.
>>> >
>>> > The gcc and gfortran commands are not found, which is weird since in
>>> > *install-spec2017.sh* there is a command for installing them. In the
>>> > terminal, I can clearly see that it is executed.
>>> >
>>> > qemu: build-essential is already the newest version (12.4ubuntu1).
>>> >> qemu: gfortran is already the newest version (4:7.4.0-1ubuntu2.3).
>>> >> qemu: 0 upgraded, 0 newly installed, 0 to remove and 176 not
>>> >> upgraded.
>>> >>
>>> >
>>> > But when it's time to build spec benchmarks they fail.
>>> >
>>> > specmake: /opt/rh/devtoolset-9/root/usr/bin/gfortran: Command not
>>> > found
>>> >>
>>> >
>>> > Thanks
>>> >
>>> > On Thu, 20 May 2021 at 21:01, Liyichao via gem5-users <
>>> gem5-users@gem5.org>
>>> > wrote:
>>> >
>>> >> Hi Hoa:
>>> >> Is the spec-2017 img just 

[gem5-users] Re: Error Building the Disk Image SPEC CPU2017 using packer

[Hoa Nguyen via gem5-users]

Hi,

The log seems to indicate that QEMU cannot use KVM on your machine.
To resolve this problem, you can either enable KVM, or choose not to
use KVM for creating the disk image.
To not to use KVM, you'll need to remove the line:
"accelerator": "kvm"
in this file: 
https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/spec-2017/disk-image/spec-2017/spec-2017.json#9.

Regards,
Hoa Nguyen

On 5/30/21, Ange via gem5-users  wrote:
> Hi,
>
> I am new to gem5, and I am trying to run SPEC CPU 2017 benchmark in full
> system simulation on X86. I have been following this tutorial
> https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/spec-2017,
> but I am getting errors building my cpu2017-1.1.0.iso file using packer
> ( ./packer build spec-2017/spec-2017.json). I have looked at the log, and I
> think my error is coming from one of the log messages below; I have been
> trying to fix this issue, but I have not been successful.
>
> packer version v1.3.4
> ubuntu version 20.04
>
> 2021/05/28 14:35:39 packer-builder-qemu plugin: Started Qemu. Pid: 3412
> 2021/05/28 14:35:39 packer-builder-qemu plugin: Qemu stderr: WARNING: Image
> format was not specified for '/tmp/packer701940508' and probing guessed
> raw.
> 2021/05/28 14:35:39 packer-builder-qemu plugin: Qemu stderr:
> Automatically detecting the format is dangerous for raw images, write
> operations on block 0 will be restricted.
> 2021/05/28 14:35:39 packer-builder-qemu plugin: Qemu stderr:
> Specify the 'raw' format explicitly to remove the restrictions.
> 2021/05/28 14:35:39 packer-builder-qemu plugin: Qemu stderr: Could not
> access KVM kernel module: No such file or directory
> 2021/05/28 14:35:39 packer-builder-qemu plugin: Qemu stderr:
> qemu-system-x86_64: failed to initialize KVM: No such file or directory
> 2021/05/28 14:35:39 ui error:  [1;31m==> qemu: Error launching VM: Qemu
> failed to start. Please run with PACKER_LOG=1 to get more info. [0m
> 2021/05/28 14:35:39 packer-builder-qemu plugin: failed to unlock port
> lockfile: close tcp 127.0.0.1:5994: use of closed network connection
> 2021/05/28 14:35:39 packer-builder-qemu plugin: failed to unlock port
> lockfile: close tcp 127.0.0.1:3853: use of closed network connection
> 2021/05/28 14:35:39 packer-builder-qemu plugin: Deleting floppy disk:
> /tmp/packer701940508
> ___
> 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] Error Building the Disk Image SPEC CPU2017 using packer

[Ange via gem5-users]

Hi,

I am new to gem5, and I am trying to run SPEC CPU 2017 benchmark in full system 
simulation on X86. I have been following this tutorial 
https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/spec-2017,
 but I am getting errors building my cpu2017-1.1.0.iso file using packer
( ./packer build spec-2017/spec-2017.json). I have looked at the log, and I 
think my error is coming from one of the log messages below; I have been trying 
to fix this issue, but I have not been successful.

packer version v1.3.4
ubuntu version 20.04 

2021/05/28 14:35:39 packer-builder-qemu plugin: Started Qemu. Pid: 3412
2021/05/28 14:35:39 packer-builder-qemu plugin: Qemu stderr: WARNING: Image 
format was not specified for '/tmp/packer701940508' and probing guessed raw.
2021/05/28 14:35:39 packer-builder-qemu plugin: Qemu stderr:  
Automatically detecting the format is dangerous for raw images, write 
operations on block 0 will be restricted.
2021/05/28 14:35:39 packer-builder-qemu plugin: Qemu stderr:  Specify 
the 'raw' format explicitly to remove the restrictions.
2021/05/28 14:35:39 packer-builder-qemu plugin: Qemu stderr: Could not access 
KVM kernel module: No such file or directory
2021/05/28 14:35:39 packer-builder-qemu plugin: Qemu stderr: 
qemu-system-x86_64: failed to initialize KVM: No such file or directory
2021/05/28 14:35:39 ui error: ==> qemu: Error launching VM: Qemu failed 
to start. Please run with PACKER_LOG=1 to get more info.
2021/05/28 14:35:39 packer-builder-qemu plugin: failed to unlock port lockfile: 
close tcp 127.0.0.1:5994: use of closed network connection
2021/05/28 14:35:39 packer-builder-qemu plugin: failed to unlock port lockfile: 
close tcp 127.0.0.1:3853: use of closed network connection
2021/05/28 14:35:39 packer-builder-qemu plugin: Deleting floppy disk: 
/tmp/packer701940508
___
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