After the recent kernel upgrade to 2.6.25.9-0.2-default Virtualbox no longer operates. The currently installed version is 1.5.6_2.6.25.5_1.1-33.1. I presume I need an updated kernel module for Virtualbox which matches the new kernel version.
Question: Where can I find such a beast, and/or where or who may I approach to prod the process? I’m sure other Virtualbox users are in the same boat.
Thanks for any advice.
Run /etc/init.d/vboxdrv setup.
Stopping VirtualBox kernel module done
Recompiling VirtualBox kernel module, NOT. It has been packaged. done
Starting VirtualBox kernel module failed
(Kernel module not found)
Virtualbox was installed with Yast2 as a package. I don’t think this will work unless there is a way to override the behavior. Guess I’ll just have to wait until the package makers decide to build it. I was just wondering if there was some way to communicate this need to them.
Or remove the packages and manually do it the hard way, if they aren’t in the mood to build it. Seems to me a proper QA program would build out all kernel modules whenever building a new update kernel for distribution to users.
Thanks anyways though.
Don’t know what the issue is, but that’s all I had to do when I upgraded the kernel.
Are you using the Virtualbox from Sun or from some OpenSUSE I’m told exists? If you got it from a repo, then it’s the maintainer of that package in the repo who needs to update it for a new kernel. I used the RPM from Sun and it works fine. Only drawback is that you have to also update kernel-source at the same time and run the vboxdrv setup step.
I had the same problem in Opensuse 11 64bits:
# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel module done
Recompiling VirtualBox kernel module, NOT. It has been packaged. done
Starting VirtualBox kernel module failed
(Kernel module not found)
After update the kernel 2.6.25.9-0.2-default, vboxdrv does not work.
I’m using VirtualBox OSE from Opensuse repos.
jason bourne schrieb:
> Stopping VirtualBox kernel module
> done
> Recompiling VirtualBox kernel module, NOT. It has been packaged.
> done
> Starting VirtualBox kernel module
> failed
> (Kernel module not found)
That’s how the openSUSE VirtualBox package behaves.
Its packagers have deliberately amputated the possibility
to recompile the kernel module on the grounds that they would
provide a new module readily compiled whenever necessary.
> Virtualbox was installed with Yast2 as a package. I don’t think this
> will work unless there is a way to override the behavior. Guess I’ll
> just have to wait until the package makers decide to build it.
Exactly. Normally you would expect them to provide an updated
package together with the new kernel that requires it. Oh well …
> Or remove the packages and manually do it the hard way, if they aren’t
> in the mood to build it.
It’s not that hard. Sun provides an RPM too, which isn’t really
more difficult to install than the one from openSUSE, but is not
crippled the same way.
> Seems to me a proper QA program would build
> out all kernel modules whenever building a new update kernel for
> distribution to users.
ACK
T.
you night want to try updating virtualbox from yast - software management
The latest version available is 1.6.2-8
This got mine working again.
I had been steadily upgrading from 10.3 to 11.0, including the KDE Beta 2. As time went by I found myself spending more time diddling with workarounds and b0rkedness more than actually getting any other work done. The KDE Beta 2 was worse then Beta 1, and especially when I noticed network throughput to/from Samba shares was horrible (xxxKB/s range) I decided I needed a box that “just works”. I even tried a fresh install of openSUSE 11.0 and it wasn’t a solution.
Went back to openSUSE 10.3 and after all the upgrading to get it current network speed is back to the (max) 24MB/s I had before, as well as not having to press the form feed button on the printer to print documents, and many other myriad annoyances.
All of the newer (SUN’s) Virtualbox releases won’t do anything over 800x600 resolution with a Windows XP guest. Way to go SUN! Buy out someone else’s software and promptly break stuff that has worked well for some time. What a shame…
So I’ve gone back to previous generation(s) of stuff that “just worked”. Now everything is fine again, so it’s back to work time. Too bad these software houses are managed by the clueless. If one were to distinguish themselves by only releasing superior quality products for use one could easily corner a market.
But that’s a rant for another day. Thanks to all who replied.
Jason
That’s true, there is a newer version of virtualbox available provided you have community repository for Virtualbox enabled.
If you want to enable it then go:
YaST -> Software -> Software repositories
Then click on Add button and choose from that long list of options community repository and click on next button. Then select Virtualbox and you are done.
The updates for virtualbox will be visible to openSUSE updater.
I just installed the Sun Virtualbox 1.6.2 RPM for 10.3 on 11.0 after installing dependencies (pam-devel, gcc, make, kernel-source) and it works just fine. Even get a 1024x800 XP screen. This is on an old i586 machine.
I guess Sun forgot to target me with the bugs. 
I’ve used virtualbox since they went opensource and windows xp has always worked with my desktop resolution (1680x1050) and any custom resolution that the window happens to be expanded to. The trick is to use autofit - the guest window is automatically resized to any resolution.
Also, you might want to go with the official virtualbox rpms, rather than the OSE. The only times I’ve seen vboxdrv setup fail have been when my kernel and kernel-source packages had different version numbers. Either that or kernel-source wasn’t installed.
Opensuse 11.0 with kde 3.5 would give you a much more stable experience, closer to what you have with 10.3. Well, go with whatever works best for you.
Had the same problem (vboxdrv module for 2.6.25.5, running kernel 2.6.25.9). Solution: Because there nothing in the kernel compile options has been changed, you can just load the vboxdrv module with
sudo insmod /lib/modules/2.6.25.5-1.1-default/updates/vboxdrv
(or whereever it is located at your machine) and it works (at least for me)
That did the trick… But now when I click on settings I get…
Could not load the Host USB Proxy Service (VERR_FILE_NOT_FOUND). The service might be not installed on the host computer.
Result Code:
0x00004005
Component:
Host
Interface:
IHost {81729c26-1aec-46f5-b7c0-cc7364738fdb}
Callee:
IMachine {f95c0793-7737-49a1-85d9-6da81097173b}
<rant>
Novell (openSUSE) should make virtualbox work just fine with newer kernels, etc. I don’t want to have to go to OBS to get virtualbox when my distro has it in default repo. I agree with another poster than went back to 10.3 because of a lot of bugs. I think newer features are great, but bug squashing tops my list of Priorities for a good distro. I dislike 6-month release cycles like other distros. I think that is too quick, but if priorities like \features/ and \stability+bugs/ were on a continuum, priority should lean more to \stability+bugs/. That’s my personal taste, and others would probably disagree. But I put SUSE on an intermediate/advanced distro, not too hard (yast is nice) and not too easy (too much automation can lead to big errors in judgment). Because of this, I think there should be MORE focus on stability, not necessarily LESS focus on features et al. However - I really REALLY REALLY like OBS.
</rant>