virtualbox.org

Did you reboot the host so the new kernel matched the headers?

oh yeah.. rebooting

That seems to have solved the installation issues!

everything passes now! Thank you! Could you give me the non-linux explanation of the problem I was experiencing and what the solution did? Thinking of blogging this for others to use (I'm setting it up
as a dev environment for a .net framework project that I want to make run on mono).

Will let you know how it works out with the user group stuff and automounting

Simply put there is a process on every Linux system that one needs to follow.
None of them are up-to-date when you get them and that appears to be the part everyone fails with.
(1) update the OS
(2) install needed packages to be able to compile external kernel modules
(3) Reboot (usually due to kernel updates)
(4) Install VirtualBox
That's the simple guide.

Yay! That so totally solved it after adding my account to the correct group! Thank you

http://twitter.com/#!/TheCodeJunkie/sta ... 6479369217

So would it be correct to say that the GA kernal module required a newer version of the kernal dev tools, than that which was installed with openSUSE?

Also do you think your first suggestion with
would have solved it straight away, if I had rebooted after or was it the
that brought the existing ones up to the latest available version?

Thanks again!

As I stated in the above it more than likely takes both. If you install the kernel packages and then do an update which installs a new kernel you will be out of sync again.

Also every time your kernel updates you will need to go through this again if you have not installed dkms or openSUSE equivalent to keep the headers in sync with the kernel. This is explained in your VirtualBox users manual.