Failed to open a session for the virtual machine Windows10.
The virtual machine 'Windows10' has terminated unexpectedly during startup with exit code 1 (0x1).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
[Resolved] Vbox won't start after kernel update
[Resolved] Vbox won't start after kernel update
Running vbox 5.0.10 on linux mint 19.2. Just updated to kernel 5.3. Getting the following when I try to start a vm.
Last edited by socratis on 31. Oct 2019, 04:26, edited 2 times in total.
Reason: Marked as [Resolved].
Reason: Marked as [Resolved].
Re: Vbox won't start after 5.3 kernel update
Went back to kernel 5.0.0.32 and getting same results. Here is log:
Code: Select all
gcc -Wp,-MD,/tmp/vbox.0/r0drv/linux/.rtStrFormatKernelAddress-r0drv-linux.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/7/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 -Iubuntu/include -include ./include/linux/compiler_types.h -D__KERNEL__ -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE -Werror=implicit-function-declaration -Werror=implicit-int -Wno-format-security -std=gnu89 -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 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -fno-jump-tables -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -O2 --param=allow-store-data-races=0 -Wframe-larger-than=1024 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -fno-omit-frame-pointer -fno-optimize-sibling-calls -fno-var-tracking-assignments -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wimplicit-fallthrough -Wvla -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -include /tmp/vbox.0/include/VBox/SUPDrvMangling.h -fno-omit-frame-pointer -fno-pie -Wno-declaration-after-statement -I./include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -D__KERNEL__ -DMODULE -DRT_WITHOUT_PRAGMA_ONCE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DSUPDRV_WITH_RELEASE_LOGGER -DVBOX_WITH_64_BITS_GUESTS -DCONFIG_VBOXDRV_AS_MISC -DRT_ARCH_AMD64 -DMODULE -DKBUILD_BASENAME='"rtStrFormatKernelAddress_r0drv_linux"' -DKBUILD_MODNAME='"vboxdrv"' -c -o /tmp/vbox.0/r0drv/linux/rtStrFormatKernelAddress-r0drv-linux.o /tmp/vbox.0/r0drv/linux/rtStrFormatKernelAddress-r0drv-linux.c /tmp/vbox.0/r0drv/linux/mp-r0drv-linux.c: In function ‘VBoxHost_RTMpOnAll’: /tmp/vbox.0/r0drv/linux/mp-r0drv-linux.c:287:18: error: void value not ignored as it ought to be int rc = smp_call_function(rtmpLinuxAllWrapper, &Args, 0 /* wait */); ^~~~~~~~~~~~~~~~~ /tmp/vbox.0/r0drv/linux/mp-r0drv-linux.c: In function ‘VBoxHost_RTMpOnOthers’: /tmp/vbox.0/r0drv/linux/mp-r0drv-linux.c:341:8: error: void value not ignored as it ought to be rc = smp_call_function(rtmpLinuxWrapper, &Args, 1 /* wait */); ^ scripts/Makefile.build:288: recipe for target '/tmp/vbox.0/r0drv/linux/mp-r0drv-linux.o' failed make[2]: *** [/tmp/vbox.0/r0drv/linux/mp-r0drv-linux.o] Error 1 make[2]: *** Waiting for unfinished jobs.... Makefile:1653: recipe for target '_module_/tmp/vbox.0' failed make[1]: *** [_module_/tmp/vbox.0] Error 2 /tmp/vbox.0/Makefile-footer.gmk:111: recipe for target 'vboxdrv' failed make: *** [vboxdrv] Error 2
Last edited by socratis on 31. Oct 2019, 04:18, edited 1 time in total.
Reason: Enclosed the information in [quote][code] tags for better readability
Reason: Enclosed the information in [quote][code] tags for better readability
Re: Vbox won't start after kernel update
Tried reinstalling vbox 6.0.10.
Got this on terminal:
Got this on terminal:
bmaring@bmaring-HP-Notebook:~$ sudo /sbin/vboxconfig vboxdrv.sh: Stopping VirtualBox services. vboxdrv.sh: Starting VirtualBox services. vboxdrv.sh: Building VirtualBox kernel modules. vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong. There were problems setting up VirtualBox. To re-start the set-up process, run /sbin/vboxconfig as root. If your system is using EFI Secure Boot you may need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information.
Last edited by socratis on 31. Oct 2019, 04:17, edited 1 time in total.
Reason: Enclosed the information in [quote][pre] tags for better readability
Reason: Enclosed the information in [quote][pre] tags for better readability
Re: Vbox won't start after kernel update
Seems to work fine after updating to 6.0.14
-
socratis
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Vbox won't start after kernel update
That's an old and outdated configuration.bmaring wrote:Running vbox 5.0.10 on linux mint 19.2
That was borderline supported with 6.0.12 or 5.2.32.bmaring wrote:Just updated to kernel 5.3.
That's it!bmaring wrote:Seems to work fine after updating to 6.0.14
If you want to use the latest version for your host/guests, you should also consider doing the same for VirtualBox. Download the latest VirtualBox. If that doesn't work you should try the latest test builds.
Glad you got it going. Marking as [Resolved].
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.