Bug 661740

Michal, can you help? I'm quite busy atm

I got the same on 11.2 with the repository http://download.opensuse.org/repositories/Virtualization:/VirtualBox_backports/openSUSE_11.2_Update/ and something similar with Oracle's http://download.virtualbox.org/virtualbox/rpm/opensuse/11.2/

However, at one point it was running. Basically what got me there was a combination of installing and uninstalling packages, starting and stopping VirtualBox 4, rebooting, and running "/etc/init.d/vboxdrv setup". Unfortunately I don't remember exactly what I did and after running "/etc/init.d/vboxdrv setup" once more, I was unable to use VB4.

I couldn't find /usr/share/virtualbox/src in the OSB repository. There are vboxdrv sources in the Oracle-provided rpm, but they don't compile and I didn't have the time to figure out why.

Hi Rainer,

you can't build host's vbox kernel modules, if you have installed virtualbox from openSUSE repo, you should be informed about this after entering /etc/init.d/vboxdrv setup - and here is the bug I oversight this patch during switch to vbox 4.0.0, I will push this message to vboxdrv init script back

thanks for report!

(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.13)
> Gecko/20101203 SUSE/3.6.13-3.1 Firefox/3.6.13
> 
> After having installed VirtualBox the command '/etc/init.d/vboxdrv setup' must
> be run as root. However, this fails with the following output:
> 
> Stopping VirtualBox kernel modules                                             
>                                                                           done
> Uninstalling old VirtualBox DKMS kernel modules/etc/init.d/vboxdrv: line 278:
> /usr/share/virtualbox/src/vboxhost/do_dkms: No such file or directory
>                                                                                
>                                                                           done
> Removing old VirtualBox netadp kernel module                                   
>                                                                           done
> Removing old VirtualBox netflt kernel module                                   
>                                                                           done
> Removing old VirtualBox kernel module                                          
>                                                                           done
> Trying to register the VirtualBox kernel modules using DKMS/etc/init.d/vboxdrv:
> line 296: /usr/share/virtualbox/src/vboxhost/do_dkms: No such file or directory
>                                                                                
>                                                                          
> failed
>   (Failed, trying without DKMS)
> Recompiling VirtualBox kernel modules                                          
>                                                                          
> failed
>   (Look at /var/log/vbox-install.log to find out what went wrong)
> 
> 
> The file /var/log/vbox-install.log contains the following:
> 
> /etc/init.d/vboxdrv: line 300:
> /usr/share/virtualbox/src/vboxhost/vboxdrv/build_in_tmp: No such file or
> directory
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> See above.
> Actual Results:  
> See above.
> 
> Expected Results:  
> See above.
> 
> I tried this with the following VirtualBox versions:
> - 3.9.80-145.1
> - 4.0.0-11.1
> 
> And I tried both VB versions under these operating systems:
> - openSUSE 11.2 on an x86_64 machine
> - openSUSE 11.4 M5 on an i586 machine

Hm, well, but how can I start VirtualBox then? Doing an "/etc/init.d/vboxdrv start" results in the following message:

Starting VirtualBox kernel modules                    failed
  (modprobe vboxnetflt failed. Please use 'dmesg' to find out why)

And dmesg says:

[207068.321394] vboxdrv: Found 2 processor cores.
[207068.321468] VBoxDrv: dbg - g_abExecMemory=ffffffffa1330300
[207068.321526] vboxdrv: fAsync=0 offMin=0x1d1 offMax=0xe4ab
[207068.321578] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
[207068.321585] vboxdrv: Successfully loaded version 4.0.0_OSE (interface 0x00160000).
[207068.619557] vboxguest: exports duplicate symbol RTMemFreeEx (owned by vboxdrv)

However, trying to insert vboxnetflt manually, i.e. with "modprobe vboxnetflt", leads to this message:

FATAL: Error inserting vboxnetflt (/lib/modules/2.6.31.14-0.6-default/updates/vboxnetflt.ko): Invalid module format

All this happens under openSUSE 11.2 with kernel 2.6.31.14-0.6-default. (I currently cannot test VirtualBox under openSUSE 11.4 M5.)

ah, you have both the host and the guest drivers installed. please deinstall the guest kmps.

Yeah, thanks a lot, that did it! I suggest to do some packaging magic in order to inhibit the installation of conflicting packages.

hm  ... we have to put conflicts between host-kmp and guest-kmp packages, but firstly we have to fix liveCD installation process - it doesn't distinguish between host or guest system and install always only vbox guest packages see bnc#615835

I let bug opened + rename to "insert conflicts between host-kmp and guest-kmp vbox packages"

I'm talking about the version 4.0.0-15.1 from http://download.opensuse.org/repositories/Virtualization:/VirtualBox_backports/openSUSE_11.2_Update/ for 11.2. Here's what I did to make it work:

1) I installed virtualbox, virtualbox-host-kmp-default, virtualbox-qt and no other VB packages.

2) After that, there were some symlinks in /lib/modules/2.6.31.14-0.6-default/weak-updates/updates/ pointing to inexistent kernel dir /lib/modules/2.6.31.8-0.1-default/updates. So I replaced those symlinks with symlinks to /lib/modules/2.6.31.14-0.6-default/updates/ .

3) I ran "depmod -a"

(All these were done as root.)


Now I see there is a newer version, 4.0.0-18.1. Maybe this fixes the symlinks issue, but since what I have now works fine, I'm not willing to try it until I made a full backup.

The solution proposed by Dirk in comment #6, solved the problem for me to.  I just upgraded from OS_11.2 to OS_11.4

As 11.2 is out of support we are closing this bug as wontfix due to the complexity of reproduction.

Please open a new issue if you are still seeing the problem on current releases.