3,240
edits
Changes
From SME Server
Jump to navigationJump to searchVirtualBox 4.0 on SME Server v8 beta 6 (view source)
Revision as of 21:49, 12 March 2017
, 21:49, 12 March 2017no edit summary
{{warning box|this how to is out of date. You probably wants to install the smeserver-phpvirtualbox and smeserver-virtualbox contribs for SME8 and SME9, then see here : [[Phpvirtualbox]]}}
===Maintainer===
===Maintainer===
[http://www.compsos.com.au CompSOS]
[http://www.compsos.com.au CompSOS]
===Support===
===Support===
For questions or comments regarding this HOWTO, contact [mailto:shiena@compsos.com.au Shiena Tadeo] of [http://www.compsos.com.au Computing SOS] or Sorolo Systems Inc. at this [mailto:sme@sorolo.com email] address.
For questions or comments regarding this HOWTO, contact [mailto:shiena@compsos.com.au Shiena] of [http://www.compsos.com.au Computing SOS] or Sorolo Systems Inc. at this [mailto:sme@sorolo.com email] address.
===Description===
===Description===
This has been tested using the following:<br/>
This has been tested using the following:<br/>
<ol>
<li>SME Server Release 8.0</li>
<li>VirtualBox-4.3</li>
<li>Kernel is 2.6.18-348.6.1.el5</li>
</ol>
===Requirements===
===Requirements===
Computer with SME server version 8 beta 6 and higher installed.
Computer with SME server version 8 and higher installed.
===Installation===
===Installation===
<ol>
<ol>
<li value="1">Setup SME Server v8 beta 6.</li>
<li value="1">Setup SME Server v8.</li>
<li value="2">Do a yum update.</li>
<li value="2">Do a yum update.</li>
<pre>yum update</pre>
<pre>yum upgrade</pre>
<li value="3"> If any updates were applied, update and reboot the server.</li>
<li value="3"> If any updates were applied, update and reboot the server.</li>
<pre>signal-event post-upgrade
<pre>signal-event post-upgrade; signal-event reboot</pre>
signal-event reboot</pre>
<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 value="5">Install kernel-devel to get the latest development tree.<br/>
Use this command only if you have a PAE kernel installed:
Use the command below, only if you have a PAE kernel installed:
<pre>yum install kernel-PAE-devel kernel-headers</pre>
<pre>yum clean all
yum install kernel-PAE-devel kernel-headers
yum info kernel-headers</pre>
Otherwise,
Otherwise,
<pre>yum install kernel-devel kernel-headers</pre>
<pre>yum install kernel-devel kernel-headers</pre>
</li>
</li>
<li value="6">Check if the compiler (GCC) is installed. If not installed, install it.</li>
Note : if you do not want to update your kernel, because of kmdl not available you can search for the right kernel-headers and kernel-devel in http://vault.centos.org/
<li value="6">Check if the compiler (GCC) is installed by issuing this command.
<pre>rpm -qa | grep gcc</pre>
You will have an output, similar to this:
<pre>libgcc-4.1.2-54.el5
gcc-4.1.2-54.el5</pre>
If not installed, install it.
<pre>yum install gcc</pre>
<pre>yum install gcc</pre>
If you will get an error "No package gcc available. Nothing to do" then do this:
<pre>cd /tmp
wget ftp://ftp.mirrorservice.org/sites/sourceware.org/pub/gcc/releases/gcc-4.7.1/gcc-4.7.1.tar.gz</pre>
</li>
<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.<br/>
<li value="8">Change your kernel boot options.<br/>
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
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
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:
<pre>kernel /vmlinuz-2.6.18-238.19.1.el5 ro root=/dev/main/root </pre>
<pre>kernel /vmlinuz-2.6.18-348.6.1.el5 ro root=/dev/main/root </pre>
<p>change it to:</p>
<p>change it to:</p>
<pre>kernel /vmlinuz-2.6.18-238.19.1.el5 ro root=/dev/main/root divider=10</pre>
<pre>kernel /vmlinuz-2.6.18-348.6.1.el5 ro root=/dev/main/root divider=10</pre>
<p><b>Reminder:</b> if you subsequently update SME Server to use a newer kernel, you may need to change
<p><b>Reminder:</b> if you subsequently update SME Server to use a newer kernel, you may need to change
your kernel boot line to reflect the update.</p>
your kernel boot line to reflect the update.</p>
the command below - they are all supposed to be backticks.</p>
the command below - they are all supposed to be backticks.</p>
<pre>ls /lib/modules/`uname -r`/build</pre>
<pre>ls -la /lib/modules/`uname -r`/build</pre>
</li>
</li>
<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>
<pre>yum install --enablerepo=epel dkms</pre>
<pre>yum install --enablerepo=epel dkms</pre>
<li value="13">Install the VirtualBox repository using the instructions [http://wiki.contribs.org/VirtualBox_Repository here].</li>
<li value="13">Install the VirtualBox repository using the instructions [http://wiki.contribs.org/VirtualBox_Repository here].</li>
<li value="14">Install <b>VirtualBox</b> (At the time of the last update to these instructions, the latest version was v4.1-2).</li>
<li value="14">Install <b>VirtualBox</b> (At the time of the last update to these instructions, the latest version was v4.3-4.3.6-91406).</li>
<pre>yum install --enablerepo=virtualbox VirtualBox-4.1</pre>
<pre>yum install --enablerepo=virtualbox VirtualBox-4.3</pre>
<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>
<pre>signal-event post-upgrade
<pre>signal-event post-upgrade; signal-event reboot</pre>
signal-event reboot</pre>
<li value="18">Setup VirtualBox as a service so it starts automatically after a reboot. Copy the command below on putty console then hit Enter.</li>
<li value="18">Setup VirtualBox as a service so it starts automatically after a reboot.</li>
<pre>for file in $(ls /etc/rc5.d/S??vbox*); do cp "$file" /etc/rc7.d/. ;done</pre>
<pre>for file in $(ls /etc/rc5.d/S??vbox*); do cp "$file" /etc/rc7.d/. ;done</pre>
<li value="19">Create a ''vbox.cfg'' file on your /etc/vbox/.</li>
<li value="19">Create a ''virtualbox'' file on your /etc/default/.</li>
<pre>nano /etc/vbox/vbox.cfg</pre>
<pre>nano /etc/default/virtualbox</pre>
virtualbox should have this content.
<pre>VBOXWEB_USER='root'
<pre>VBOXWEB_USER='root'
VBOXWEB_HOST=127.0.0.1
VBOXWEB_HOST=127.0.0.1
VBOXWEB_PORT=18083</pre>
VBOXWEB_PORT=18083
VBOXWEB_LOGFILE=/var/log/vboxweb
INSTALL_DIR=/usr/lib/virtualbox</pre>
<b>Note: Without the ''virtualbox'' file, vbox services on your rc7.d folder will not start.</b>
<b>After creating the ibay, do not forget to assign a password.</b>
<li value="20">Install phpVirtualBox using this link http://wiki.contribs.org/Phpvirtualbox#DB_Configuration
<li value="21">Before we install <b>[http://code.google.com/p/phpvirtualbox/ phpVirtualBox]</b>, make sure you install <b>SOAP</b> first</li>
<li value="21">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>
Finally,
Finally,
<li value="30">Open a terminal window to the SME Server and create a directory to store the virtual machine images.</li>
<li value="22">Open a terminal window to the SME Server and create a directory to store the virtual machine images.</li>
<pre>mkdir -p /var/lib/VirtualBox/VMs</pre>
<pre>mkdir -p /root/VirtualBox VMs/addons</pre>
<li value="31">Download the VirtualBox Guest Additions iso for later installation into your virtual machine guests.</li>
<li value="23">Download the VirtualBox Guest Additions iso for later installation into your virtual machine guests.</li>
<pre>mkdir -p /var/lib/VirtualBox/addons
<pre>cd /root/VirtualBox VMs/addons
cd /var/lib/VirtualBox/addons
wget http://download.virtualbox.org/virtualbox/4.3.6/VBoxGuestAdditions_4.3.6.iso</pre>
wget http://download.virtualbox.org/virtualbox/4.1.2/VBoxGuestAdditions_4.1.2.iso</pre>
<li value="32">Using a web browser, Go to http://yourdomain.com/phpvbox and connect to the phpVirtualBox web application.
<li value="24">Using a web browser, Go to http://yourdomain.com/phpvirtualbox and connect to the phpVirtualBox web application.
At this point, VirtualBox should now be configured and running correctly. 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 this list.
</li>
</li>
</ol>
===Creating a Virtual Machine===
===Creating a Virtual Machine===
<ol>
<li value="33">Using a web browser, go to http://yourdomain.com/phpvbox to create your virtual machine.
<li>Using a web browser, go to http://yourdomain.com/phpvirtualbox to create your virtual machine.
<ul>
<ul>
<li>Create a new virtual machine (e.g. vmXP)</li>
<li>Create a new virtual machine (e.g. vmXP)</li>
<li>Enable network card (either NAT or Bridged) so you can connect to your new VM console.</li>
<li>Enable network card (either NAT or Bridged) so you can connect to your new VM console.</li>
</ul>
</ul>
[[File:virtual_box.jpg]]
[[File:PhpVirtualBox-rdp-port.jpg]]
<li>Even when the extension is installed, the VRDP server is disabled by default. On console:</li>
<li value="34">Ensure you are connected to the server's internal network, then open a Remote Desktop client program.
<pre>vboxmanage modifyvm "vmXP" --vrde on</pre>
<li>Ensure you are connected to the server's internal network, then open a Remote Desktop client program.
<ul>
<ul>
<li> On Windows, open an RDP client (run->mstsc) then type your server’s domain name, (e.g. mydomain.com), hostname (e.g. myserver), or ip address (e.g. 192.168.100.254)</li>
<li>On Windows, open an RDP client (run -> mstsc) then type your server’s hostname:port number (e.g. myserver:9000), or your Server's (not your Guest) IP address followed by colon then the port number as shown on above image (Remote Desktop Server Port under Display) (e.g. 192.168.100.1:9000).</li>
<b>NOTE:</b> No need to change to port number to 9000 (as per above) in your Windows registry (HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber). It will still be using port 3389 even though phpVirtualBox is using port 9000.<br/>
If you're remotely connected to your server's phpvirtualbox and adding a new Guest remotely, open port 9000 (source and destination TCP poty) pointing to server's IP, so you can be able to access the console built-in to PhpVirtualBox.
</li>
</ul>
</ul>
</li>
<li>Install the VirtualBox Guest Additions ISO into your newly setup VM.</li>
[[File:PhpVirtualBox-install-guest-addition.jpg]]
</ol>
<li value="35">Install the VirtualBox Guest Additions iso into your newly setup VM.</li>
===Access VM outside the Network===
<ol>
<li>On SME Server Manager page, on <b>Port Forwarding</b> left menu, open port <b>9000</b> (as per Remote Desktop Server Port under Display) using your desired Source Port:</li>
Protocol: TCP<br/>
Source Ports: 33900<br/>
Destination IP: 192.168.5.1 ''(which is also the guest IP'')<br/>
Destination Port: 9000<br/>
Allow Hosts: <you can leave it blank, or place your Public IP so only your IP can access the VM)<br/>
Rule Comment: <eg. vmXP for SOS><br/>
<li>Now you can access your VM thru RDP using this hostname ''domain.com:33900''</li>
</ol>
</ol>
</pre>
</pre>
<li>Edit your vbox file located on /etc/init.d/
<li>Edit your ''vbox'' file located on /etc/init.d/
<pre>
<pre>
#!/bin/sh
#!/bin/sh
[[Category: Virtualisation]]
[[Category: Virtualisation]]
[[Category: Advanced]]
[[Category: Advanced]]
[[Category: Contrib]]
[[Category: Howto]]
