recommend installing Dynamic Kernel Module Support (DKMS)2. This framework helps with building and upgrading kernel modules. If DKMS is not already installed, execute one of the following: • On an Ubuntu directory (e.g. $HOME/.VirtualBox/Machines on 219 10 Technical background Linux). If you are upgrading from a VirtualBox version before 4.0, files in these directories are not automatically moved in VirtualBox. However, when VirtualBox encounters a settings file from an earlier version (e.g. after upgrading VirtualBox), it attempts to preserve the settings format as much as possible. It will only silently

recommend installing Dynamic Kernel Module Support (DKMS)2. This framework helps with building and upgrading kernel modules. If DKMS is not already installed, execute one of the following: • On an Ubuntu directory (e.g. $HOME/.VirtualBox/Machines on 219 10 Technical background Linux). If you are upgrading from a VirtualBox version before 4.0, files in these directories are not automatically moved in VirtualBox. However, when VirtualBox encounters a settings file from an earlier version (e.g. after upgrading VirtualBox), it attempts to preserve the settings format as much as possible. It will only silently

recommend installing Dynamic Kernel Module Support (DKMS)2. This framework helps with building and upgrading kernel modules. If DKMS is not already installed, execute one of the following: • On an Ubuntu directory (e.g. $HOME/.VirtualBox/Machines on 218 10 Technical background Linux). If you are upgrading from a VirtualBox version before 4.0, files in these directories are not automatically moved in VirtualBox. However, when VirtualBox encounters a settings file from an earlier version (e.g. after upgrading VirtualBox), it attempts to preserve the settings format as much as possible. It will only silently

recommend installing Dynamic Kernel Module Support (DKMS)2. This framework helps with building and upgrading kernel modules. If DKMS is not already installed, execute one of the following: • On an Ubuntu directory (e.g. $HOME/.VirtualBox/Machines on 219 10 Technical background Linux). If you are upgrading from a VirtualBox version before 4.0, files in these directories are not automatically moved in VirtualBox. However, when VirtualBox encounters a settings file from an earlier version (e.g. after upgrading VirtualBox), it attempts to preserve the settings format as much as possible. It will only silently

directory (e.g. $HOME/.VirtualBox/Machines on 234 10 Technical background Linux). If you are upgrading from a VirtualBox version before 4.0, files in these directories are not automatically moved in VirtualBox. However, when VirtualBox encounters a settings file from an earlier version (e.g. after upgrading VirtualBox), it attempts to preserve the settings format as much as possible. It will only silently immediately during startup, in both virtualized and physical environments. The recommended solution is upgrading to at least Solaris 10 5/08 (“S10U5”). Alternative solutions include forcing Solaris to always boot

under the VirtualBox configuration directory (e.g. $HOME/.VirtualBox/Machines on Linux). If you are upgrading from a VirtualBox version before 4.0, files in these directories are not automatically moved in VirtualBox. However, when VirtualBox encounters a settings file from an earlier version (e.g. after upgrading VirtualBox), it attempts to preserve the settings format as much as possible. It will only silently immediately during startup, in both virtualized and physical environments. The recommended solution is upgrading to at least Solaris 10 5/08 (“S10U5”). Alternative solutions include forcing Solaris to always boot

under the VirtualBox configuration directory (e.g. $HOME/.VirtualBox/Machines on Linux). If you are upgrading from a VirtualBox version before 4.0, files in these directories are not automatically moved in VirtualBox. However, when VirtualBox encounters a settings file from an earlier version (e.g. after upgrading VirtualBox), it attempts to preserve the settings format as much as possible. It will only silently immediately during startup, in both virtualized and physical environments. The recommended solution is upgrading to at least Solaris 10 5/08 (“S10U5”). Alternative solutions include forcing Solaris to always boot

under the VirtualBox configuration directory (e.g. $HOME/.VirtualBox/Machines on Linux). If you are upgrading from a VirtualBox version before 4.0, files in these directories are not automatically moved in VirtualBox. However, when VirtualBox encounters a settings file from an earlier version (e.g. after upgrading VirtualBox), it attempts to preserve the settings format as much as possible. It will only silently immediately during startup, in both virtualized and physical environments. The recommended solution is upgrading to at least Solaris 10 5/08 (“S10U5”). Alternative solutions include forcing Solaris to always boot

under the VirtualBox configuration directory (e.g. $HOME/.VirtualBox/Machines on Linux). If you are upgrading from a VirtualBox version before 4.0, files in these directories are not automatically moved in VirtualBox. However, when VirtualBox encounters a settings file from an earlier version (e.g. after upgrading VirtualBox), it attempts to preserve the settings format as much as possible. It will only silently immediately during startup, in both virtualized and physical environments. The recommended solution is upgrading to at least Solaris 10 5/08 (“S10U5”). Alternative solutions include forcing Solaris to always boot

under the VirtualBox configuration directory (e.g. $HOME/.VirtualBox/Machines on Linux). If you are upgrading from a VirtualBox version before 4.0, files in these directories are not automatically moved in VirtualBox. However, when VirtualBox encounters a settings file from an earlier version (e.g. after upgrading VirtualBox), it attempts to preserve the settings format as much as possible. It will only silently immediately during startup, in both virtualized and physical environments. The recommended solution is upgrading to at least Solaris 10 5/08 (“S10U5”). Alternative solutions include forcing Solaris to always boot