Changes between Version 1 and Version 2 of Ticket #18089, comment 1
- Timestamp:
- Oct 30, 2018 8:00:45 PM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #18089, comment 1
v1 v2 1 1 I too am seeing this behavior since upgrading to VirtualBox 5.2.20 (with a CentOS 7 x64 guest). The host CPU is pegged at 100% while the guest is doing nothing (I've tried to stop almost everything inside the guest, but the CPU usage on the host remains at 100%). 2 2 3 I've also tried to boot the VM with "legacy" and "default" paravirtualization. The result is the same, after a while this behavior appears (randomly, I can't reproduce it reliably).3 I've also tried to boot the VM with "legacy" and "default" paravirtualization. The result is the same, after a while this behavior appears. It seems to be triggered by the host coming back from sleep. 4 4 5 5 The host is also macOS 10.12.6. The previous version of VirtualBox that I used (and didn't show this behavior, as far as I can tell) was 5.2.18.