Opened 9 years ago
Closed 8 years ago
#14668 closed defect (fixed)
The 5.0.6 RPM x86_64 Package for Fedora 22 is missing /sbin/rcvboxdrv
| Reported by: | Mce128 | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.0.6 |
| Keywords: | rcvboxdrv, missing, x86_64, fedora 22 | Cc: | |
| Guest type: | Windows | Host type: | Linux |
Description
I downloaded the following from the download page earlier today and then installed it.
http://download.virtualbox.org/virtualbox/5.0.6/VirtualBox-5.0-5.0.6_103037_fedora22-1.x86_64.rpm
Naturally, I then proceeded to attempt to build the new kernel module and of course, I found that the /etc/init.d/vboxdrv was missing since--according to the changelog and other documentation and the error message when attempting to run a VM without having rebuild the kernel module--it has been removed and supplanted by /sbin/rcvboxdrv for the purposes of building the kernel module. Well, this would be fine and dandy if not for a wee tiny problem... The aforementioned RPM file did not install /sbin/rcvboxdrv! Nor does it contain that file to be able to do so!
Needless to say, this makes it so that it is completely not possible to access my VMs. The VMs that until I downloaded the update this past afternoon worked beautifully and that one of which happens to contain my TurboTax2014 install. This is a particularly sticky situation as since I filed an extension back in April, my return is due in 9 days now! (the horror! heh) I think it goes without saying that even though I find it exceedingly distasteful to perform that task, it is mandatory that I complete it and due to this latest update, I am completely and thoroughly unable to do so... serious bummer there...
Can you please release a corrected RPM ASAP or even quicker? Maybe travel back in time and fix the RPM prior to its release? Just this once, I won't tell anyone that you'd done it. ;)
Thanks! Joe
Change History (6)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Could you try re-installing the Fedora 22 package? I think that this is a one-off upgrade problem from 5.0.4 to 5.0.6.
comment:3 by , 9 years ago
Or running:
/usr/lib/virtualbox/postinst-common.sh /usr/lib/virtualbox --start
Any feedback appreciated, including "the problem just went away".
comment:5 by , 9 years ago
I would prefer my one from comment 3. That actually invokes vboxdrv.sh setup as one of the things it does.
comment:6 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Hopefully fixed with VBox 5.0.8.
Oh well, I can't edit the original ticket. My reasons for wanting to are twofold. Firstly, to remove much of the extraneous information that I put in there that is of no use toward the remediation of the problem and is more or less just pointless griping on my part and for which I apologize.
Secondly, due to the fact that I just installed the VirtualBox-5.0-5.0.6_103037_fedora18-1.x86_64.rpm package instead of the fedora 22 package and this package, unlike the one in the initial ticket posting, does actually contain the /sbin/rcvboxdrv file. I still had to sign the driver since I am running secure boot, but that is not any real difficulty and just a bit of a diversion in the process of getting the VMs back up and running.
I look forward to the Fedora 22 RPM being fixed so that I can deploy it instead of relying on a build that is targeted to older versions of libraries, et.al.
Thanks again! Joe