Re: [Xen-users] Xen Killing fortran app?!

[Luis Rodrigues <luis@xxxxxxxxx>]

Ok.

Thanks.

On Thu, 11 May 2006 15:59:55 +0200
"Petersson, Mats" <Mats.Petersson@xxxxxxx> wrote:

> > -----Original Message-----
> > From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> > [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> > Luis Rodrigues
> > Sent: 11 May 2006 14:46
> > To: xen-users@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [Xen-users] Xen Killing fortran app?!
> > 
> > 
> > size CAMx.mrpo.1.8.i_linux
> >    text    data     bss     dec     hex filename
> > 2968811 1189952 1287728136      1291886899      4d00a133      
> >   CAMx.mrpo.1.8.i_linux
> > 
> > On dom0 I get:
> > 
> > free
> >              total       used       free     shared    
> > buffers     cached
> > Mem:       1009664     778684     230980          0      
> > 17740     557744
> > -/+ buffers/cache:     203200     806464
> > Swap:            0          0          0
> > 
> > on domU
> > 
> >              total       used       free     shared    
> > buffers     cached
> > Mem:       1043124     868752     174372          0      
> > 47328     568616
> > -/+ buffers/cache:     252808     790316
> > Swap:       511992          4     511988
> > 
> > I have 2GB, 1 for dom0 and 1 form domU.
> 
> That is your problem. If you give more than 1.3GB (plus a bit) to the
> domain you want to run CAMx in, you'll be fine. 
> 
> The numbers are:
> Text - the size of the code (the compiled fortran code + libraries and
> stuff)
> Data - the size of data (variables that have a value other than zero,
> mainly)
> BSS  - block-storage section (variables that are either undefined or
> zero)
> 
> Add those up and you get "dec", which stands for "total size in
> decimal", and convert it to hexadecimal, and you get "hex". Filename is
> obvious enough, I suppose. 
> 
> The "plus a bit" means enough memory for the operating system, shell,
> graphical user interface etc. You probably want at least 128MB for this,
> more will not hurt, except that the other domain ends up with less, and
> that's of course going to affect things in some way. 
> 
> Another option is to make the swap larger. This may work, but only if
> the BSS section is over-sized because the variables are not really used
> all the time - for example, there may be an array that can hold 1000
> elements, but in your usage, it's only used for 400 elements. In this
> case, 60% of this variable would be fine to just "have space for",
> rather than actually residing in RAM. I can't say if this works or not
> for your application, as I'm not quite sure what the design of the
> application is (and I'm not really going to spend several hours trying
> to figure out what does what in some fortran code, a language that I'm
> not very good at understanding in the first place). 
> 
> --
> Mats
> > 
> > It is running fine on domU and craches on dom0.
> > 
> > I really doen't understand these nunbers, is it memory?
> > 
> > Luis
> > 
> > 
> > 
> > 
> > On Thu, 11 May 2006 15:34:17 +0200
> > "Petersson, Mats" <Mats.Petersson@xxxxxxx> wrote:
> > 
> > > > -----Original Message-----
> > > > From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> > > > [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Luis 
> > > > Rodrigues
> > > > Sent: 11 May 2006 14:10
> > > > To: xen-users@xxxxxxxxxxxxxxxxxxx
> > > > Subject: [Xen-users] Xen Killing fortran app?!
> > > > 
> > > > Hi,
> > > > 
> > > > I have an fortran application (CAMx model) that runs fine on my 
> > > > machine witout XEN.
> > > > If  I start xend from init scripts (so xen is running from
> > > > begin) the applications simply craches.
> > > > 
> > > > strace ./CAMx.mrpo.1.8.i_linux
> > > > execve("./CAMx.mrpo.1.8.i_linux",
> > > > ["./CAMx.mrpo.1.8.i_linux"], [/* 33 vars */]) = -1 ENOMEM (Cannot 
> > > > allocate memory)
> > > > +++ killed by SIGKILL +++
> > > How much memory does the app actually need (do "size ./CAMx*")? 
> > > 
> > > It sounds like it could actually be running out of memory, perhaps?
> > > 
> > > --
> > > Mats
> > > 
> > 
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> > 
> > 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users