[linux] Virtuele machine start niet meer op
Daniel C. von Asmuth
asmuth op bakunin.xs4all.nl
Za Jun 23 13:35:28 CEST 2018
Aldus schreef harry.harmsen op gmail.com op Sat, Jun 23, 2018 at 12:40:46PM +0200:
> *Linux Mint 17.3. Na terugzetten van een vorige situatie wil mijn Oracle VM
> Virual Box niet meer opstarten. Ik krijg de volgende foutmelding:*
>
>
> harry op harry-MS-7708 ~ $ sudo /sbin/rcvboxdrv setup
> [sudo] password for harry:
> Stopping VirtualBox kernel modules ...done.
> Uninstalling old VirtualBox DKMS kernel modules ...done.
> Trying to register the VirtualBox kernel modules using DKMSError! Bad
> return status for module build on kernel: 4.15.13-041513-generic (x86_64)
> Consult /var/lib/dkms/vboxhost/5.0.40/build/make.log for more information.
> ...failed!
> (Failed, trying without DKMS)
> Recompiling VirtualBox kernel modules ...failed!
> (Look at /var/log/vbox-install.log to find out what went wrong)
> harry op harry-MS-7708 ~ $
Dat ziet er buitengewoon merkwaardig uit: Linux Mint 17.3 zou dateren
van december 2015 en Linux 4.15.13 van maart 2018. VirtualBox 5.0.40
dateert van april 2017. De GCC versie 4.8.x tussen 2013 en 2015.
> *Het genoemde logbestand ziet er zo uit:*
> Makefile:946: "Cannot use CONFIG_STACK_VALIDATION=y, please install
> libelf-dev, libelf-devel or elfutils-libelf-devel"
Heb je die DKMS en elfutils pakketten geïnstalleerd?
> test -e include/generated/autoconf.h -a -e include/config/auto.conf || (
> \
> echo >&2; \
> echo >&2 " ERROR: Kernel configuration is invalid."; \
> echo >&2 " include/generated/autoconf.h or
> include/config/auto.conf are missing.";\
> echo >&2 " Run 'make oldconfig && make prepare' on kernel src
> to fix it."; \
> echo >&2 ; \
> /bin/false)
Heb je dat geprobeerd?
> mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
> make -f ./scripts/Makefile.build obj=/tmp/vbox.0
> gcc -Wp,-MD,/tmp/vbox.0/linux/.SUPDrv-linux.o.d -nostdinc -isystem
> /usr/lib/gcc/x86_64-linux-gnu/4.8/include -I./arch/x86/include
> -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi
> -I./arch/x86/include/generated/uapi -I./include/uapi
> -I./include/generated/uapi -include ./include/linux/kconfig.h -D__KERNEL__
> -fno-pie -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs
> -fno-strict-aliasing -fno-common -fshort-wchar
> -Werror-implicit-function-declaration -Wno-format-security -std=gnu89
> -fno-PIE -fno-pie -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64
> -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387
> -mpreferred-stack-boundary=3 -mtune=generic -mno-red-zone -mcmodel=kernel
> -funit-at-a-time -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1
> -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1
> -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1
> -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_SHA1_NI=1
> -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare
> -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern
> -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -O2
> -Wno-maybe-uninitialized --param=allow-store-data-races=0
> -DCC_HAVE_ASM_GOTO -Wframe-larger-than=1024 -fstack-protector-strong
> -fno-omit-frame-pointer -fno-optimize-sibling-calls -pg -include
> /tmp/vbox.0/include/VBox/SUPDrvMangling.h
> -I/lib/modules/4.15.13-041513-generic/build/include -I/tmp/vbox.0/
> -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -I/tmp/vbox.0/vboxdrv/
> -I/tmp/vbox.0/vboxdrv/include -I/tmp/vbox.0/vboxdrv/r0drv/linux
> -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0
> -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DSUPDRV_WITH_RELEASE_LOGGER
> -Wno-declaration-after-statement -DCONFIG_VBOXDRV_AS_MISC -DRT_ARCH_AMD64
> -DVBOX_WITH_64_BITS_GUESTS -fno-pie -DMODULE
> -DKBUILD_BASENAME='"SUPDrv_linux"' -DKBUILD_MODNAME='"vboxdrv"' -c -o
> /tmp/vbox.0/linux/SUPDrv-linux.o /tmp/vbox.0/linux/SUPDrv-linux.c
> gcc: error: unrecognized command line option ‘-fstack-protector-strong’
En daar zien we een relevante foutmelding. Je zou die optie gewoon
kunnen verwijderen uit de makefile.
Ik zou een nieuwere GCC installeren en een oudere kernel en misschien
een nieuwere VirtualBox. Sommige mensen zouden gewoon upgraden naar de
nieuwste Linux Mint.
> make[2]: *** [/tmp/vbox.0/linux/SUPDrv-linux.o] Fout 1
> make[1]: *** [_module_/tmp/vbox.0] Fout 2
> make: *** [vboxdrv] Fout 2
>
> *Maar ik krijg nog steeds de virtuele machine niet opgestart.Wat moet ik
> nog meer doen?Alvast bedankt voor de hulp.*
>
> Groet,
> Harry Harmsen
> Assen
Succes,
Daniel
Domstad
--
Geeks of a feather cruft together
Meer informatie over de Linux
maillijst