Changes

   <li value="4">Check your current kernel.</li>

   <li value="4">Check your current kernel.</li>

       <pre>uname -r</pre>

       <pre>uname -r</pre>

   <li value="5">Install kernel-devel to get the latest development tree.</li>

   <li value="5">Install kernel-devel to get the latest development tree.

Use this command only if you have a PAE kernel installed:

Use this command only if you have a PAE kernel installed:

       <pre>yum install kernel-PAE-devel kernel-headers</pre>

       <pre>yum install kernel-PAE-devel kernel-headers</pre>

Otherwise,

Otherwise,

       <pre>yum install kernel-devel kernel-headers</pre>

       <pre>yum install kernel-devel kernel-headers</pre>

 

   <li value="6">Check if the compiler (GCC) is installed. If not installed, install it.</li>

   <li value="6">Check if the compiler (GCC) is installed. If not installed, install it.</li>

       <pre>yum install gcc</pre>

       <pre>yum install gcc</pre>

   <li value="7">Update SME, and reboot again</li>

   <li value="7">Update SME, and reboot again.</li>

       <pre>signal-event post-upgrade

       <pre>signal-event post-upgrade

signal-event reboot</pre>

signal-event reboot</pre>

   <li value="8">Change your kernel boot options</li>

   <li value="8">Change your kernel boot options

       <pre>Optionally, for best results with SME 8.x and earlier versions,

       Optionally, for best results with SME 8.x and earlier versions, modify /etc/grub.conf, adding divider=10 to the kernel boot options in order

modify /etc/grub.conf, adding divider=10 to the kernel boot options in order

to reduce the idle CPU load with VirtualBox. For example, if your kernel boot line is

to reduce the idle CPU load with VirtualBox. For example, if your kernel boot line is

kernel /vmlinuz-2.6.18-238.19.1.el5 ro root=/dev/main/root

      <pre>kernel /vmlinuz-2.6.18-238.19.1.el5 ro root=/dev/main/root</pre>

change it to

      change it to

kernel /vmlinuz-2.6.18-238.19.1.el5 ro root=/dev/main/root divider=10</pre>

      <pre>kernel /vmlinuz-2.6.18-238.19.1.el5 ro root=/dev/main/root divider=10</pre>

<b>Reminder: if you subsequently update SME Server to use a newer kernel, you may need to change

<b>Reminder: if you subsequently update SME Server to use a newer kernel, you may need to change

your kernel boot line to reflect the update.</b>

your kernel boot line to reflect the update.</b>

 

   <li value="9">Create a symbolic link</li>

   <li value="9">Create a symbolic link</li>

       <pre>NOTE: Be careful if you cut-and-paste the command below.

       <b>NOTE: Be careful if you cut-and-paste the command below. In some terminal windows, from some browsers, the parts of the command in

In some terminal windows, from some browsers, the parts of the command in

bold font do not paste correctly. Pay particular attention to the dashes (-) and the backticks (`). There aren't any single quote marks in

bold font do not paste correctly. Pay particular attention to the

the command below - they are all supposed to be backticks.</b>

dashes (-) and the backticks (`). There aren't any single quote marks in

the command below - they are all supposed to be backticks.</pre>

ln <b>-s</b> /usr/src/kernels/<b>`uname -r`</b>-<b>`uname -m`</b> /lib/modules/<b>`uname -r`</b>/build<br />

    <pre>ln <b>-s</b> /usr/src/kernels/<b>`uname -r`</b>-<b>`uname -m`</b> /lib/modules/<b>`uname -r`</b>/build</pre>

<b>Reminder: if you subsequently update SME Server to use a newer kernel, you may need to recreate the symbolic link.</b>

    <b>Reminder: if you subsequently update SME Server to use a newer kernel, you may need to recreate the symbolic link.</b>

   <li value="10">Check that the symbolic link was properly created by doing a directory listing.</li>

   <li value="10">Check that the symbolic link was properly created by doing a directory listing.</li>

       <pre>NOTE: Be careful if you cut-and-paste the command below.

       <b>NOTE: Be careful if you cut-and-paste the command below. In some terminal windows, from some browsers, the parts of the command in

In some terminal windows, from some browsers, the parts of the command in

bold font do not paste correctly. Pay particular attention to the dashes (-) and the backticks (`). There aren't any single quote marks in

bold font do not paste correctly. Pay particular attention to the

the command below - they are all supposed to be backticks.</b>

dashes (-) and the backticks (`). There aren't any single quote marks in

 

the command below - they are all supposed to be backticks.</pre>

    <pre>ls /lib/modules/<b>`uname -r`</b>/build</pre>

   <li value="11">Install the Fedora Epel repository using the instructions [http://wiki.contribs.org/Epel here].</li>

   <li value="11">Install the Fedora Epel repository using the instructions [http://wiki.contribs.org/Epel here].</li>

   <li value="12">Install Dynamic Kernel Module Support (DKMS)</li>

   <li value="12">Install Dynamic Kernel Module Support (DKMS)</li>

   <li value="15">Review the VirtualBox installation log to ensure that the installation was successful.</li>

   <li value="15">Review the VirtualBox installation log to ensure that the installation was successful.</li>

       <pre>tail /var/log/vbox-install.log</pre>

       <pre>tail /var/log/vbox-install.log</pre>

   <li value="16"> Remove the compiler install (for security best practices)</li>

   <li value="16">Remove the compiler install (for security best practices)</li>

       <pre> rpm -e gcc</pre>

       <pre> rpm -e gcc</pre>

   <li value="17">Update SME, and reboot again</li>

   <li value="17">Update SME, and reboot again</li>

VBOXWEB_PORT=18083</pre>

VBOXWEB_PORT=18083</pre>

Note: Without the vbox.cfg, vbox services on your rc7.d folder will not start.

<b>Note: Without the vbox.cfg, vbox services on your rc7.d folder will not start.</b>

   <li value="20">Login to the server-manager page and create an ibay for <b>phpvbox</b>.

   <li value="20">Login to the server-manager page and create an ibay for <b>phpvbox</b>.

   <li value="24">Create a config file using the example file provided.</li>

   <li value="24">Create a config file using the example file provided.</li>

       <pre>cp config.php-example config.php</pre>

       <pre>cp config.php-example config.php</pre>

   <li value="25">Open ''config.php'' (located on your /phpvbox/html/ folder). Uncomment some lines (by removing the '#' at the beginning of the line).</li>

   <li value="25">Open ''config.php'' (located on your /phpvbox/html/ folder). Uncomment some lines (by removing the '#' at the beginning of the line).

       <pre>nano /home/e-smith/files/ibays/phpvbox/html/config.php</pre>

       <pre>nano /home/e-smith/files/ibays/phpvbox/html/config.php</pre>

       <pre>/* SOAP URL of vboxwebsrv (not phpVirtualBox's URL) */

       <pre>/* SOAP URL of vboxwebsrv (not phpVirtualBox's URL) */

       <pre>// Path

       <pre>// Path

var $cachePath = '../tmp';</pre>

var $cachePath = '../tmp';</pre>

 

   <li value="26">Disable authentication of ''vboxwebsrv'' (this is not recommended, but at this stage, this is the only setup that works). Login to the server’s SSH and type this command.</li>

   <li value="26">Disable authentication of ''vboxwebsrv'' (this is not recommended, but at this stage, this is the only setup that works). Login to the server’s SSH and type this command.</li>

       <pre>vboxmanage setproperty websrvauthlibrary null</pre>

       <pre>vboxmanage setproperty websrvauthlibrary null</pre>

signal-event reboot</pre>

signal-event reboot</pre>

   <li value="29">Ensure that the extension pack is installed correctly.</li>

   <li value="29">Ensure that the extension pack is installed correctly.

Open a console window, then

Open a console window, then

       <pre>vboxmanage list extpacks</pre>

       <pre>vboxmanage list extpacks</pre>

 

At this point, VirtualBox should now be configured and running correctly. To check this, we will now log into the ibay we created for phpVirtualBox and attempt to create a new virtual machine.If you encounter problems, please recheck that you have setup VirtualBox as a service so it starts automatically after a reboot, and that your vbox.cfg file is configured correctly. To manage VirtualBox and any virtual machines, use the command line utility VBoxManage. See VBoxManage --help . For a list of available switches for VBoxManage, see [http://www.virtualbox.org/manual/ch08.html this list].

At this point, VirtualBox should now be configured and running correctly. To check this, we will now log into the ibay we created for phpVirtualBox and attempt to create a new virtual machine. If you encounter problems, please recheck that you have setup VirtualBox as a service so it starts automatically after a reboot, and that your vbox.cfg file is configured correctly. To manage VirtualBox and any virtual machines, use the command line utility VBoxManage. See VBoxManage --help . For a list of available switches for VBoxManage, see [http://www.virtualbox.org/manual/ch08.html this list].

Finally,

Finally,

</pre>

</pre>

<li>Edit your vbox file located on /etc/init.d/</li>

<li>Edit your vbox file located on /etc/init.d/

<pre>

<pre>

#!/bin/sh

#!/bin/sh

esac

esac

</pre>

</pre>

</ol>

</ol>