Re: [sage-support] Re: Win 7 64 Host and SAGE/Fedora guest on VMware or Virtualbox

2011-12-05 Thread Carel van Dam
I'm doing my masters at the moment and I plan on running sage quite a bit
for now, both via the VM and a local linux install. I can try one image a
month for you guys (The cap is a bit of an issue), and I'll try break each
distro during my coffee breaks :P May be it'd help to setup a page on what
to do when X happens :) I'll read through the links you've sent a little
later. Thanks for the assistance once again.

On Fri, Dec 2, 2011 at 10:28 AM, emil emil.widm...@gmail.com wrote:



 On Dec 1, 11:42 pm, Carel van Dam carelv...@gmail.com wrote:
  Hi Mr. Widmann and Mr Braun,
 
  Thanks for your responses, sorry my reply has been slow. I'll try out
 your
  distro during the week Mr. Widmann, I ran out of cap last month :S. The
  Read Me I was referring to was both of the Read Me's on the Sage download
  site. I can't remember which one I'm afraid.
 
  As to the *.ovf, I got that by extracting the *.ova file, some old
  instructions I found on google told me to do that :S I'm now using the
  OVA's as supplied.
 
  In the *.ova, I had er... Sage 4.7.1, the problem still persists, some
 how
  the network settings were broken when I played around with the VM router
  File  Preferrences (Ctrl+G)  Network  Virtual Box Adapter (Select) 
  Edit (Space)  make changes applicable to your system.
  The network settings for the VM as per Mr. Braun's instructions are also
 to
  do with it.
 
  Since My last e-mail and your replies I got the 4.7.2 ova and the problem
  seems to have fixed itself I also installed  an Open SUSE VM to check I
  could get the network working with the VM and this seemed to work fine,
  both using NAT and the Bridged adaptor.
 
  Yesterday when I took the PC to another network, that broke the sage VM
  again. I fixed it this time by deleting the VM and re-importing, you
 loose
  your files that way but it atleast gets you running again. I believe the
  problem is with virtualbox and not the distribution, so thank you for
 your
  time spent helping me. I'll keep pocking around a bit, If I find anything
  that may be of use to some one who reads this mailing list then I'll
 reply
  here again, mostly because I've seen this question asked a few times on
 the
  web but it's seldomly replied to/solved.
 
  regards,
 
  Carel

 Hello Mr. van Dam,

 thank you for your detailed response. It is very helpful. The
 developement of the virtual machine image - although the most popular
 distribution of sage -
 is still kind of a fringe topic in sage developement. To have more
 people contributing, even if it is just short feedback about arising
 problems, could make an considerable impact about the quality of this
 product (and I explicitly include documentation/troubleshooting as one
 of the most important things).

 You are right that using virtualisation has its own tricks and
 pitfalls. About your problem with the lost net connection: I am
 shooting in the blue here, but it could be related to an existing MAC
 adress of the VM and some settings in the /etc/udev folder.

 Please read here:

 http://www.linuxquestions.org/questions/debian-26/no-network-on-virtualbox-udev-problem-822023/
 https://www.virtualbox.org/ticket/2286
 https://forums.virtualbox.org/viewtopic.php?t=7749highlight=udev

 If the network connectivity is lost I sometimes had success by just
 going to the network section of the Virtual Box GUI and unselect and
 reselect the adapter.

 Sometimes there are other issues - the last days and I installed and
 uninstalled VMs repeadetly. At one point - network was not working and
 I had absolutely no clue why - I had to log into my router because the
 dhcpd server had run out of possible new adresses and I had to
 increase the available pool - I don't think this was the problem in
 your case, just to show that there are some hard to find pitfalls.

 To improve and ease the distribution of the sage VM I built an
 integrated VirtualBox Sage VM installer the last days. To develope
 this further I need some feedback and testers. I know this needs some
 commitment of time and Bandwith but it is just a humble invitation to
 help to make sage an easier experience for a lot of users.

 I have announced this installer and the download link (650 MB) here:

 http://groups.google.com/group/sage-windows/browse_thread/thread/ca801cbfc5b9170d

 kind regards
 emil





 --
 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


-- 
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


Re: [sage-support] Re: Win 7 64 Host and SAGE/Fedora guest on VMware or Virtualbox

2011-12-01 Thread Carel van Dam
Hi Mr. Widmann and Mr Braun,

Thanks for your responses, sorry my reply has been slow. I'll try out your
distro during the week Mr. Widmann, I ran out of cap last month :S. The
Read Me I was referring to was both of the Read Me's on the Sage download
site. I can't remember which one I'm afraid.

As to the *.ovf, I got that by extracting the *.ova file, some old
instructions I found on google told me to do that :S I'm now using the
OVA's as supplied.

In the *.ova, I had er... Sage 4.7.1, the problem still persists, some how
the network settings were broken when I played around with the VM router
File  Preferrences (Ctrl+G)  Network  Virtual Box Adapter (Select) 
Edit (Space)  make changes applicable to your system.
The network settings for the VM as per Mr. Braun's instructions are also to
do with it.

Since My last e-mail and your replies I got the 4.7.2 ova and the problem
seems to have fixed itself I also installed  an Open SUSE VM to check I
could get the network working with the VM and this seemed to work fine,
both using NAT and the Bridged adaptor.

Yesterday when I took the PC to another network, that broke the sage VM
again. I fixed it this time by deleting the VM and re-importing, you loose
your files that way but it atleast gets you running again. I believe the
problem is with virtualbox and not the distribution, so thank you for your
time spent helping me. I'll keep pocking around a bit, If I find anything
that may be of use to some one who reads this mailing list then I'll reply
here again, mostly because I've seen this question asked a few times on the
web but it's seldomly replied to/solved.

regards,

Carel

On Thu, Nov 24, 2011 at 2:35 PM, Volker Braun vbraun.n...@gmail.com wrote:

 If you see the Error: Unable to locate IOAPIC for GIO... error during
 boot you don't have to do anything. The linux kernel in the VM will simply
 not use IOAPIC and everything will work fine.

 I'm very confused how you get a second virtual ethernet device. In my
 virtual machine there is only one virtual network adapter enabled. Are you
 sure you didn't accidentally enable a second adapter? See
 Settings-Network-Adapter N for N=2

 --
 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


-- 
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