5,576
edits
Changes
From SME Server
Jump to navigationJump to search→Kernel Upgrade
*how to create [[VirtualBox_4.0_on_SME_Server_v8_beta_6#Creating_a_Virtual_Machinecreate| your first VM]]
*how to create [[VirtualBox_4.0_on_SME_Server_v8_beta_6#Creating_a_Virtual_Machinecreate| your first VM]]
*how to automatically [[VirtualBox_4.0_on_SME_Server_v8_beta_6#Automatically_Start_Virtual_Machine|start VM with the server]] }}
*how to automatically [[VirtualBox_4.0_on_SME_Server_v8_beta_6#Automatically_Start_Virtual_Machine|start VM with the server]] }}
===Restart the Web Service===
phpvirtualbox controls a virtualbox service, you may need to restart it if you can't connect to phpvirtualbox
/etc/init.d/vboxweb-service restart
===Kernel Upgrade===
===Kernel Upgrade===
After a kernel upgrade and the "signal-event post-upgrade; signal-event reboot", the vboxdrv need to be compiled with the new kernel, a script is launched at the boot time to test if the compilation is needed.
After a kernel upgrade and the "signal-event post-upgrade; signal-event reboot", the vboxdrv need to be compiled with the new kernel, a script is launched at the boot time to test if the compilation is needed.
You can see if all kernel modules are compiled and loaded, if you issue :
# /etc/init.d/vboxdrv status
VirtualBox kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) are loaded.
{{Tip box|If you want to launch manually the compilation of virtualbox module you can do these command lines in a root terminal.}}
{{Tip box|If you want to launch manually the compilation of virtualbox module you can do these command lines in a root terminal.}}
