Suse 11.0 problem with VirtualBox

I am running Suse 11.0 and trying to get a virtual machine running using VirtualBox. I’ve started creating a Win98 environment but get the following error when I try to start it:-

The VirtualBox kernel driver is not accessible to the current user. Make sure that the user has write permissions for /dev/vboxdrv by adding them to the vboxusers groups. You will need to logout for the change to take effect…
VBox status code: -1909 (VERR_VM_DRIVER_NOT_ACCESSIBLE).

Result Code:
IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}

I have taken a look (using YAST) at my User and Group security and I don’t see anything re vboxdrv. How can I set up what this message is asking for? How do I go on from here?

Yast > Security and Users > User and Group Management > Users tab select user then click “EDIT” button > Details tab > check vboxuser in right panel then OK.

And when you get it working for W98, read the FAQ item on how to avoid high CPU load running a W98 VM.

Thanks guys
I have installed Win98. It’s running a little slow but working. I will take a look into the CPU usage etc. and then I want to try and get my scanner working as I want my old OCR facility (unfortunately, I have not found OCR on Linux to come near the Windows apps).
Someone has suggested that Vmware Player is better than VirtualBox. Any thoughts on this?
I initially tried to get XEN going but found out I needed a bigger and better processor than I have. Which of all of these is actually the best considering peripheral support as that is what I’m really wanting (eg USB devices and serial ports, etc)?

Something I meant to ask… It seems that after every reboot I will have to reload vboxdrv using modprobe.
How do I put this into the boot procedure, and how would I remove it if necessary at a later stage?

vboxdrv is loaded by the init script /etc/init.d/vboxdrv. All you have to do is make it run at levels 3 and 5 using the runlevel editor in YaST. Alternatively from a root shell just do:

chkconfig --list vboxdrv

and note that it isn’t loaded at any runlevel, and then do

chkconfig --set vboxdrv on

and do

chkconfig --list vboxdrv

and you will see that it is now set to be loaded at levels 2-5.