Re: Problemi con AndoVM su Virtualbox
Il 08/02/2013 17:17, Alessandro Pellizzari ha scritto:
> Il Fri, 08 Feb 2013 16:47:15 +0100, Portobello ha scritto:
>
>> '/etc/init.d/vboxdrv setup'
>
>> Ho provato a dare il comando (/etc/init.d/vboxdrv setup) da terminale,
>> come root, da mi da' un'altro errore e mi dice che la directory non
>> esiste.
>
> Il tuo problema è qui.
> Senza quei driver compilati correttamente, Virtualbox non supporta la
> rete.
>
> Leggi bene l'errore, guarda i log, e cerca di capire perché non va.
>
> Potrebbero semplicemente mancarti i pacchetti con gli header del kernel
> che stai usando.
>
Ora ho aggiornato il pacchetto virtualbox all'ultima versione 4.2.xxx, e
ho fatto un piccolo passo avanti.
durante l'installazione mi da' questi messaggi :
" sudo dpkg -i virtualbox-4.2_4.2.6-82870~Debian~wheezy_amd64.deb
(Reading database ... 123271 files and directories currently installed.)
Unpacking virtualbox-4.2 (from
virtualbox-4.2_4.2.6-82870~Debian~wheezy_amd64.deb) ...
Setting up virtualbox-4.2 (4.2.6-82870~Debian~wheezy) ...
Installing new version of config file /etc/init.d/vboxdrv ...
Installing new version of config file
/etc/init.d/vboxballoonctrl-service ...
addgroup: The group `vboxusers' already exists as a system group. Exiting.
insserv: script vboxdrv: service vboxdrv already provided!
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
[ ok ] Stopping VirtualBox kernel modules:.
[ ok ] Uninstalling old VirtualBox DKMS kernel modules:.
[....] Trying to register the VirtualBox kernel modules using
DKMS:Error! Your kernel headers for kernel 3.1.0-1-amd64 cannot be found.
Please install the linux-headers-3.1.0-1-amd64 package,
or use the --kernelsourcedir option to tell DKMS where it's located
[FAIL] Failed, trying without DKMS ... failed!
[....] Recompiling VirtualBox kernel modules:
[FAIL] Look at /var/log/vbox-install.log to find out what went wrong ...
failed!
insserv: script vboxdrv: service vboxdrv already provided!
insserv: script vboxdrv: service vboxdrv already provided!
insserv: script vboxdrv: service vboxdrv already provided!
Processing triggers for readahead-fedora ...
Processing triggers for shared-mime-info ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Unknown media type in type 'uri/mms'
Unknown media type in type 'uri/mmst'
Unknown media type in type 'uri/mmsu'
Unknown media type in type 'uri/pnm'
Unknown media type in type 'uri/rtspt'
Unknown media type in type 'uri/rtspu'
Processing triggers for desktop-file-utils ...
Processing triggers for hicolor-icon-theme ...
Processing triggers for python-central ..."
Con apper ho cercato i pacchetti header del mio kernel (
linux-headers-3.1.0-1-amd64 ) ma non ci sono (ho visto solo quelli del
2.6 e del 3.2).
Dopo ho dato il comando da terminale :
sudo /etc/init.d/vboxdrv setup
Come suggerito anche in vari forum, per risolvere il problema.
Ma da' ancora degli errori :
" ok ] Stopping VirtualBox kernel modules:.
[ ok ] Uninstalling old VirtualBox DKMS kernel modules:.
[....] Trying to register the VirtualBox kernel modules using
DKMS:Error! Your kernel headers for kernel 3.1.0-1-amd64 cannot be found.
Please install the linux-headers-3.1.0-1-amd64 package,
or use the --kernelsourcedir option to tell DKMS where it's located
[FAIL] Failed, trying without DKMS ... failed!
[....] Recompiling VirtualBox kernel modules:
[FAIL] Look at /var/log/vbox-install.log to find out what went wrong ...
failed! "
Nel file di log /var/log/vbox-install.log c'e' scritto :
"Uninstalling modules from DKMS
removing old DKMS module vboxhost version 4.2.6
------------------------------
Deleting module version: 4.2.6
completely from the DKMS tree.
------------------------------
Done.
Attempting to install using DKMS
Creating symlink /var/lib/dkms/vboxhost/4.2.6/source ->
/usr/src/vboxhost-4.2.6
DKMS: add completed.
Failed to install using DKMS, attempting to install without
Makefile:181: *** Error: unable to find the sources of your current
Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop."
Ora non so che altro provare?
E dove posso trovare gli headers del mio kernel che e'
uname -a
Linux debian 3.1.0-1-amd64 #1 SMP Tue Jan 10 05:01:58 UTC 2012 x86_64
GNU/Linux
Grazie
Reply to: