On 01/28/2012 08:18 PM, Steven Stern wrote: the problem is solved but operating systems do not recognize any despite this network interface is configured in the settings of virtualboxOn 01/28/2012 01:07 PM, Paolo De Michele wrote:On 01/28/2012 07:54 PM, Dave Ulrick wrote:On Sat, 28 Jan 2012, Paolo De Michele wrote:the other time I solved with the following command: /sbin/service vboxdrv setup the output is: Redirecting to /bin/systemctl setup vboxdrv.service Unknown operation setupThis is most likely happening due to the new 'systemd' feature that's been added to Fedora. To get around it, try running the vboxdrv init script directly like this: # /etc/init.d/vboxdrv setup You might consider installing the 'dkms' package ('yum install dkms'). This will automatically rebuild the VirtualBox kernel modules whenever you install a new kernel RPM, making it unnecessary to run 'vboxdrv setup'. Davethe command is not run: /etc/init.d/vboxdrv setup bash: /etc/init.d/vboxdrv: No such file or directoryAs a workaround, consider uninstalling the OSE package and install the the Fedora repository from here: https://www.virtualbox.org/wiki/Linux_Downloads (Scroll down to the bottom to get to the installation instructions for the repository.) does anyone know help me? thanks in advance |
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org