This might not be too relevant to OS X, since I am running Ubuntu, but I'll put it here for the record anyway, in case it is useful to someone:
At some point when the virtualbox image wasn't working for me I recompiled the kernel module this way. I think that I did it after getting a more informative error message from virtualbox that suggested it as a solution. I also had the problem that I had to unload the KVM kernel modules before virtualbox would work. I think that I installed KVM sometime in the past to try it out, but I don't actually use it. (Virtualbox actually gave me an intelligent error message here.) I originally thought that the final thing that I did to make the virtualbox image go from not working to working was increase the video ram, but I have since tried decreasing the video ram, and the image still works. Also, somewhere in between I created a different virtualbox image to install Windows on, and I may have rebooted by computer once or twice. Anyway, these are at least some of the various things that I did, and some combination of these actions made the image work when it originally did not. I wish I had been more systematic so that I knew exactly what I did. Another thought that occurs to me is: What does virtualbox do when you ask it to use VT-X/AMD-V and your processor does not support it? Will it cause an error, or will virtualbox just ignore the option? On Wed, 2009-10-28 at 23:58 -0400, Bill Page wrote: > William, Marshall, > > Have you tried recompiling the Virtualbox kernel headers? > > $ sudo /etc/init.d/vboxdrv setup > > It also reloads the kernel module. > > I suppose that reasonably you should not have to do this immediately > after an install but perhaps the install misses something subtle about > the configuration. > > Regards, > Bill Page. > > On Wed, Oct 28, 2009 at 11:33 PM, William Stein wrote: > > > > On Mon, Oct 26, 2009 at 9:18 AM, mhampton wrote: > >> > >> I can't seem to get virtualbox 3.0.8 to work on my mac. Things work > >> fine on my windows machine, I did a small test by adding the new > >> biopython optional package and that worked well. I am curious if > >> anyone else can get virtualbox to work on OS X 10.4, or if its > >> something funny about my machine. > >> > >> -Marshall > > > > I just had exactly the same problem as you with the same error message > > on my OS X 10.6 macbook air laptop. I did the following: > > > > 1. Rebooted. That didn't fix it. > > 2. Downloaded VirtualBox (3.0.10 now -- they release more often > > than Sage!), and reinstalled from scratch. That didn't help. > > 3. Reinstalled 3.0.10 *again* from scratch... and everything works > > now. Weird. > > > > When I googled for results about this error message during the last > > week, all I found were emails from you. > > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
