On 06.10.2015 09:35, Michael Thayer wrote: > Hello All, > > Looking at this now. I think that as a workaround, running > /usr/lib/virtualbox/postinst-common.sh as root should fix this, and that > it should stay fixed after that unless you downgrade VirtualBox.
Correction: /usr/lib/virtualbox/postinst-common.sh /usr/lib/virtualbox --start > Regards, > > Michael > > On 05.10.2015 23:14, thoms wrote: >> Hi Michael, >> >> 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. >>> >>> 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'm also seeing this same behavior and it appears to be an issue with >> the update (vs. install) process in 5.0.6. >> >> After performing a local 'yum update' on a CentOS 6 system (5.0.4 -> >> 5.0.6), I ran into this same problem, so I did some digging: >> >> # rpm -ql VirtualBox-5.0 > vbox-5.0.6 >> # yum downgrade ./VirtualBox-5.0-5.0.4_102546_el6-1.x86_64.rpm >> # rpm -ql VirtualBox-5.0 > vbox-5.0.4 >> # sdiff -b -s -W -w128 vbox-5.0.4 vbox-5.0.6 >> >> /etc/rc.d/init.d/vboxautostart-service < >> /etc/rc.d/init.d/vboxballoonctrl-service < >> /etc/rc.d/init.d/vboxdrv < >> /etc/rc.d/init.d/vboxweb-service < >> /sbin/rcvboxdrv < >> /usr/bin/VBoxSDL < >> /usr/bin/vboxsdl < >> > >> /usr/lib/virtualbox/postinst-common.sh >> > >> /usr/lib/virtualbox/prerm-common.sh >> > >> /usr/lib/virtualbox/routines.sh >> > >> /usr/lib/virtualbox/vboxautostart-service.sh >> > >> /usr/lib/virtualbox/vboxballoonctrl-service.sh >> > >> /usr/lib/virtualbox/vboxdrv.sh >> > >> /usr/lib/virtualbox/vboxweb-service.sh >> /usr/share/doc/VirtualBox-5.0-5.0.4_102546_el6 | >> /usr/share/doc/VirtualBox-5.0-5.0.6_103037_el6 >> /usr/share/doc/VirtualBox-5.0-5.0.4_102546_el6/LICENSE | >> /usr/share/doc/VirtualBox-5.0-5.0.6_103037_el6/LICENSE >> /usr/share/doc/VirtualBox-5.0-5.0.4_102546_el6/UserManual.pdf | >> /usr/share/doc/VirtualBox-5.0-5.0.6_103037_el6/UserManual.pdf >> /usr/share/doc/VirtualBox-5.0-5.0.4_102546_el6/VirtualBox.chm | >> /usr/share/doc/VirtualBox-5.0-5.0.6_103037_el6/VirtualBox.chm >> /usr/src/vboxhost-5.0.4 | >> /usr/src/vboxhost-5.0.6 >> >> >> It appears that the update process fails to create the scripts in >> '/etc/rc.d/init.d/vbox*', so none of this gets started at boot. Of >> course, you won't notice this until the system takes a reboot. >> >> If you fully remove VBox as with: >> >> # yum erase VirtualBox-5.0-5.0.4_102546_el6-1.x86_64' >> >> and then: >> >> # yum install ./VirtualBox-5.0-5.0.6_103037_el6-1.x86_64.rpm >> >> as a clean install (i.e., not an update), then the scripts are created: >> >> # ls /etc/rc.d/init.d/vbox* >> /etc/rc.d/init.d/vboxautostart-service /etc/rc.d/init.d/vboxdrv >> /etc/rc.d/init.d/vboxballoonctrl-service /etc/rc.d/init.d/vboxweb-service >> >> and VBox drivers and services start up as they normally should during >> boot. >> >> -Thom >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> 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 >> > > -- ORACLE Deutschland B.V. & Co. KG Michael Thayer Werkstrasse 24 VirtualBox engineering 71384 Weinstadt, Germany mailto:michael.tha...@oracle.com ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstraße 25, D-80992 München Registergericht: Amtsgericht München, HRA 95603 Komplementärin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Geschäftsführer: Alexander van der Ven, Astrid Kepper, Val Maher ------------------------------------------------------------------------------ _______________________________________________ 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
