Hi, first I want to thank you for your fast help and appropriate answering to
my e-mail, I am sending this to tell you what finally happen with my
sage-vmware upgrade.
a) I tried to install again sage-3.4 making the changes to memsize in
sage_vmx.vmx but this did not work at all,
the behavior was the same that the previous one.
b) I tried with the other available build download sage-3.2.3, changing also
the memsize as you suggest, and I have now the sage again at work. So I am
pretty much happy than last saturday, and this would be my solution meanwhile I
upgrade my laptop, but ...
c) What now concerns me is that I was reading another e-mail of someone with
as much as 3GB of ram who could not put vmware sage-3.4 to work, showing the
same behavior I have reported previously. Perhaps as William suggest that
vmware build is broken.
Finally, I just want to thank you again,
Jorge
> From: wst...@gmail.com
> Date: Sat, 18 Apr 2009 19:04:30 -0700
> Subject: [sage-support] Re: I was using sage-3.1.4 upgrade to 3.4 and have
> memory issues
> To: sage-support@googlegroups.com
>
>
> On Sat, Apr 18, 2009 at 6:59 PM, mabshoff
> <michael.absh...@mathematik.uni-dortmund.de> wrote:
> >
> >
> >
> > On Apr 18, 6:53 pm, William Stein <wst...@gmail.com> wrote:
> >> 2009/4/18 Jorge E. ´Sanchez Sanchez <hnr...@hotmail.com>:
> >
> > <SNIP>
> >
> >> > So I went back, to install the previous version available in the download
> >> > page: sage-vmware-3.2.3, it worked for a while but very slowly all the
> >> > time,
> >> > after that when I tried to run sage_vmx.vmx, the VMware console sent a
> >> > complaining message like "not enough memory for running the given virtual
> >> > machine" and suggest that restarting the host if the VM was working
> >> > previously will fix the problem, I tried that many times, but still sage
> >> > cannot restart as told.
> >
> > There might no longer be any Sage 3.1.4 binaries, but you can download
> > the sources into the current Sage VMWare image, unpack them somewhere
> > in $HOME, run make and they should build fine. Given that a serious
> > number of bugs have been fixed since then as well as numerous
> > enhancements added this is generally not recommended.
>
> Moreover, doing the above will in no way help at all. The entire
> problem is that the default memsize on the virtual machine was
> increased in 3.2.3 to 512 from 300-ish in 3.1.4. Sage worked for you
> before, not because you used 3.1.4, but because of a single default
> setting in the virtual machine. Given that your computer only has
> 512MB RAM, it's no surprise that a virtual machine can't work if it
> tries to allocate 512MB RAM too.
>
> William
>
> >
> >> Edit the file sage_vmx.vmx and change the line that says
> >>
> >> memsize="512"
> >>
> >> to
> >>
> >> memsize="300"
> >>
> >> or some other smaller number (between say 200 and 324).
> >>
> >> William
> >
> > Cheers,
> >
> > Michael
> > >
> >
>
>
>
> --
> William Stein
> Associate Professor of Mathematics
> University of Washington
> http://wstein.org
>
> >
_________________________________________________________________
¿Ya actualizaste tu Perfil de Windows Live?
www.actualizatuperfil.com.mx
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
