All I can offer here is the usual advice:
1) Reduce the number of target processors to 1
2) Reduce the target clock frequency to 20 MHz
3) Run simics without the -stall flag / with the -fast flag
4) If possible, use Simics 2.x to make the checkpoints because booting
seems to be faster
Once disks are made (os installed, etc), its fine to crank up the cpu
speed and increase the number of processors, provided you pass -r to
the kernel at boot-time.
Regards,
Dan
Abdullah Kayi wrote:
Thanks Dan for the clarification. I realized that I do not
have "xterm" installed on my host machine (Intel Q6600 Quadcore 2.4 Ghz
w/4GB Memory), so after installing that I get more information and
control during the installation. Even though I still get the same
warnings this time installation seems to be running but after 15 hours
I am this stage, is this normal?
Solaris Initial Install
MBytes Installed: 96.57
MBytes Remaining: 3593.09
Installing: X Windows System Window Drivers
Here is th output from "top".
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
20270 apokayi 25 0 551m 302m 7056 R 100 9.2 958:16.20
simics-common
Here is the size of the disk that is being generated.
apokayi@klondike:~/checkpoint_files$ du -h
212M ./disk
212M .
Regards,
Abdullah
On Mon, Mar 17, 2008 at 11:57 PM, Dan Gibson
< degibson@xxxxxxxx>
wrote:
The naked scripts are available to simplify the checkpoint-creation
process -- you do not NEED to use them to run GEMS, but they
(sometimes) make initial checkpoint creation more convenient by
automating the boot / OS install process. If you prefer to boot your
own machine from scratch ala GEMS 1.x (possibly using the naked scripts
as a guide), feel free.
Regards,
Dan
Abdullah Kayi wrote:
I am also very interested in learning the
answer to this
question. Or any other solution to start running simulations on GEMS
without using these scripts that are apparently not working for me.
Regards,
Abdullah
On Sun, Mar 16, 2008 at 8:06 PM, Berkin
Ozisikyilmaz < boz283@xxxxxxxxxxxxxxxxxxxx>
wrote:
Do we need
to use naked-check-create.sh to
create the checkpoints? Or can we just boot the machine up with simics
and then
get a check point with write-configuration?
Thanks
Berkin
-----Original
Message-----
From: gems-users-bounces@xxxxxxxxxxx
[mailto:gems-users-bounces@xxxxxxxxxxx]
On Behalf Of Dan
Gibson
Sent: Sunday,
March
16, 2008 5:38
PM
To: Gems Users
Subject: Re:
[Gems-users]
Checkpoints creation problem
Simics
2.2.19 checkpoints
are forward-compatible to Simics 3.0.x.
Abdullah Kayi wrote:
One more thing I compiled Ruby and Opal using
instructions for
Simics3.0.X and using simics3.0.31. But as suggested earlier I am using
simics
2.2.19 for the checkpoints. Is this a problem? I remember the scripts
don't
work for simics3.0.X.
Abdullah
On Sun,
Mar 16, 2008 at
4:24 PM, Abdullah Kayi <apokayi@xxxxxxxxx>
wrote:
It does
exist. After I
run the naked-check-create.sh script "disk" directory is also being
created inside that directory. I am not sure why the script complains
about it
when I run directly from simics.
As far as I understand from the installation instructions after
compiling Ruby
and Opal before starting any simulation we need to create the
checkpoints. And
at that stage the only file to be modified is system.conf, right?
I haven't changed anything neither in simics2.2.19 nor any of the
scripts in
gems2.1. I also checked the md5sums of the Solaris iso images and I
tried
Solaris9,10,Express. So finding a stupid mistake that blindly I missed
in
system.conf was somehow my only hope.
Abdullah
On Sun,
Mar 16, 2008 at
3:58 PM, Derek Hower <drh5@xxxxxxxxxxx>
wrote:
The
original system.conf
file that comes with the Gems release
contains the parameters that worked for us.
Make sure that the directory /home/apokay/checkpoint_files exists
before you run the script.
-Derek
On Sun, Mar 16, 2008 at 11:56 AM, Abdullah Kayi <apokayi@xxxxxxxxx>
wrote:
> To narrow down the potential mistake(s), can anybody kindly send
his/her
> system.conf file that worked fine with naked-check-create.sh to me?
> My host system settings are gcc 3.4.6, x86_64 Linux (ubuntu
gutsy 7.10),
> simics 2.2.19, gem 2.1.
>
> Thanks in advance,
>
> Abdullah
>
>
> On Sun, Mar 16, 2008 at 12:41 AM, Abdullah Kayi <apokayi@xxxxxxxxx>
wrote:
> >
> > I tried to debug the error by going to
$(SIMICS_DIR)/home/sarek and
tried
> to run the installation script directly from there with:
> >
> > ./simics -x sol10-cd-install-1.simics
> >
> > I am getting the following errors when I tried to install
Solaris10.
I am
> not sure if this new set of errors would help to solve the problem.
> > I am actually not even sure what I am doing is viable in this
situation.
> Any help is appreciated.
> >
> > Checking out a license... done: academic license.
> > Looking for additional Simics modules in ./modules
> >
> > +----------------+ Copyright 1998-2005 by
Virtutech, All Rights
> Reserved
> > | Virtutech | Version:
simics-2.2.19
> > | Simics | Compiled:
Tue Aug 16 20:23:17 CEST 2005
> > +----------------+
> > www.simics.com
"Virtutech" and "Simics" are trademarks of
> Virtutech AB
> >
> > Type 'copyright' for details on copyright.
> > Type 'license' for details on warranty, copying, etc.
> > Type 'readme' for further information about this version.
> > Type 'help help' for info on the on-line documentation.
> >
> > Using CD-ROM image file:
/home/apokayi/Solaris/sol-10-u4-ga-sparc-v1.iso
> >
> >
> > setting media file-cd25B_2_6
> > [fc0_image error] Error creating
/home/apokayi/checkpoint_files
> >
> >
> >
> > /disk/platinum.disk: No such file or directory
> > [error] setting attribute files in fc0_image:
> > illegal value
> > Error while loading a configuration: Failed to initialize all
objects
> > This has left the configuration system in an inconsistent
state.
> > Restarting Simics is recommended.
> >
> > Failed to initialize all objects
> >
> > Failed loading the configuration in Simics. This is probably
> > due to some misconfiguration, or that some required file is
> > missing. Please check the above output for error messages
> >
> > [platinum-common.simics:227] the command did not complete
properly;
> interrupting script
> > [sol10-cd-install-1.simics:63] the command did not complete
properly;
> interrupting scrip
> >
> >
> > Many thanks,
> >
> > Abdullah
>
>
_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.
--
http://www.cs.wisc.edu/~gibson [esc]:wq!
_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/"
to your search.
_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.
--
http://www.cs.wisc.edu/~gibson [esc]:wq!
_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/"
to your search.
_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.
--
http://www.cs.wisc.edu/~gibson [esc]:wq!
|
|