Hi Paolo,
Em 28-01-2012 16:49, Paolo De Michele escreveu:
On 01/28/2012 08:18 PM, Steven Stern wrote:
On 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 setup
This 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'.
Dave
the command is not run:
/etc/init.d/vboxdrv setup
bash: /etc/init.d/vboxdrv: No such file or directory
As 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.)
the problem is solved but operating systems do not recognize any
despite this network interface is configured in the settings of
virtualbox
does anyone know help me?
thanks in advance
Suggestion:
]I have the same problem. To get the virtual machine WinVista64
running after a kernel update until we don't have a solution I
uninstall and install the "VirtualBox-OSE.x86_64 4.1.8-2.fc16 "
package, via yum. It works allways.
Bye,
--
Lucélio Gomes de Freitas
ETFCSF=> U.G.F.=> P.U.C.(RJ)
Engº, Analista Suporte(Free Mind).
Email: aa.lucelio@xxxxxxxxx
Tel: 55 0XX 21 85964911
|
--
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
