Opened 4 years ago
Last modified 4 years ago
#19907 new defect
Starting VM causes 100% load on one cpu in NT-Kernel, even after VM exit
| Reported by: | theRman | Owned by: | |
|---|---|---|---|
| Component: | host support | Version: | VirtualBox 6.1.14 |
| Keywords: | Cc: | ||
| Guest type: | all | Host type: | Windows |
Description
Observe in Host task manager, that "System" process works normally. Everything idle.
Simply start some VM (tested Fedora 32 and Windows 10 1909 guest). Wait until its booted and logged in (Guest additions installed and loaded).
Observe in Host task manager, that "System" (ntoskrnl.exe) process fully loads 1 core. This is in addition to the VM process itself.
Shutdown VM.
High load can still be observed and is persistent until host is rebooted.
I tried to reproduce this with same VMs imported to another host, but failed. Seemingly its somehow connected to specific host configuration/hardware. host hardware also is relatively new. However it is 100% reproducible on this host and always triggered by staring some VM.
Attachments (1)
Change History (5)
by , 4 years ago
| Attachment: | WindowToTheWorld10-2020-09-21-18-20-44.log added |
|---|
comment:1 by , 4 years ago
Anything I can do to support analysis? Things to try, logs to gather etc?
This bug is especially annoying on this machine, as its a notebook and it makes it basically impossible to use VMs on battery power.
comment:2 by , 4 years ago
I found out that it actually is not related to the VM start. Even just starting VirtualBox UI causes the high load in nt kernel.
comment:3 by , 4 years ago
And... it even happens with a new Windows user profile. So even without any configured VMs or changed settings.
It would be nice if someone could look into this.
comment:4 by , 4 years ago
Same with latest VBox (6.1.16) Same if HyperV is used or not Same if Extensions are installed or not
I updated all drivers for the machine, but still happens...
VBox.log