On 10/05/2015 03:38 AM, Michael Thayer wrote: > Hello zGreenfelder, > > On 05.10.2015 01:16, zGreenfelder wrote: >> I'm running a centos system, saw an update for virtualbox, loaded it, >> now I'm getting this and unable to start any of my VMs: >> >> [root@nemesis ~]# virtualbox >> WARNING: The vboxdrv kernel module is not loaded. Either there is no module >> available for the current kernel (2.6.32-573.7.1.el6.x86_64) >> or it failed to >> load. Please recompile the kernel module and install it by >> >> sudo /sbin/rcvboxdrv setup >> >> You will not be able to start VMs until this problem is fixed. >> No protocol specified >> Qt WARNING: VirtualBox: cannot connect to X server :1.0 >> [root@nemesis ~]# whereis rcvboxdrv >> rcvboxdrv: >> [root@nemesis ~]# /sbin/rcvboxdrv setup >> -bash: /sbin/rcvboxdrv: No such file or directory >> [root@nemesis ~]# >> >> >> ... so... what's supposed to have the rcvboxdrv program/script/whatever? >> why did this move to /sbin instead of /etc/init.d? anyone have some >> pointers? > I will start with the easiest bit: in these days of systemd, not all > systems have /etc/init.d. If you do then the old script should still > land there (can you check that it is still present on your system?), but > we decided to adopt SUSEs convention (much older than systemd by the > way) of /sbin/rc* in addition, for the others.
all the previous versions of ViI rtualBox landed the script in /etc/init.d, it wasn't there. [root@nemesis /]# find etc -name "*boxdrv" -ls 1724 0 lrwxrwxrwx 1 root root 17 Oct 4 18:54 etc/rc.d/rc2.d/S20vboxdrv -> ../init.d/vboxdrv 1496 0 lrwxrwxrwx 1 root root 17 Oct 4 18:54 etc/rc.d/rc0.d/K80vboxdrv -> ../init.d/vboxdrv 1730 0 lrwxrwxrwx 1 root root 17 Oct 4 18:54 etc/rc.d/rc3.d/S20vboxdrv -> ../init.d/vboxdrv 1763 0 lrwxrwxrwx 1 root root 17 Oct 4 18:54 etc/rc.d/rc5.d/S20vboxdrv -> ../init.d/vboxdrv 1821 0 lrwxrwxrwx 1 root root 17 Oct 4 18:54 etc/rc.d/rc6.d/K80vboxdrv -> ../init.d/vboxdrv 1692 0 lrwxrwxrwx 1 root root 17 Oct 4 18:54 etc/rc.d/rc1.d/K80vboxdrv -> ../init.d/vboxdrv 1757 0 lrwxrwxrwx 1 root root 17 Oct 4 18:54 etc/rc.d/rc4.d/S20vboxdrv -> ../init.d/vboxdrv [root@nemesis /]# I can't run the rpm to grab data any longer; but I do have where I reverted back: [zep@nemesis ~]$ sudo yum downgrade VirtualBox-5.0 Loaded plugins: fastestmirror, refresh-packagekit, security Setting up Downgrade Process Loading mirror speeds from cached hostfile * epel: ftp.cse.buffalo.edu * rpmforge: mirror.team-cymru.org Resolving Dependencies --> Running transaction check ---> Package VirtualBox-5.0.x86_64 0:5.0.4_102546_el6-1 will be a downgrade ---> Package VirtualBox-5.0.x86_64 0:5.0.6_103037_el6-1 will be erased --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Downgrading: VirtualBox-5.0 x86_64 5.0.4_102546_el6-1 virtualbox 72 M Transaction Summary ================================================================================ Downgrade 1 Package(s) Total download size: 72 M Is this ok [y/N]: y Downloading Packages: VirtualBox-5.0-5.0.4_102546_el6-1.x86_64.rpm | 72 MB 00:18 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Installing : VirtualBox-5.0-5.0.4_102546_el6-1.x86_64 1/2 Creating group 'vboxusers'. VM users must be member of that group! No precompiled module for this kernel found -- trying to build one. Messages emitted during module compilation will be logged to /var/log/vbox-install.log. Stopping VirtualBox kernel modules [ OK ] Recompiling VirtualBox kernel modules [ OK ] Starting VirtualBox kernel modules [ OK ] Cleanup : VirtualBox-5.0-5.0.6_103037_el6-1.x86_64 2/2 Verifying : VirtualBox-5.0-5.0.4_102546_el6-1.x86_64 1/2 Verifying : VirtualBox-5.0-5.0.6_103037_el6-1.x86_64 2/2 Removed: VirtualBox-5.0.x86_64 0:5.0.6_103037_el6-1 Installed: VirtualBox-5.0.x86_64 0:5.0.4_102546_el6-1 Complete! > > Could you please give more details of your system and what you did to > upgrade VirtualBox and any additional information that seems useful, > like messages displayed while you were upgrading? I just did a quick > test install on CentOS 6 and everything worked as expected. So it would > help if I understood why your system is different. If you installed > from the RPM package, the output of "rpm -ql VirtualBox-5.0" would be > good to see too. > > Regards, > > Michael I just used yum update to do the upgrade, the system is centos 6, latest patches [root@nemesis Downloads]# cat /etc/yum.repos.d/virtualbox.repo [virtualbox] name=Oracle Linux / RHEL / CentOS-$releasever / $basearch - VirtualBox baseurl=http://download.virtualbox.org/virtualbox/rpm/el/$releasever/$basearch enabled=1 gpgcheck=1 gpgkey=http://download.virtualbox.org/virtualbox/debian/oracle_vbox.asc for my repo -- public gpg key id: AE60F64C ------------------------------------------------------------------------------ _______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe
