Re: [opensuse] VirtualBox OSE problmes with openSUSE 10.3 On Thu, 2008-02-14 at 09:21 +0200, Dave Plater wrote:
> Tom Patton wrote:
> > On Thu, 2008-02-14 at 00:04 -0200, CF wrote:
> >   
> >> Adam Jimerson wrote:
> >>     
> >>> I installed VirtualBox OSE off the OSS repositories and I have all of its 
> >>> dependencies installed, or the ones that I know I was following the 
> >>> instructions from the VirtualBox End-User Guide and the wiki article about it 
> >>> http://en.opensuse.org/VirtualBox_Installation.  After getting everything set 
> >>> up it works fine until I reboot my system, it seems the vboxdrv kernel module 
> >>> or /dev/vboxdrv does not like to stay installed on my system.  In order to 
> >>> use VirtualBox I have to run the vboxdrv setup command everytime I restart or 
> >>> turn on my machine.
> >>>       
> >> When you install VBox package from OSS repo, you need to load VBox
> >> kernel module manually, as root user, every time you use VBox, or set
> >> the kernel module to be automatically loaded at boot through YaST2 ->
> >> System Configuration.
> >>     
> > correct
> >   
> >> However, none of this is required if you install VBox package directly
> >> from http://www.virtualbox.org/
> >>
> >>     
> > Are you sure?  I'm running the suse10.3 rpm package from their site (for
> > the USB support), and still have to modprobe the vboxdrv module to run
> > it...why do you say it isn't required?  I believe you will find that you
> > do need the module, and will even have to re-compile it when/if you
> > update the kernel..by ===>  (the command "/etc/init.d/vboxdrive setup",
> > and is quite automatic.)
> >
> > Tom in NM
> >
> >
> >   
> With the binary from the virtualbox site, you simply install the rpm and
> it takes care of the kernel and everything else. You only have to run
> the module loader once and once after each kernel change.

Of course. But if SUSE had left vboxdrv alone, having the 'setup' make a
new module, then the SUSE RPM could have done an 'insserv vboxdrv'. Then
(1) we would not be having this discussion because everyone's kernel
modules would load as expected, and (2) new kernels could be handled by
either a new vb rpm, or a simple run of 'vboxdrv setup'. As it stands
now, 'vboxdrv setup' from SUSE does NOT remake the module no matter. The
code is removed unconditionally from that part of the script. You are
running the virtualbox from SUSE's RPM, no?

> Dave
-- 
Roger Oberholtzer

OPQ Systems / RambÃ¶ll RST

RambÃ¶ll Sverige AB
KapellgrÃ¤nd 7
P.O. Box 4205
SE-102 65 Stockholm, Sweden

Office: Int +46 8-615 60 20
Mobile: Int +46 70-815 1696


