Kernel panic at startup

[m0rtalis]

When starting arch linux from the live cd on my Windows host I get a kernel panic "Kernel panic - not syncing: corrupted stack end detected inside scheduler".

I have to capture the screen to get at least a bit of the stuff printed but here is what I have of the kernel panic:

Code: Select all

[14.623934] BUG: stack guard page was hit at 00000000d8e0ee2d (stack is 0000000007e39dfa..000000004c853142)
[14.640427] kernel stack overflow (double-fault): 0000 [#1] PREEMPT SMP PTI
[14.673092] CPU: 0 PID: 16 Comm: cpuhp/0 Not tainted 5.6.15-arch1-1 #1
[14.676632] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
[14.680427] RIP: 0010:error_entry+0x1b/0x100
[14.682712] Code: ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 fc 56 48 8b 74 24 08 48 89 7c 24
.... (didn't capture this)
(repeated lines of:)
[14.8xxxxx] ? native_iret+0x07/0x7
[14.8xxxxx] ? do_page_fault+0x14/0x180
(end repeated lines)

(linked modules and cpu registers. If you need this let me know)
[15.372345] note: cpuhp/0[16] exited with preempt_count 2
[15.478440] Kernel panic - not syncing: corrupted stack end detected inside scheduler
[15.520349] Kernel Offset: 0xde00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[15.525035] ---[ end Kernel panic - not syncing: corrupted stack end detected inside scheduler ]---

Hardware virtualization is enabled in BIOS
Virtualbox Version: 6.1.10
VM Extension Pack: 6.1.10r138449
Host
OS: Windows 10 Pro 64bit
Processor: Intel i7-3770
RAM: 16GB
Guest
OS: Arch Linux 64bit
Processor: 4 CPUs/100%
RAM: 8GB
Video Memory: 64MB
Paravirtualization Interface: Default
Hardware Virtualization: Enable Nested Paging is enabled

Logs are attached.

Any help is greatly appreciated.

[m0rtalis]

Error still remains after update to VirtualBox 6.1.12

[scottgus1]

Hyper-V is enabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active)

Additionally, you have all four physical hyperthreaded cores available for the guest to use. Hyperthreads don't count in Virtualbox, so you have all cores available for the guest. If the guest goes full-throttle on all engines, the host will go unstable. Try 2 processors in the guest.

Also, the guest has 3D enabled and the host Nvidia drivers are having a problem:

00:00:03.832936 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_CR_PKCS7_KEY_USAGE_MISMATCH fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nvwuwu.inf_amd64_8092fc7fd16353b3\
nvd3dumx.dll

A new Nvidia driver version for your host video was put out with a file that has a portion of its security signature incompatible with Virtualbox's hardening. (The jury is still out on whether it is Nvidia or Virtualbox at fault, or both.)Try turning 3D off or see fth0's suggestions:
viewtopic.php?f=6&t=99059&p=480386#p480336

If you get the Nvidia driver straightened out, the guest has only 64MB video RAM. 3D will need more. Max that slider out.