VBox 6.1.6: Win 10 VM freezing with kernel backtrace
Posted: 7. May 2020, 13:36
Hi, I'm running virtualbox v6.1.6 (also tried v6.1.4, same behaviour) on a Gentoo Linux machine with kernel version v5.4.38 (also tried v5.4.28, same behaviour). The Extension Pack is NOT installed. The guest OS is Windows 10 64bit. I connect remotely to the VM using VNC (using VirtualBox' integrated capabilities, no VNC server running in the geust machine).
The VM boots up fine but gets stuck seconds to minutes of usage. VirtualBox still reports the machine as "Running" but is unable to stop it using the "poweroff" command. The machine then stays stuck in "Stopping" and I have to reboot the host.
In the host's kernel log, there is a backtrace following a page fault error. I've tried to find the root cause by searching for the affected function names but nothing seems to be related to or relevant for the problem I am experiencing.
Kernel backtrace:
I'm attaching the following files:
- VBox.log
- host's kernel log
- host's kernel configuration
I'd be happy for any hints that help me solve that problem. Thanks!
The VM boots up fine but gets stuck seconds to minutes of usage. VirtualBox still reports the machine as "Running" but is unable to stop it using the "poweroff" command. The machine then stays stuck in "Stopping" and I have to reboot the host.
In the host's kernel log, there is a backtrace following a page fault error. I've tried to find the root cause by searching for the affected function names but nothing seems to be related to or relevant for the problem I am experiencing.
Kernel backtrace:
Code: Select all
[ 295.761327] BUG: unable to handle page fault for address: 00007f48dc560000
[ 295.761333] #PF: supervisor read access in kernel mode
[ 295.761335] #PF: error_code(0x0001) - permissions violation
...
[ 295.761365] Call Trace:
[ 295.761372] ? __switch_to_asm+0x34/0x70
[ 295.761375] ? down+0xd/0x50
[ 295.761377] ? up+0xd/0x50
[ 295.761383] ? VBoxHost_RTSemFastMutexRelease+0x3e/0x50 [vboxdrv]
[ 295.761385] ? _cond_resched+0x14/0x30
[ 295.761387] ? down+0xd/0x50
[ 295.761390] ? futex_wake+0x8b/0x160
[ 295.761391] ? _cond_resched+0x14/0x30
[ 295.761394] ? __kmalloc+0x122/0x210
[ 295.761397] ? supdrvIOCtl+0xfec/0x3300 [vboxdrv]
[ 295.761401] ? rtR0MemAllocEx+0x14b/0x230 [vboxdrv]
[ 295.761402] ? do_futex+0x8b0/0xcf0
[ 295.761405] ? __check_object_size+0x153/0x164
[ 295.761408] ? _copy_from_user+0x37/0x60
[ 295.761411] ? SUPR0Printf+0x206/0x340 [vboxdrv]
[ 295.761413] ? do_vfs_ioctl+0x431/0x6a0
[ 295.761415] ? ksys_ioctl+0x46/0x90
[ 295.761416] ? __x64_sys_ioctl+0x11/0x20
[ 295.761419] ? do_syscall_64+0x43/0x110
[ 295.761421] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
- VBox.log
- host's kernel log
- host's kernel configuration
I'd be happy for any hints that help me solve that problem. Thanks!