I had upgraded Ubuntu 25.04 to 25.10 with Kernel 6.14. to 6.17.
I had my own Kernel 6.14 config, which worked well with Vbox then and still works with Vbox 7.2.2-dfsg-2.
But my own new Kernel 6.17 does not work. Its config is based on my 6.14 config.
No machine could boot and crashed instantly with a kernel error message:
Code: Select all
EMT-0[12862]: segfault at 7f9a1d4ddff0 ip 00007f9a1d4ddff0 sp 00007f9a047f7c88 error 14 in VBoxVMM .so[2ddff0,7f9a1d2a3000+303000] likely on CPU 12 (core 4, socket 0)
kernel: Code: Unable to access opcode bytes at 0x7f9a1d4ddfc6.
kernel: BUG: scheduling while atomic: EMT-0/12862/0x7ffff801Ubuntu stock kernel 6.17 works.
All kernels are booted with:
ro verbose mem_encrypt=off delayacct debugfs=on vsyscall=none zswap.enabled=1 zswap.zpool=zsmalloc slab_debug=-
There is no error in VM log, they all think, they are running. Last lines are:
00:00:01.016182 Changing the VM state from 'POWERING_ON' to 'RUNNING'
00:00:01.016200 Console: Machine state changed to 'Running'
The Vbox boot screen is not shown in any VM.