Opened 4 years ago
Last modified 4 years ago
#20463 new defect
Windows 10 guest crashes on startup
Reported by: | robert21 | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 6.1.22 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Linux |
Description
Host is Pop OS 21.04 with kernel 5.13.2-051302-generic from Ubuntus mainline kernels.
Usually this works just fine, my VM started just fine on kernel 5.13.1 but now with the update to .2 it crashes on startup. I did do a sudo vboxconfig
after a new kernel update, this did not help.
The crash is as follows:
Jul 19 07:37:44 pc1 vboxdrv.sh: Stopping VirtualBox services. Jul 19 07:37:44 pc1 vboxdrv.sh: VirtualBox services stopped. Jul 19 07:37:46 pc1 vboxdrv.sh: Starting VirtualBox services. Jul 19 07:37:46 pc1 vboxdrv.sh: Building VirtualBox kernel modules. Jul 19 07:37:50 pc1 vboxdrv.sh: VirtualBox kernel modules built. Jul 19 07:37:50 pc1 kernel: [ 470.024094] vboxdrv: Found 32 processor cores Jul 19 07:37:50 pc1 kernel: [ 470.041364] vboxdrv: TSC mode is Invariant, tentative frequency 3399987811 Hz Jul 19 07:37:50 pc1 kernel: [ 470.041365] vboxdrv: Successfully loaded version 6.1.22 (interface 0x00300000) Jul 19 07:37:50 pc1 kernel: [ 470.244020] VBoxNetFlt: Successfully started. Jul 19 07:37:50 pc1 vboxdrv.sh: VirtualBox services started. Jul 19 07:37:50 pc1 kernel: [ 470.245483] VBoxNetAdp: Successfully started. Jul 19 07:37:51 pc1 kernel: [ 470.914903] SUPR0GipMap: fGetGipCpu=0x3b Jul 19 07:37:52 pc1 gnome-shell[4732]: ../../../gobject/gsignal.c:2732: instance '0x56199cb9d210' has no handler with id '59274' Jul 19 07:37:52 pc1 kernel: [ 471.454134] vboxdrv: 0000000000000000 VMMR0.r0 Jul 19 07:37:52 pc1 kernel: [ 471.555385] vboxdrv: 0000000000000000 VBoxDDR0.r0 Jul 19 07:37:52 pc1 kernel: [ 471.609014] VBoxNetFlt: attached to 'enp7s0' / a8:5e:45:11:96:76 Jul 19 07:37:52 pc1 kernel: [ 471.611471] vboxdrv: 0000000000000000 VBoxEhciR0.r0 Jul 19 07:37:52 pc1 kernel: [ 471.611804] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0) Jul 19 07:37:52 pc1 kernel: [ 471.643364] device enp7s0 entered promiscuous mode Jul 19 07:37:52 pc1 gnome-shell[4732]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x620018a specified for 0x620018c. Jul 19 07:38:13 pc1 kernel: [ 492.433391] device enp7s0 left promiscuous mode Jul 19 07:38:13 pc1 kernel: [ 492.458757] Jul 19 07:38:13 pc1 kernel: [ 492.458757] !!Assertion Failed!! Jul 19 07:38:13 pc1 kernel: [ 492.458757] Expression: pCritSect->s.Core.NativeThreadOwner == hNativeSelf Jul 19 07:38:13 pc1 kernel: [ 492.458757] Location : /home/vbox/vbox-6.1.22/src/VBox/VMM/VMMAll/PDMAllCritSect.cpp(575) int PDMCritSectLeave(PPDMCRITSECT) Jul 19 07:38:13 pc1 kernel: [ 492.458764] ffffad525034a000 <R3_STRING>: ffffffffffffffff != 00007f6f9c164640; cLockers=-1 cNestings=1 Jul 19 07:38:13 pc1 kernel: [ 492.489177] vboxnetflt: 0 out of 0 packets were not sent (directed to host) Jul 19 07:38:26 pc1 gnome-shell[4732]: ../../../gobject/gsignal.c:2732: instance '0x56199871a0a0' has no handler with id '61338' Jul 19 07:38:26 pc1 kernel: [ 506.400406] vboxdrv: 0000000000000000 VMMR0.r0 Jul 19 07:38:27 pc1 kernel: [ 506.511297] vboxdrv: 0000000000000000 VBoxDDR0.r0 Jul 19 07:38:27 pc1 kernel: [ 506.553575] VBoxNetFlt: attached to 'enp7s0' / a8:5e:45:11:96:76 Jul 19 07:38:27 pc1 kernel: [ 506.556406] vboxdrv: 0000000000000000 VBoxEhciR0.r0 Jul 19 07:38:27 pc1 kernel: [ 506.556838] VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0) Jul 19 07:38:27 pc1 kernel: [ 506.589360] device enp7s0 entered promiscuous mode
Attachments (2)
Change History (3)
by , 4 years ago
comment:1 by , 4 years ago
You're encountering a known issue with Linux kernel 5.13, which is not supported by VirtualBox 6.1.22. The upcoming VirtualBox 6.1.24 is expected to support it.
Note:
See TracTickets
for help on using tickets.
VBox.log