I’m using the VirtualBox since a while and was quite happy with it. But I yesterday tried to somehow share my printer over Samba on the LAN. That’s when the fun was over: Next time I tried to start VirtualBox the"jumping loading appplication" mouse pointer appeared and after some seconds … the normal mouse pointer came back and … nothing … no error message … simply nothing. As if I never have treid to start the virtual box. So I had the idea to look in the systgem log. Open Yast and System Log and … had simply no idea which message was relevant in this context.
So I decided to unstill the VirtualBox, reboot, install it again and reboot and … still the same problem. Seems as if the uninstall does not really clean everything as it should do …
Started to find information on the internet and found the hint to use dmesg. Got lots of information and several ideas what might be important for me to solve this problem. But this puzzle also did not lead to a solution.
How can I clean old remains of the virtualbox and make a clean new installation ?
And if virtualbox has a problem during the installation - how can I know what it is ?
Or is it better/easier/faster to reinstall Opensuse 13.1 ?
Try to run it in a terminal window. Do you get an error message?
VirtualBox
PS: Uninstalling/reinstalling will only remove/readd the files contained in the packages. Other stuff like the configuration or the VMs itself will not be altered.
Those are found by default in ~/.VirtualBox/ and “~/VirtualBox VMs/”.
You may want to try to rename the ~/.VirtualBox/ folder to do a fresh start. But I actually doubt that the configuration is at fault here.
VirtualBox in the konsole does not work, nor does vbox. And su does not help as well
The systems answers:
“If ‘VirtualBox’ is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf VirtualBox”
Frankly said, I have no idea where Yast2 takes the packages from, what method/stratregy it uses is to handle the instll/uninstall of software.
Currently it suggests to install virtualbox and virtualbox-host-kmp-desktop, which is less than It did 4 months ago. But at this time it was still OS 12.3, so I though, maybe things have changed slightly and 2 files are sufficient. May it makes sense to chosse alll files which contain a virtualbox string in their name …
I used Windows as from WfW 3.11 until now Win7 and my Linux knowledge/experience is now around 4 month old. I develope software with IBM lotus Notes and Eclipse. And made last year the big jump to Linux. And its a big jump indeed, but I’m still able to learn
Have overseen the rpm line. Here is the result:
rpm -qa | grep -i virtualbox
virtualbox-host-kmp-desktop-4.3.6_k3.11.6_4-108.7.x86_64
virtualbox-4.3.6-108.7.x86_64
Please uninstall “vboxgtk” and install “virtualbox-qt” instead, that’s the official GUI. “vboxgtk” doesn’t really work with recent VirtualBox versions (although it should at least start though)
According to Google this could point to a permissions issue in the /tmp directory.
And this most probably happened because you tried to run VirtualBox as root. (this is never a good idea)
This is what I get in the Yast2->System Log whe nI try to start teh VirtualBox:
kernel: 7988.964348] warning: `VirtualBox’ uses 32-bit capabilities (legacy support in use)
2014-01-31T13:30:01.258886+01:00 Hasty /usr/sbin/cron[5936]: pam_unix(crond:session): session opened for user root by (uid=0)
2014-01-31T13:30:01.262953+01:00 Hasty systemd[1]: Starting Session 11 of user root.
2014-01-31T13:30:01.263667+01:00 Hasty systemd[1]: Started Session 11 of user root.
2014-01-31T13:30:01.293999+01:00 Hasty /USR/SBIN/CRON[5936]: pam_unix(crond:session): session closed for user root
2014-01-31T13:39:49.160446+01:00 Hasty su: (to joe) joe on none
2014-01-31T13:39:49.161245+01:00 Hasty su: pam_unix(su:session): session opened for user root by (uid=1000)
2014-01-31T13:39:49.163215+01:00 Hasty su: pam_systemd(su:session): pam_putenv: delete non-existent entry; XDG_RUNTIME_DIR
Unfortunately I run now into an error when I try to start a virtual machine:
Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing
‘/etc/init.d/vboxdrv setup’
as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.
Although I installed the DKMS package, as requested trying this “vboxdrv setup” as user and afterwards as su does not work. The system says: Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing
‘/etc/init.d/vboxdrv setup’
as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.
So I installed the DKMS package and then I tried ‘/etc/init.d/vboxdrv setup’ as su: “su: user /etc/init.d/vboxdrv does not exist” As user I hvae no right to access this subdir / file
1.
uname -a
Linux Hasty 3.11.6-4-desktop #1 SMP PREEMPT Wed Oct 30 18:04:56 UTC 2013 (e6d4a27) x86_64 x86_64 x86_64 GNU/Linux
**2. **
joe@Hasty:~> sudo zypper in -f virtualbox-host-kmp-desktop
root’s password:
Loading repository data…
Reading installed packages…
Forcing installation of ‘virtualbox-host-kmp-desktop-4.3.6_k3.11.6_4-108.7.x86_64’ from repository ‘openSUSE BuildService - Virtualization (VirtualBox)’.
Resolving package dependencies…
The following package is going to be reinstalled:
virtualbox-host-kmp-desktop-4.3.6_k3.11.6_4-108.7
1 package to reinstall.
Overall download size: 273.7 KiB. No additional space will be used or freed after the operation.
Continue? [y/n/? shows all options] (y): y
Retrieving package virtualbox-host-kmp-desktop-4.3.6_k3.11.6_4-108.7.x86_64 (1/1), 273.7 KiB (578.7 KiB unpacked)
Retrieving: virtualbox-host-kmp-desktop-4.3.6_k3.11.6_4-108.7.x86_64.rpm …[done]
(1/1) Installing: virtualbox-host-kmp-desktop-4.3.6_k3.11.6_4-108.7 …[done]
Additional rpm output:
WARNING: Can’t read module /lib/modules/3.11.6-4-desktop/weak-updates/updates/vboxvideo.ko: No such file or directory
WARNING: Can’t read module /lib/modules/3.11.6-4-desktop/weak-updates/updates/vboxsf.ko: No such file or directory
WARNING: Can’t read module /lib/modules/3.11.6-4-desktop/weak-updates/updates/vboxguest.ko: No such file or directory
**
3.**
joe@Hasty:~> sudo systemctl status vboxdrv.service
vboxdrv.service - LSB: VirtualBox Linux module
Loaded: loaded (/etc/init.d/vboxdrv)
Active: active (exited) since Fri 2014-01-31 14:21:09 CET; 7min ago
Process: 854 ExecStart=/etc/init.d/vboxdrv start (code=exited, status=0/SUCCESS)
Jan 31 14:21:09 Hasty systemd[1]: Starting LSB: VirtualBox Linux module…
Jan 31 14:21:09 Hasty vboxdrv[854]: WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
Jan 31 14:21:09 Hasty vboxdrv[854]: Starting VirtualBox kernel modules…done
Jan 31 14:21:09 Hasty systemd[1]: Started LSB: VirtualBox Linux module.
ls -l /lib/modules/3.11.6-4desktop/weak-updates/updates /lib/modules/3.11.6-4-desktop/updates/
Maybe try to completely remove the KMP and install it again:
sudo zypper rm virtualbox-host-kmp-desktop
sudo zypper in virtualbox-host-kmp-desktop
Run this afterwards to reload the kernel module (or reboot):
sudo systemctl restart vboxdrv.service
[Update]: But they are link files
[Update]: The links point to lib/modules/3.11.6-4desktop/updates/ where the files indeed do exist.
That’s normal, that’s how openSUSE’s weak-update stuff works.
It’s done this way that you don’t have to install the matching KMP package for every installed kernel.
The kernel module is installed somewhere instead, and a link is created for every installed kernel.
And another thing:
Jan 31 14:21:09 Hasty vboxdrv[854]: WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
Why do you have an /etc/modprobe.conf? What’s in there?
As the message implies, you should better remove it and use files in /etc/modprobe.conf.d/ instead.
Have copied the modprobe.conf into the subdir modprobe.d. I assume that this file was created while I was trying to make the Samba shares for the printer (still does not work, but this is another topic)
And finally the requested ls :
joe@Hasty:~> ls -l /lib/modules/3.11.6-4desktop/weak-updates/updates /lib/modules/3.11.6-4-desktop/updates/
ls: cannot access /lib/modules/3.11.6-4desktop/weak-updates/updates: No such file or directory
/lib/modules/3.11.6-4-desktop/updates/:
total 588
-rw-r–r-- 1 root root 505160 Jan 24 22:03 vboxdrv.ko
-rw-r–r-- 1 root root 14384 Jan 24 22:03 vboxnetadp.ko
-rw-r–r-- 1 root root 37600 Jan 24 22:03 vboxnetflt.ko
-rw-r–r-- 1 root root 35400 Jan 24 22:03 vboxpci.ko
Can you post the content of that file?
I can’t believe that you would need a modprobe.conf for a printer samba share.
And finally the requested ls :
joe@Hasty:~> ls -l /lib/modules/3.11.6-4desktop/weak-updates/updates /lib/modules/3.11.6-4-desktop/updates/
ls: cannot access /lib/modules/3.11.6-4desktop/weak-updates/updates: No such file or directory
You left out a ‘-’, the directory is called /lib/modules/3.11.6-4-desktop/weak-updates/updates.
But that doesn’t matter anymore anyway, since it it working now…
