Hi,
I'm new to sage and and Linux and I've been struggling the last few
days to get a running SAGE system on my own machine using the *.ova
and *.ovf files. I'm reporting what I've found since there seems to be
little info on the web, or atleast there is little info using the key
words I've been using to search and I've tried quite a few
combinations. I also have a few questions that are posted at the
bottom.
The problem, as per the readme.txt in the sage website :
1) Download the sage.ovf file
2) Downloaded Sun's VirtualBox or VMware
3) import the application in Virtualbox or VMware starts
> If you get IOAPIC errors on virtualbox go SAGE>Settings (Ctrl
+s)>System>Enable IOAPIC to correct
4) Sage says point firefox to http://localhost:8000
> If you can't connect via firefox your first response may be 'Oh
Doodle', Looking on google for help is a mess.
Corrective action :
To the Newbie there is no direct reason why this should happen, all
the forums point to different problems, none of which seem to help,
most indicate that NAT or Bridged networking should be enabled. None
of these help because infact your network card on the SAGE/Fedora VM
machine is down. This appears to be in the OVF/OVA file and not a
problem in the virtualbox or VMware machine. The steps to verify this
are as follows :
Exit sage note book :
1) press Ctrl+C once or twice to exit the SAGE notebook : either
login as root (Tricky from terminal 7) or prefix all the following
commands with sudo
or
1) press Alt+Fn where n is another terminal n = 2 - 6 worked nicely
and login as root, password should be sage
2) execute : ifconfig # This will show only the lo interface if you
have this error
3) execute : ifconfig -a # This will show all the interfaces and
you'll notice eth1 exists but isn't necessarily up
if you don't see an eth1 or eth0 then you may have issues with the
driver not being installed, I don't know how to fix that. You probably
won't see a wlan0, as all VM cards are treated as hard wired LAN
connections.
4) execute : ifconfig eth1 up # This starts the eth1 card and should
assign it an ip of 10.xxx.xxx.xxx
if you're using a bridged connection with a DHCP router/ADSL box then,
this should also work with NAT but I'm not sure.
5) execute : dhclient eth1 # This will get the correct ip info for the
VM and your VM will be able to access the interwebs, I checked this
only with ping. haven't tried links (the cmd based internet browser),
not sure it's installed in the *.ova/*.ovf in all honesty.
So having eventually worked all that out, I now have a few questions.
1) how do I configure the Fedora VM to use my eth1 settings at startup
instead of restarting with the incorrect IP and eth0 inactive ?
2) how does this all affect twisted the sage webserver ?
3) how do I setup sage to operate from whatever IP the DHCP assigns
the Fedora machine, instead of running local host ?
Thanks to anyone who replies, I also hope I posted in the right forum
regards,
Carel
--
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
URL: http://www.sagemath.org
