Nie jesteś zalogowany.
Jeśli nie posiadasz konta, zarejestruj je już teraz! Pozwoli Ci ono w pełni korzystać z naszego serwisu. Spamerom dziękujemy!
Ogłoszenie
Prosimy o pomoc dla małej Julki — przekaż 1% podatku na Fundacji Dzieciom zdazyć z Pomocą.
Więcej informacji na dug.net.pl/pomagamy/.
- Forum Debian Users Gang
- » Software
- » Virtualbox uruchomienie maszyny wirtualnej (vboxdrv)
#26 2015-06-04 19:32:15
ilin - 
Palacz
- ilin
- Palacz
- Skąd: PRLu
- Zarejestrowany: 2006-05-03
Re: Virtualbox uruchomienie maszyny wirtualnej (vboxdrv)
To do kompletu pokaż jeszcze
Kod:
uname -a
Offline
#27 2015-06-04 20:54:20
mike26 - Użytkownik
- mike26
- Użytkownik
- Skąd: ~/
- Zarejestrowany: 2013-10-16
Re: Virtualbox uruchomienie maszyny wirtualnej (vboxdrv)
Kod:
uname -a Linux debian 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24) x86_64 GNU/Linux
Offline
#28 2015-06-04 20:54:22
Yampress - Imperator
- Yampress
- Imperator
- Zarejestrowany: 2007-10-18
Re: Virtualbox uruchomienie maszyny wirtualnej (vboxdrv)
kernel-kbuild jeszcze ...
Offline
#29 2015-06-04 21:27:39
mike26 - Użytkownik
- mike26
- Użytkownik
- Skąd: ~/
- Zarejestrowany: 2013-10-16
Re: Virtualbox uruchomienie maszyny wirtualnej (vboxdrv)
Sorry ale nie rozumie o co chodzi z kernel-kbuild tzn. system nie rozpoznaje takiego polecenia
w repo znalazłem kbuild oraz linux-kbuild-3.16
Ostatnio edytowany przez mike26 (2015-06-04 21:32:15)
Offline
#30 2015-06-04 21:28:26
mati75 - Psuj
- mati75
- Psuj
- Skąd: masz ten towar?
- Zarejestrowany: 2010-03-14
Re: Virtualbox uruchomienie maszyny wirtualnej (vboxdrv)
Powinno pociągnąć z zależnościami do nagłówków.
Offline
#31 2015-06-05 11:10:42
mike26 - Użytkownik
- mike26
- Użytkownik
- Skąd: ~/
- Zarejestrowany: 2013-10-16
Re: Virtualbox uruchomienie maszyny wirtualnej (vboxdrv)
Usunąłem Virtualbox'a i zainstalowałem Vmware
http://www.4shared.com/photo/akdibJgCce/vmware.html
Po uruchomieniu pojawia się następny błąd
Kod:
cat /tmp/vmware-root/vmware-5919.log 2015-06-05T10:51:21.576+02:00| vthread-4| I120: Log for VMware Workstation pid=5919 version=11.1.0 build=build-2496824 option=Release 2015-06-05T10:51:21.576+02:00| vthread-4| I120: The process is 64-bit. 2015-06-05T10:51:21.576+02:00| vthread-4| I120: Host codepage=UTF-8 encoding=UTF-8 2015-06-05T10:51:21.576+02:00| vthread-4| I120: Host is Linux 3.16.0-4-amd64 Debian GNU/Linux 8.0 (jessie) 2015-06-05T10:51:21.576+02:00| vthread-4| I120: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": Nie ma takiego pliku ani katalogu. 2015-06-05T10:51:21.576+02:00| vthread-4| I120: Msg_Reset: 2015-06-05T10:51:21.576+02:00| vthread-4| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": Nie ma takiego pliku ani katalogu. 2015-06-05T10:51:21.576+02:00| vthread-4| I120: ---------------------------------------- 2015-06-05T10:51:21.576+02:00| vthread-4| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values. 2015-06-05T10:51:21.576+02:00| vthread-4| I120: DictionaryLoad: Cannot open file "/home/wojtek/.vmware/config": Nie ma takiego pliku ani katalogu. 2015-06-05T10:51:21.576+02:00| vthread-4| I120: Msg_Reset: 2015-06-05T10:51:21.576+02:00| vthread-4| I120: [msg.dictionary.load.openFailed] Cannot open file "/home/wojtek/.vmware/config": Nie ma takiego pliku ani katalogu. 2015-06-05T10:51:21.576+02:00| vthread-4| I120: ---------------------------------------- 2015-06-05T10:51:21.576+02:00| vthread-4| I120: PREF Optional preferences file not found at /home/wojtek/.vmware/config. Using default values. 2015-06-05T10:51:21.576+02:00| vthread-4| I120: PREF Unable to check permissions for preferences file. 2015-06-05T10:51:21.576+02:00| vthread-4| I120: DictionaryLoad: Cannot open file "/home/wojtek/.vmware/preferences": Nie ma takiego pliku ani katalogu. 2015-06-05T10:51:21.576+02:00| vthread-4| I120: Msg_Reset: 2015-06-05T10:51:21.576+02:00| vthread-4| I120: [msg.dictionary.load.openFailed] Cannot open file "/home/wojtek/.vmware/preferences": Nie ma takiego pliku ani katalogu. 2015-06-05T10:51:21.576+02:00| vthread-4| I120: ---------------------------------------- 2015-06-05T10:51:21.576+02:00| vthread-4| I120: PREF Failed to load user preferences. 2015-06-05T10:51:21.596+02:00| vthread-4| W110: Logging to /tmp/vmware-root/vmware-5919.log 2015-06-05T10:51:21.612+02:00| vthread-4| I120: Obtaining info using the running kernel. 2015-06-05T10:51:21.612+02:00| vthread-4| I120: Created new pathsHash. 2015-06-05T10:51:21.612+02:00| vthread-4| I120: Setting header path for 3.16.0-4-amd64 to "/lib/modules/3.16.0-4-amd64/build/include". 2015-06-05T10:51:21.612+02:00| vthread-4| I120: Validating path "/lib/modules/3.16.0-4-amd64/build/include" for kernel release "3.16.0-4-amd64". 2015-06-05T10:51:21.612+02:00| vthread-4| I120: Failed to find /lib/modules/3.16.0-4-amd64/build/include/linux/version.h 2015-06-05T10:51:21.612+02:00| vthread-4| I120: /lib/modules/3.16.0-4-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2015-06-05T10:51:21.612+02:00| vthread-4| I120: using /usr/bin/gcc-4.8 for preprocess check 2015-06-05T10:51:21.617+02:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.16.0-4-amd64". 2015-06-05T10:51:21.617+02:00| vthread-4| I120: The header path "/lib/modules/3.16.0-4-amd64/build/include" for the kernel "3.16.0-4-amd64" is valid. Whoohoo! 2015-06-05T10:51:21.675+02:00| vthread-4| I120: found symbol version file /lib/modules/3.16.0-4-amd64/build/Module.symvers 2015-06-05T10:51:21.675+02:00| vthread-4| I120: Reading symbol versions from /lib/modules/3.16.0-4-amd64/build/Module.symvers. 2015-06-05T10:51:21.692+02:00| vthread-4| I120: Read 16472 symbol versions 2015-06-05T10:51:21.692+02:00| vthread-4| I120: Reading in info for the vmmon module. 2015-06-05T10:51:21.692+02:00| vthread-4| I120: Reading in info for the vmnet module. 2015-06-05T10:51:21.692+02:00| vthread-4| I120: Reading in info for the vmblock module. 2015-06-05T10:51:21.692+02:00| vthread-4| I120: Reading in info for the vmci module. 2015-06-05T10:51:21.692+02:00| vthread-4| I120: Reading in info for the vsock module. 2015-06-05T10:51:21.692+02:00| vthread-4| I120: Setting vsock to depend on vmci. 2015-06-05T10:51:21.692+02:00| vthread-4| I120: Invoking modinfo on "vmmon". 2015-06-05T10:51:21.694+02:00| vthread-4| I120: "/sbin/modinfo" exited with status 256. 2015-06-05T10:51:21.694+02:00| vthread-4| I120: Invoking modinfo on "vmnet". 2015-06-05T10:51:21.695+02:00| vthread-4| I120: "/sbin/modinfo" exited with status 256. 2015-06-05T10:51:21.695+02:00| vthread-4| I120: Invoking modinfo on "vmblock". 2015-06-05T10:51:21.697+02:00| vthread-4| I120: "/sbin/modinfo" exited with status 256. 2015-06-05T10:51:21.697+02:00| vthread-4| I120: Invoking modinfo on "vmci". 2015-06-05T10:51:21.698+02:00| vthread-4| I120: "/sbin/modinfo" exited with status 256. 2015-06-05T10:51:21.698+02:00| vthread-4| I120: Invoking modinfo on "vsock". 2015-06-05T10:51:21.700+02:00| vthread-4| I120: "/sbin/modinfo" exited with status 0. 2015-06-05T10:51:21.709+02:00| vthread-4| I120: to be installed: vmmon status: 0 2015-06-05T10:51:21.709+02:00| vthread-4| I120: to be installed: vmnet status: 0 2015-06-05T10:51:21.717+02:00| vthread-4| I120: Obtaining info using the running kernel. 2015-06-05T10:51:21.717+02:00| vthread-4| I120: Setting header path for 3.16.0-4-amd64 to "/lib/modules/3.16.0-4-amd64/build/include". 2015-06-05T10:51:21.717+02:00| vthread-4| I120: Validating path "/lib/modules/3.16.0-4-amd64/build/include" for kernel release "3.16.0-4-amd64". 2015-06-05T10:51:21.717+02:00| vthread-4| I120: Failed to find /lib/modules/3.16.0-4-amd64/build/include/linux/version.h 2015-06-05T10:51:21.717+02:00| vthread-4| I120: /lib/modules/3.16.0-4-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2015-06-05T10:51:21.717+02:00| vthread-4| I120: using /usr/bin/gcc-4.8 for preprocess check 2015-06-05T10:51:21.722+02:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.16.0-4-amd64". 2015-06-05T10:51:21.722+02:00| vthread-4| I120: The header path "/lib/modules/3.16.0-4-amd64/build/include" for the kernel "3.16.0-4-amd64" is valid. Whoohoo! 2015-06-05T10:51:21.782+02:00| vthread-4| I120: found symbol version file /lib/modules/3.16.0-4-amd64/build/Module.symvers 2015-06-05T10:51:21.782+02:00| vthread-4| I120: Reading symbol versions from /lib/modules/3.16.0-4-amd64/build/Module.symvers. 2015-06-05T10:51:21.798+02:00| vthread-4| I120: Read 16472 symbol versions 2015-06-05T10:51:21.799+02:00| vthread-4| I120: Kernel header path retrieved from FileEntry: /lib/modules/3.16.0-4-amd64/build/include 2015-06-05T10:51:21.799+02:00| vthread-4| I120: Update kernel header path to /lib/modules/3.16.0-4-amd64/build/include 2015-06-05T10:51:21.799+02:00| vthread-4| I120: Validating path "/lib/modules/3.16.0-4-amd64/build/include" for kernel release "3.16.0-4-amd64". 2015-06-05T10:51:21.799+02:00| vthread-4| I120: Failed to find /lib/modules/3.16.0-4-amd64/build/include/linux/version.h 2015-06-05T10:51:21.799+02:00| vthread-4| I120: /lib/modules/3.16.0-4-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2015-06-05T10:51:21.799+02:00| vthread-4| I120: using /usr/bin/gcc-4.8 for preprocess check 2015-06-05T10:51:21.804+02:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.16.0-4-amd64". 2015-06-05T10:51:21.804+02:00| vthread-4| I120: The header path "/lib/modules/3.16.0-4-amd64/build/include" for the kernel "3.16.0-4-amd64" is valid. Whoohoo! 2015-06-05T10:51:21.806+02:00| vthread-4| I120: Found compiler at "/usr/bin/gcc" 2015-06-05T10:51:21.809+02:00| vthread-4| I120: Got gcc version "4.9.2". 2015-06-05T10:51:21.809+02:00| vthread-4| I120: GCC minor version 4 does not match Kernel GCC minor version 4. But that is ok. 2015-06-05T10:51:21.809+02:00| vthread-4| I120: Using user supplied compiler "/usr/bin/gcc". 2015-06-05T10:51:21.812+02:00| vthread-4| I120: Got gcc version "4.9.2". 2015-06-05T10:51:21.812+02:00| vthread-4| I120: GCC minor version 4 does not match Kernel GCC minor version 4. But that is ok. 2015-06-05T10:51:21.822+02:00| vthread-4| I120: Trying to find a suitable PBM set for kernel "3.16.0-4-amd64". 2015-06-05T10:51:21.822+02:00| vthread-4| I120: No matching PBM set was found for kernel "3.16.0-4-amd64". 2015-06-05T10:51:21.822+02:00| vthread-4| I120: GCC minor version 4 does not match Kernel GCC minor version 4. But that is ok. 2015-06-05T10:51:21.822+02:00| vthread-4| I120: Validating path "/lib/modules/3.16.0-4-amd64/build/include" for kernel release "3.16.0-4-amd64". 2015-06-05T10:51:21.823+02:00| vthread-4| I120: Failed to find /lib/modules/3.16.0-4-amd64/build/include/linux/version.h 2015-06-05T10:51:21.823+02:00| vthread-4| I120: /lib/modules/3.16.0-4-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2015-06-05T10:51:21.823+02:00| vthread-4| I120: using /usr/bin/gcc-4.8 for preprocess check 2015-06-05T10:51:21.829+02:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.16.0-4-amd64". 2015-06-05T10:51:21.829+02:00| vthread-4| I120: The header path "/lib/modules/3.16.0-4-amd64/build/include" for the kernel "3.16.0-4-amd64" is valid. Whoohoo! 2015-06-05T10:51:21.831+02:00| vthread-4| I120: GCC minor version 4 does not match Kernel GCC minor version 4. But that is ok. 2015-06-05T10:51:21.831+02:00| vthread-4| I120: Validating path "/lib/modules/3.16.0-4-amd64/build/include" for kernel release "3.16.0-4-amd64". 2015-06-05T10:51:21.831+02:00| vthread-4| I120: Failed to find /lib/modules/3.16.0-4-amd64/build/include/linux/version.h 2015-06-05T10:51:21.831+02:00| vthread-4| I120: /lib/modules/3.16.0-4-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2015-06-05T10:51:21.831+02:00| vthread-4| I120: using /usr/bin/gcc-4.8 for preprocess check 2015-06-05T10:51:21.837+02:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.16.0-4-amd64". 2015-06-05T10:51:21.837+02:00| vthread-4| I120: The header path "/lib/modules/3.16.0-4-amd64/build/include" for the kernel "3.16.0-4-amd64" is valid. Whoohoo! 2015-06-05T10:51:21.837+02:00| vthread-4| I120: Using temp dir "/tmp". 2015-06-05T10:51:21.839+02:00| vthread-4| I120: Obtaining info using the running kernel. 2015-06-05T10:51:21.839+02:00| vthread-4| I120: Setting header path for 3.16.0-4-amd64 to "/lib/modules/3.16.0-4-amd64/build/include". 2015-06-05T10:51:21.839+02:00| vthread-4| I120: Validating path "/lib/modules/3.16.0-4-amd64/build/include" for kernel release "3.16.0-4-amd64". 2015-06-05T10:51:21.839+02:00| vthread-4| I120: Failed to find /lib/modules/3.16.0-4-amd64/build/include/linux/version.h 2015-06-05T10:51:21.839+02:00| vthread-4| I120: /lib/modules/3.16.0-4-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2015-06-05T10:51:21.839+02:00| vthread-4| I120: using /usr/bin/gcc-4.8 for preprocess check 2015-06-05T10:51:21.844+02:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.16.0-4-amd64". 2015-06-05T10:51:21.844+02:00| vthread-4| I120: The header path "/lib/modules/3.16.0-4-amd64/build/include" for the kernel "3.16.0-4-amd64" is valid. Whoohoo! 2015-06-05T10:51:21.927+02:00| vthread-4| I120: found symbol version file /lib/modules/3.16.0-4-amd64/build/Module.symvers 2015-06-05T10:51:21.927+02:00| vthread-4| I120: Reading symbol versions from /lib/modules/3.16.0-4-amd64/build/Module.symvers. 2015-06-05T10:51:21.947+02:00| vthread-4| I120: Read 16472 symbol versions 2015-06-05T10:51:21.947+02:00| vthread-4| I120: Invoking modinfo on "vmmon". 2015-06-05T10:51:21.949+02:00| vthread-4| I120: "/sbin/modinfo" exited with status 256. 2015-06-05T10:51:21.949+02:00| vthread-4| I120: Invoking modinfo on "vmnet". 2015-06-05T10:51:21.951+02:00| vthread-4| I120: "/sbin/modinfo" exited with status 256. 2015-06-05T10:51:22.332+02:00| vthread-4| I120: Setting destination path for vmmon to "/lib/modules/3.16.0-4-amd64/misc/vmmon.ko". 2015-06-05T10:51:22.332+02:00| vthread-4| I120: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar". 2015-06-05T10:51:22.338+02:00| vthread-4| I120: Successfully extracted the vmmon source. 2015-06-05T10:51:22.338+02:00| vthread-4| I120: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-ZiVA89/vmmon-only auto-build HEADER_DIR=/lib/modules/3.16.0-4-amd64/build/include CC=/usr/bin/gcc IS_GCC_3=no" 2015-06-05T10:51:24.152+02:00| vthread-4| W110: Failed to build vmmon. Failed to execute the build command. 2015-06-05T10:51:24.155+02:00| vthread-4| I120: Setting destination path for vmnet to "/lib/modules/3.16.0-4-amd64/misc/vmnet.ko". 2015-06-05T10:51:24.155+02:00| vthread-4| I120: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar". 2015-06-05T10:51:24.161+02:00| vthread-4| I120: Successfully extracted the vmnet source. 2015-06-05T10:51:24.161+02:00| vthread-4| I120: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-ZiVA89/vmnet-only auto-build HEADER_DIR=/lib/modules/3.16.0-4-amd64/build/include CC=/usr/bin/gcc IS_GCC_3=no" 2015-06-05T10:51:25.734+02:00| vthread-4| W110: Failed to build vmnet. Failed to execute the build command.
Kod:
/etc/init.d/vmware restart Stopping VMware services: VMware Authentication Daemon done VM communication interface socket family done Virtual machine communication interface done Virtual machine monitor done Blocking file system done Starting VMware services: Virtual machine monitor failed Virtual machine communication interface done VM communication interface socket family done Blocking file system done Virtual ethernet failed VMware Authentication Daemon done
Offline
#32 2015-06-05 11:15:39
Pavlo950 - człowiek pasjonat :D
#33 2015-06-05 11:20:40
mike26 - Użytkownik
- mike26
- Użytkownik
- Skąd: ~/
- Zarejestrowany: 2013-10-16
Re: Virtualbox uruchomienie maszyny wirtualnej (vboxdrv)
tak
mati75 napisał(-a):
Powinno pociągnąć z zależnościami do nagłówków.
To, może mieć związek z błędem który miałem jakiś czas temu. Otóż zainstalowane programy mogłem uruchomić z "menu programów" jednak z terminalu już nie, nie wykrywało takiego polecenia.
Programy/pakiety zainstalowane w systemie których nie można uruchomić
Nie rozwiązałem tego, po prostu ponownie zainstalowałem programy których nie mogłem uruchomić w terminalu.
Ostatnio edytowany przez mike26 (2015-06-05 11:30:07)
Offline
#34 2015-06-05 11:48:07
mati75 - Psuj
- mati75
- Psuj
- Skąd: masz ten towar?
- Zarejestrowany: 2010-03-14
Re: Virtualbox uruchomienie maszyny wirtualnej (vboxdrv)
Wygląda jakby partycja była uszkodzona albo filesystem, bo zmiany nie są wprowadzane.
Offline
#35 2015-06-05 12:01:53
mike26 - Użytkownik
- mike26
- Użytkownik
- Skąd: ~/
- Zarejestrowany: 2013-10-16
Re: Virtualbox uruchomienie maszyny wirtualnej (vboxdrv)
Można to jakoś naprawić?
Offline
#36 2015-06-05 12:19:56
mati75 - Psuj
- mati75
- Psuj
- Skąd: masz ten towar?
- Zarejestrowany: 2010-03-14
Re: Virtualbox uruchomienie maszyny wirtualnej (vboxdrv)
fsck spróbuj dać z live cd na przykład.
Offline
#37 2015-06-08 10:26:59
mike26 - Użytkownik
- mike26
- Użytkownik
- Skąd: ~/
- Zarejestrowany: 2013-10-16
Re: Virtualbox uruchomienie maszyny wirtualnej (vboxdrv)
wykonałem
Kod:
aptitude dist-upgrade
do wersji 8.1 i virtualbox 5.0 działa.
Offline
#38 2015-06-08 21:38:07
Yampress - Imperator
- Yampress
- Imperator
- Zarejestrowany: 2007-10-18
Re: Virtualbox uruchomienie maszyny wirtualnej (vboxdrv)
nie zbudował Ci modułów virtualbox podczas instalacji bo nie miałeś pakiet ów potrzebnych do tej operacji, które wyżej Ci tutaj podali.
Offline
- Forum Debian Users Gang
- » Software
- » Virtualbox uruchomienie maszyny wirtualnej (vboxdrv)