[Bug]: Unable to powerup any VM instance #584
Description
Version
7.2.6
Host OS Type
Linux
Host OS name + version
Gentoo 6.18.6
Host Architecture
x86
Guest OS Type
all
Guest Architecture
x86
Guest OS name + version
No response
Component
VMM
What happened?
I'm unable to powerup any VM. Window pops up and disappers again. Manager reports:
Result Code: | NS_ERROR_CALL_FAILED (0x800706be)
dmesg reports:
[ 131.244534] ------------[ cut here ]------------
[ 131.244536] WARNING: CPU: 1 PID: 6797 at kernel/softirq.c:429 __local_bh_enable_ip+0x29/0x40
[ 131.244541] Modules linked in: vboxnetadp(O) vboxnetflt(O) vboxdrv(O) snd_hda_codec_intelhdmi snd_hda_codec_hdmi snd_hda_codec_alc662 snd_hda_codec_realtek_lib snd_hda_codec_generic rfkill wmi_bmof i915 i2c_algo_bit drm_buddy snd_hda_intel intel_gtt drm_client_lib snd_intel_dspcfg drm_display_helper snd_hda_codec snd_hda_core drm_kms_helper ttm snd_hwdep video drm snd_pcm e1000e snd_timer wmi [last unloaded: vboxdrv(O)]
[ 131.244553] CPU: 1 UID: 0 PID: 6797 Comm: EMT-0 Tainted: G S U O 6.18.16 #1 VOLUNTARY
[ 131.244556] Tainted: [S]=CPU_OUT_OF_SPEC, [U]=USER, [O]=OOT_MODULE
[ 131.244556] Hardware name: Gigabyte Technology Co., Ltd. Z370M D3H/Z370M D3H-CF, BIOS F10 09/18/2018
[ 131.244557] RIP: 0010:__local_bh_enable_ip+0x29/0x40
[ 131.244558] Code: 00 65 f6 05 32 46 2d 01 0f 75 1f ff ce f7 de 65 01 35 23 46 2d 01 65 66 f7 05 1a 46 2d 01 ff ff 74 0c 65 ff 0d 10 46 2d 01 c3 <0f> 0b eb dd 65 66 83 3d 0a 46 2d 01 00 74 e9 e8 73 ff ff ff eb e2
[ 131.244560] RSP: 0018:ffff88813b76fb88 EFLAGS: 00010206
[ 131.244561] RAX: 0000000000000246 RBX: ffffc90001493000 RCX: 0000000000000000
[ 131.244562] RDX: 0000000000000000 RSI: 0000000000000200 RDI: ffffffff8126cc1c
[ 131.244562] RBP: ffff88813b76fbc0 R08: 0000000000000a3c R09: 0000000000000000
[ 131.244563] R10: ffffc900014de340 R11: ffffc900014cd000 R12: ffffc90001493000
[ 131.244564] R13: 0000000000000001 R14: ffffc90001493000 R15: 0000000000000487
[ 131.244565] FS: 00007f71003886c0(0000) GS:ffff88888d0de000(0000) knlGS:0000000000000000
[ 131.244566] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 131.244566] CR2: 0000000000000000 CR3: 000000015f333005 CR4: 00000000003726f0
[ 131.244568] Call Trace:
[ 131.244569] <TASK>
[ 131.244569] ? raw_spin_rq_lock_nested+0x9/0x10
[ 131.244571] ? sched_balance_newidle+0x342/0x4a0
[ 131.244573] ? update_load_avg+0x7b/0x690
[ 131.244575] ? wakeup_preempt+0x63/0x70
[ 131.244577] ? supdrvIOCtlFast+0x55/0xa0 [vboxdrv]
[ 131.244583] ? VBoxDrvLinuxIOCtl_7_2_7+0x41/0x470 [vboxdrv]
[ 131.244586] ? do_futex+0xa6/0x120
[ 131.244587] ? __x64_sys_ioctl+0x72/0xc0
[ 131.244589] ? do_syscall_64+0x57/0x600
[ 131.244591] ? entry_SYSCALL_64_after_hwframe+0x4b/0x53
[ 131.244592] </TASK>
[ 131.244592] ---[ end trace 0000000000000000 ]---
[ 131.244597] EMT-0[6797]: segfault at 7f70d82d0390 ip 00007f70d82d0390 sp 00007f7100387c08 error 14 in VBoxDD.so[4a390,7f70d82bc000+2ea000] likely on CPU 1 (core 1, socket 0)
[ 131.244603] Code: Unable to access opcode bytes at 0x7f70d82d0366.
[ 131.244616] BUG: scheduling while atomic: EMT-0/6797/0x7ffffc00
[ 131.244617] Modules linked in: vboxnetadp(O) vboxnetflt(O) vboxdrv(O) snd_hda_codec_intelhdmi snd_hda_codec_hdmi snd_hda_codec_alc662 snd_hda_codec_realtek_lib snd_hda_codec_generic rfkill wmi_bmof i915 i2c_algo_bit drm_buddy snd_hda_intel intel_gtt drm_client_lib snd_intel_dspcfg drm_display_helper snd_hda_codec snd_hda_core drm_kms_helper ttm snd_hwdep video drm snd_pcm e1000e snd_timer wmi [last unloaded: vboxdrv(O)]
[ 131.244625] CPU: 1 UID: 0 PID: 6797 Comm: EMT-0 Tainted: G S U W O 6.18.16 #1 VOLUNTARY
[ 131.244627] Tainted: [S]=CPU_OUT_OF_SPEC, [U]=USER, [W]=WARN, [O]=OOT_MODULE
[ 131.244627] Hardware name: Gigabyte Technology Co., Ltd. Z370M D3H/Z370M D3H-CF, BIOS F10 09/18/2018
[ 131.244627] Call Trace:
[ 131.244628] <TASK>
[ 131.244629] dump_stack_lvl+0x49/0x70
[ 131.244630] __schedule_bug.cold+0x42/0x4f
[ 131.244632] __schedule+0x75d/0xb20
[ 131.244634] ? select_task_rq_fair+0x363/0x1140
[ 131.244636] ? hrtimer_nanosleep_restart+0x110/0x110
[ 131.244638] schedule+0x1b/0xc0
[ 131.244639] schedule_timeout+0xbf/0x100
[ 131.244640] __wait_for_common+0x68/0x140
[ 131.244642] wait_for_completion_state+0x18/0x30
[ 131.244643] vfs_coredump+0x326/0x2160
[ 131.244645] ? desc_update_last_finalized+0x34/0x60
[ 131.244648] ? vprintk_store+0x45a/0x4c0
[ 131.244649] ? vprintk_emit+0xf5/0x1f0
[ 131.244650] ? kmem_cache_free+0x2cb/0x410
[ 131.244651] ? get_signal+0x30d/0x6f0
[ 131.244652] get_signal+0x271/0x6f0
[ 131.244653] arch_do_signal_or_restart+0x77/0x270
[ 131.244656] irqentry_exit_to_user_mode+0xe1/0x160
[ 131.244658] asm_exc_page_fault+0x22/0x30
[ 131.244659] RIP: 0033:0x7f70d82d0390
[ 131.244661] Code: Unable to access opcode bytes at 0x7f70d82d0366.
[ 131.244661] RSP: 002b:00007f7100387c08 EFLAGS: 00010246
[ 131.244662] RAX: 0000000000000000 RBX: 0000000000000002 RCX: 00007f7100387ccc
[ 131.244662] RDX: 0000000000000002 RSI: 0000000000000002 RDI: 00007f70d8009cc0
[ 131.244663] RBP: 00007f7100387c50 R08: ffffffffffffffff R09: 00007f70d8009cc0
[ 131.244664] R10: 00007f70ba437000 R11: 0000000000000246 R12: 00007f70d8009000
[ 131.244664] R13: 0000000000000000 R14: 0000000000000002 R15: 00007f7100387ccc
[ 131.244665] </TASK>
How can we reproduce this?
Install latest Virtualbox release on a (Gentoo) Linux system with Kernel 6.18.16
compile and load host kernel modules
fireup VMM and power up any VM instance.
Did you upload all of your necessary log files, screenshots, etc.?
- Yes, I've uploaded all pertinent files to this issue.