On Wed, 2008-02-13 at 08:29 +0100, Per Jessen wrote:

Adam Jimerson wrote:

...

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.

Check if the vboxdrv init-script is properly embedded in your init-sequence.

I have a vboxdrv and a vboxnet in /etc/init.d. These do not seem to be in /etc/rc.d/rc5.d, meaning there may be a missing inserv in the RPMs. I am not sure that this would solve the problem, as the script requires 'setup' as a parameter each time, not the 'start' it will get as part of the rc startup. I confess I have not looked into this more than to run the script. Maybe the 'start' entry does a 'setup' as well. I figured I was not alone and that an update would correct any omission. Which I expect will soon be the case :) -- 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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wed, 2008-02-13 at 10:50 -0500, Adam Jimerson wrote:

On Wednesday 13 February 2008 02:38:50 am Roger Oberholtzer wrote:

...

On Wed, 2008-02-13 at 08:29 +0100, Per Jessen wrote:

...

Same here, I have both vboxdrv and vboxnet in /etc/init.d and /etc/rc.d but not in /etc/rc.d/rc5.d. Anyways I applied one of the many workarounds suggested, and modprobed vboxdrv and it works fine without having to re-run the setup script. It would be nice if there will be an update to fix this problem.

AFAIK, no update is necessary. It's been mentioned often, you can go to Yast Runlevel Services and start the vboxdrv service, however I only use vbox a few times a day, and I modprobe & rmmod the driver as needed here in my laptop. The driver module needs a recompile each time the kernel upgrades anyway, so this approach seems "safer" to me. None of these gyrations seem to harm the installed winXP vm system, it comes up fine each time (knock on wood). Tom in NM -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wednesday 13 February 2008 03:21:49 am Benji Weber wrote:

On 13/02/2008, 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.

Link to your bug report?

As a work around you can always add vboxdrv to be loaded on each boot

: http://bw.uwcs.co.uk/b/yast_modules_loaded_on_boot_vboxdrv.png

-- Benjamin Weber

I didn't open a bug report, because I didn't know if this was a SUSE related problem or VirtualBox problem.

On Wed, 2008-02-13 at 10:52 +0100, Valerio wrote:

I solved it some months ago running (as root) /etc/init.d/vboxdrv setup just once. It compiled kernel module for vbox (you have to run it every kernel update)

Odd. For both the original poster and for me, one must do this at each reboot. Probably when there is a new kernel as well. Reboots happen often on laptops... -- 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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wednesday 13 February 2008 04:52:25 am Valerio wrote:

2008/2/13, Adam Jimerson :

...

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.

If it wasn't for the fact that I have VirtualBox installed on a laptop instead of a desktop I would take the easy way out and only restart my system for kernel updates. I noticed that along with the kernel update today there was the KMP package and the kernel module package for VirtualBox caught my eye saying that it fixed three problems, none of the three fixes help out in my case. Here is the full error:

VirtualBox - Error Failed to start the virtual machine Ubuntu 7.10. VirtualBox kernel driver not installed. The vboxdrv kernel module was either not loaded or /dev/vboxdrv was not created for some reason. Re-setup the kernel module by executing '/etc/init.d/vboxdrv setup' as root.

VBox status code: -1908 (VERR_VM_DRIVER_NOT_INSTALLED).

Result Code: 0x80004005 Component: Console Interface: IConsole {1dea5c4b-0753-4192-b909-22330f64ec45}

The version of VirtualBox OSE (and related tools/packages) I have installed is: VirtualBox OSE 1.5.2-10.2 VirtualBox-guest-tools 1.5.2-10.2 VirtualBox-kmp-default 1.5.2_2.6.22.17_0.1-10.3 xorg-x11-driver-virtualbox 1.5.2-10.2

Looking at this raises a question about the version numbers, mainly the 10.x part. Does the -10.2 mean that I have 10.2 packages installed for VirtualBox under my 10.3 system? The only OSS repo I have on my system is the 10.3 one, so if I am right on my clueless guess then that means that the only part of VirtualBox that has been packaged for 10.3 is the kmp-default package and this will not have any effect on VirtualBox's over all preformace right?

I solved it some months ago running (as root) /etc/init.d/vboxdrv setup just once. It compiled kernel module for vbox (you have to run it every kernel update)

-- ****************************************************** Valerio Bontempi Blog: http://mithland.wordpress.com/ "... de te querida presencia... comandante..." ******************************************************

I figured that I would, but I am having to run it everytime I restart my laptop which I should not have to do.

Kai Ponte pecked at the keyboard and wrote:

On Tuesday 12 February 2008 10:59:24 pm 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.

Don't know why the devs didn't do this for us, but it is fairly simple.

Administrator Settings (YaST) > System > System Services (runlevel)

Look for vboxdrv in the list. There's an "Enable" button. Click that.

Click Finish and you should be good to go.

Or try insserv vboxdrv from the command line. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wed, 2008-02-13 at 23:43 -0700, 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.)

Pretty much all true. Except that the vboxdrv in SUSE's RPM does not recompile the kernel module when you do a 'setup'. Instead, you get a poorly worded and very misleading message that it says, in effect, that "it will do it, NOT". Some sort of American slang way of simply saying the kernel module will not be remade now. It fooled me as well (an American to boot). But I looked at the script and saw the module is never rebuilt in the setup. Perhaps the original vboxdrv does this. But not SUSE's. I wonder why they felt the need to make this change. 'setup' only exists to do more than 'start'. But now is is pretty much an alias. Why? -- 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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

To summarize and perhaps end this thread about VirtualBox as supplied by SUSE: 1) SUSE's VirtualBox kernel module is not installed in such a way that it is loaded automatically. This is nothing to do with kernel updates. The module is not set up to be loaded automatically. 2) You have two options to remedy this: a) run "/etc/init.d/vboxdrv start" by hand at each system reboot. b) run "insserv vboxdrv" once and be done with it. (Why the RPM does not do this is anybody's guess.) 3) Forget you ever heard of "/etc/init.d/vboxdrv setup". It had no effect on for the SUSE RPM. Be aware that SUSE's "setup" does not do the same as the original VirtualBox "setup". 4) SUSE will (is this not the case?) provide a new VirtualBox driver to match new kernels that they release. Updating one should cause an update of the other automatically.

Tom in NM

Where in NM? I lived a few years in Las Cruces. I loved the place. Even though I left it for Sweden. Go figure. And just try to get a late summer green chili enchilada here... -- 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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Fri, 2008-02-15 at 15:37 -0700, Tom Patton wrote:

On Fri, 2008-02-15 at 12:40 +0100, Roger Oberholtzer wrote:

...

To summarize and perhaps end this thread about VirtualBox as supplied by

In any event, I think we were saying the same things, that the VB site rpm script works, and the suse-site rpm does not. Whichever, it works perfectly adequate for me, and I modprobe as needed. It makes sense for suse to include the module on the upgrade site with a new kernel, but the VB-release handles the re-compile well also... ok...NOW I have updated the kernel in "master", and the opensuse update repo DID provide a new vboxdrv module for the open-source version VB...

(it did not become an auto-load, but I don't want that anyway) So the script from VB WILL recompile their version of the driver, but opensuse (for some reason) wishes to do it themselves and ship it out with the kernel update. Tom in NM -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

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 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Roger Oberholtzer wrote:

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 If that questions for me no, I needed usb support so I only tried the suse one once and then installed the suse 10.3 rpm from http://www.virtualbox.org/wiki/Downloads . Everybody else who has, had no problems. If my kernel changes, it prompts me to run the module installer and restart vbox. Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Tom Patton wrote:

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

Well, I never had to load the kernel module after installing from http://www.virtualbox.org/ (I needed to when installed the package available in the DVD). However, after updating the kernel, you do need to recompile the kernel module. After doing this, I do not know if it would keep loading automatically. Kind regards... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org