I downloaded Virtualbox from their official site. I installed it and it worked well. However, every time I reboot my host machine, virtualbox can’t start. I mean after reboot, I click on its icon and nothing happens. I run the installation again and it works again. Some service fails to start? Where should I look at?
Virtualbox uses it’s own kernel module. When you update your kernel that module is not automatically rebuilt. The command triggers rebuilding the kernel-module for Virtualbox, restarts the Virtualbox daemon, and you’re back in business. Maybe this tells you more.
On 02/19/2013 09:56 AM, Knurpht wrote:
>
> bonedriven;2528527 Wrote:
>> I don’t quite understand, but it does work like a charm. Thanks!
>
> Virtualbox uses it’s own kernel module. When you update your kernel
> that module is not automatically rebuilt. The command triggers
> rebuilding the kernel-module for Virtualbox, restarts the Virtualbox
> daemon, and you’re back in business. Maybe this tells you more.
Every kernel module, example vboxdrv.ko, has to be built using exactly the same
setup that was used to build the kernel. For the drivers/modules that are built
into the kernel, it is automatic. Every driver/module that is external to the
kernel (example vboxdrv.ko) must be rebuilt. There is no way around that - that
rule is strictly enforced.
You can get VirtuaBox to recompile and install on each kernel update using dkms. It takes just a little longer on startup as the binary file is compiled into the new kernel. You must install dkms from YaST for this to work. Look at my article on the subject here:
On Tue, 19 Feb 2013 08:56:02 +0000, bonedriven wrote:
> I downloaded Virtualbox from their official site. I installed it and it
> worked well. However, every time I reboot my host machine, virtualbox
> can’t start. I mean after reboot, I click on its icon and nothing
> happens.
> I run the installation again and it works again. Some service fails to
> start? Where should I look at?
Try starting it from a terminal window and see what error message comes
up.
Chances are the service isn’t started - I use the version in the Build
Service in the Virtualization:/VirtualBox_Backports repository and it
doesn’t have any issues. That version is also kept relatively current.
I will see when I get to the office tomorrow. As I thought the issue had been solved after I “rebuilt” the kernel module. However, today the issue did come out once again.
On Wed, 20 Feb 2013 21:56:02 +0000, bonedriven wrote:
> I will see when I get to the office tomorrow. As I thought the issue had
> been solved after I “rebuilt” the kernel module. However, today the
> issue did come out once again.
The nice thing about using the repo is that the kernel module issue is
handled properly (no special steps needed).
Anyway, I just added community repository where there is one for virtualbox or sth. I don’t know if that changes anything. Maybe I need to reinstall virtualbox from there. But I’ll leave it as it is for now.
On Thu, 21 Feb 2013 22:26:02 +0000, bonedriven wrote:
> Knurpht;2529029 Wrote:
>> The way you installed Vbox, this will happen every time you get a new
>> kernel (which normally isn’t too often), just remember to run
>> >
> Code:
> --------------------
> > > su -c ‘/etc/init.d/vboxdrv setup’
> --------------------
>> > whenever it doesn’t work.
>
> Yes, I understand.
>
> Anyway, I just added community repository where there is one for
> virtualbox or sth. I don’t know if that changes anything. Maybe I need
> to reinstall virtualbox from there. But I’ll leave it as it is for now.
Adding the repo isn’t sufficient if you want the updates to come from
there - you need to install it from that repo. Given that it’s working
at present, maybe wait until it isn’t, and then remove the installation
from Oracle and install it from the repo.