Cannot open Sage in VirtualBox (sagevm login?)

654 views
Skip to first unread message

Ivo Pezelj

unread,
Mar 16, 2014, 4:03:34 PM3/16/14
to sage-s...@googlegroups.com
Hi there,

It seems like loading Sage from VirtualBox is meant to be a simple task, but for some reason it does not work for me.

I downloaded .ova file normally and installed VirtualBox (obviously I'm using Windows). I loaded .ova into VB without an issue.

However, as I try to start Sage, the virtual machine boots up perhaps normally, up to a point where it asks me for "sagevm login:". There seems to be no way around it. When I do something right, like inserting "sage" and providing the same for password (which pops up next), the machine seems to proceed but quickly shuts down, saying, among others, that it "caught signal 15".

Before this appears, there are some messages that are not overly motivating (like "Fast TSC calibration failed" and "SMBus base address uninitialized"), but as I never used this before I don't know if they are expected.

I have not fiddled with any settings, it was supposed to be a straight loading, so I have no idea what's happening. Interestingly, I was unable to find anyone else ever complaining about this...

This is a fresh installation of the latest Sage.ova and VirtualBox on Win8 64-bit. I have previously only used Sage online.

Many thanks for any help!

Dima Pasechnik

unread,
Mar 17, 2014, 4:55:53 AM3/17/14
to sage-s...@googlegroups.com
On 2014-03-16, Ivo Pezelj <peze...@gmail.com> wrote:
> Hi there,
>
> It seems like loading Sage from VirtualBox is meant to be a simple task, but for some reason it does not work for me.
>
> I downloaded .ova file normally and installed VirtualBox (obviously I'm using Windows). I loaded .ova into VB without an issue.
>
> However, as I try to start Sage, the virtual machine boots up perhaps normally, up to a point where it asks me for "sagevm login:". There seems to be no way around it. When I do something right, like inserting "sage" and providing the same for password (which pops up next), the machine seems to proceed but quickly shuts down, saying, among others, that it "caught signal 15".

from http://wiki.sagemath.org/SageAppliance

6. Summary of usernames and passwords

Login to the Sage notebook - Username: admin, Password: sage
Login to the sage account in the virtual machine - Username: sage,
Password: sage
Login as root (administrator account) to the virtual machine -
Username: root, Password: sage

>
> Before this appears, there are some messages that are not overly motivating (like "Fast TSC calibration failed" and "SMBus base address uninitialized"), but as I never used this before I don't know if they are expected.
>
> I have not fiddled with any settings, it was supposed to be a straight loading, so I have no idea what's happening. Interestingly, I was unable to find anyone else ever complaining about this...
>
> This is a fresh installation of the latest Sage.ova and VirtualBox on Win8 64-bit. I have previously only used Sage online.

Could be a corrupt .ova download, or a version mismatch between .ova
and VirtualBox.
What is the version of VirtualBox you are running?


cjsh100 cjsh100

unread,
Mar 17, 2014, 6:12:56 AM3/17/14
to sage-s...@googlegroups.com
a months age,I run normal,32 bit win xp,about 20 min's,all OK

在 2014年3月17日星期一UTC+8上午4时03分34秒,Ivo Pezelj写道:

Eric Gourgoulhon

unread,
Mar 18, 2014, 5:00:25 PM3/18/14
to sage-s...@googlegroups.com
Hi,

A friend of mine had exactly the same problem: the virtual machine shut down with "Caught signal 15" on Windows 8 64-bit. It seems that's because he installed the 32-bit version of VirtualBox. After installing the 64-bit version of VirtualBox (4.3.8), the problem disappeared and Sage works perfectly. So could you try with VirtualBox 64 bit ?

Best wishes,

Eric.

Volker Braun

unread,
Mar 18, 2014, 10:10:31 PM3/18/14
to sage-s...@googlegroups.com
On Sunday, March 16, 2014 4:03:34 PM UTC-4, Ivo Pezelj wrote:

Before this appears, there are some messages that are not overly motivating (like "Fast TSC calibration failed" and "SMBus base address uninitialized"), but as I never used this before I don't know if they are expected.

These are normal.

Reply all
Reply to author
Forward
0 new messages