[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:
[ 74.874612] BUG: scheduling while atomic: EMT-0/2884/0x7ffffe00 [ 74.874616] 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 snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core i2c_algo_bit snd_hwdep drm_buddy intel_gtt drm_client_lib drm_display_helper snd_pcm video drm_kms_helper ttm drm e1000e snd_timer wmi [ 74.874628] CPU: 2 UID: 0 PID: 2884 Comm: EMT-0 Tainted: G S U O 6.18.16 #1 VOLUNTARY [ 74.874630] Tainted: [S]=CPU_OUT_OF_SPEC, [U]=USER, [O]=OOT_MODULE [ 74.874631] Hardware name: Gigabyte Technology Co., Ltd. Z370M D3H/Z370M D3H-CF, BIOS F10 09/18/2018 [ 74.874632] Call Trace: [ 74.874633] <TASK> [ 74.874634] dump_stack_lvl+0x49/0x70 [ 74.874637] __schedule_bug.cold+0x42/0x4f [ 74.874639] __schedule+0x75d/0xb20 [ 74.874641] ? count_memcg_events+0x51/0x100 [ 74.874642] schedule+0x1b/0xc0 [ 74.874644] exit_to_user_mode_loop+0x3e/0xb0 [ 74.874645] do_syscall_64+0x1b2/0x600 [ 74.874647] entry_SYSCALL_64_after_hwframe+0x4b/0x53 [ 74.874648] RIP: 0033:0x7f470485dc8f [ 74.874650] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [ 74.874651] RSP: 002b:00007f46e426dc60 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 74.874652] RAX: 0000000000000000 RBX: 00000036fcbb00fe RCX: 00007f470485dc8f [ 74.874653] RDX: 0000000000000000 RSI: 00000000000056c0 RDI: 0000000000000006 [ 74.874654] RBP: 00007f46e426dcc0 R08: 0000000000000000 R09: 0000000000000003 [ 74.874655] R10: 0000000000cb7354 R11: 0000000000000246 R12: 0000000000000000 [ 74.874655] R13: 00007f46ec004000 R14: 00007f46c62c9000 R15: 00007f46ec004000 [ 74.874656] </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.