I had the same problem with VirtualBox 3.1.0 in Vista: VirtualBox was ignoring the squashfs partition, so Linux loaded but Sage didn't.
The fix was to edit the "IDE Controller" list in VirtualBox -> Settings -> Storage. There should be three entries: sage_appliance.vmdk sage_appliance_swap.vmdk sage_squashfs-4.2.1.vmdk --hms ijvm wrote: > Dear all, > > I encountered a similar problem as described by Christopher Brown. > Since yesterday I had been attempting to install Sage 4.2.1 using > VirtualBox 3.1.0 on two laptops, one with Windows Vista and another > with Windows XP. I always got an error when finalizing the importing > of Sage. Afterwards the VM would run Linux but not Sage. After reading > the previous post I used VirtualBox 3.0.10 and problem solved. > > The error I got in Windows XP was "VirtualBox Interface has > encountered a problem and needs to close. We are sorry for the > inconvenience." > > > On Dec 6, 6:34 pm, Christopher Brown <robot.ga...@gmail.com> wrote: > > I am experiencing an error using virtualbox 3.1.0 and the sage 4.1.2 > > appliance. When I import the appliance using virtualbox, the process runs > > for about two minutes, and then I receive a Windows error, "This program has > > stopped responding". Virtualbox then seems to have the appliance, but only > > runs linux (not sage within linux). > > > > My OS is Windows Vista. > > > > The problem was solved by rolling back to virtualbox 3.0.10. -- 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
