Koozali.org: home of the SME Server
Obsolete Releases => SME 8.x Contribs => Topic started by: clm314159 on May 30, 2012, 01:53:38 AM
-
I just installed the new SME 8 and worked through the contrib for installing VBox. The only other modification to the system was that I started but did not finish installing VMware. I got through all the steps up to the point where I access the VBox through the PHPVirtualBox and I could not get any connection. Since this is about 30 steps into the process I was a bit bummed and was worried about finding my mistake after so muny steps. After about 30 min. of trouble shooting and many reboots, I changed the IP address in vbox.cfg (Virtualbox) and config.php (PHPVirtualBox) from 127.0.0.1 to the actual IP of my Host. After a reboot, everything works fine. So my questions are:
1. Is this an important insight to getting VBox to run on SME 8? If so, how do I make the changes to the contribs page or who do I tell to make the changes?
2. I have an 32-bit XP virtual machine running that I am accessing with the Remote Desktop Client from Windows. It is a little jerky in the mouse department. Is there any fix for that?
3. Just a thought, wouldn't it be cleaner to tell people where the actual grub.conf file is located in step 8 instead of the symlink referring to it?
-
Afraid I can't help you on the techy bits but for Wiki access read here :
http://wiki.contribs.org/Help:Contents
B. Rgds
John
-
1. Is this an important insight to getting VBox to run on SME 8? If so, how do I make the changes to the contribs page or who do I tell to make the changes?
2. I have an 32-bit XP virtual machine running that I am accessing with the Remote Desktop Client from Windows. It is a little jerky in the mouse department. Is there any fix for that?
3. Just a thought, wouldn't it be cleaner to tell people where the actual grub.conf file is located in step 8 instead of the symlink referring to it?
Please open a bug at Bugzilla under 8.xx contribs section on the basis that if it does not work (as you have shown here) it is a bug. Folks there will deal with it, i.e. move your report to documentation or whatever. In this way, it will on the records. Please provide full detail, not just a link to this topic.
Thanks.