virtualbox.org

I know this thread is a few months old now, but I don't see that a solution was ever reached. I was able to locate the instance in my VMLog where the issue occurred, just not sure what to make of the information...

00:22:09.717888 GUI: Capturing keyboard on resume
00:22:20.154003 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:22:20.154309 AIOMgr: Async flushes not supported
00:22:20.157976 AIOMgr: Endpoint for file 'C:\Users\RyGuy\VirtualBox VMs\TryingAgain\TryingAgain.vdi' (flags 000c0781) created successfully
00:22:20.166927 PDMR3Suspend: 12 884 686 ns run time
00:22:20.166936 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'

Why was it suspended? What does all of this mean?...

00:22:20.166943 Console: Machine state changed to 'Paused'
00:22:20.176377 GUI: Releasing keyboard on pause/stuck
00:22:20.176385 GUI: Releasing mouse on pause/stuck
00:22:20.177278 GUI: Machine-window #0 deactivated
00:22:20.177289 GUI: Releasing mouse on focus out
00:22:20.177318 GUI: Machine-view #0 unfocused, reason=3
00:22:22.087150 GUI: Machine-window #0 activated
00:22:22.087169 GUI: Machine-view #0 focused, reason=3
00:22:22.087980 GUI: Request for close-action to power VM off.

This would be where I told the VM to power off.

I also noticed some previous entries like these:

00:13:00.658702 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago

00:02:31.007172 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 18 seconds ago
00:02:31.009797 VMMDev: GuestHeartBeat: Guest is alive (gone 18 532 952 316 ns)

00:02:12.290353 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 47 seconds ago
00:02:12.291555 VMMDev: GuestHeartBeat: Guest is alive (gone 47 643 144 602 ns)

Why does it keep saying my heartbeat is unresponsive?... I'm not dead...

I've also attached the full log, in case that helps. The original log was apparently too big, so I just removed the first half-ish (anything before 00:00:03)

Partial logs are not often much use when trying to identify issues/problems. Please compact (zip) the log and it should then be within the upload limit.

Here you go

Split to separate topic, per Do not hijack other threads, create your own. Choose your title carefully.

The thread you linked to says "Please do not hijack unrelated threads..." which definitely makes sense... Except that it's not an "unrelated" thread... my VM does keep freezing on me and this thread was going through the troubleshooting process of trying to help another user resolve that same problem, which never got solved... I was just trying to avoid crowding the forums with open, unanswered, and unresolved questions...

No problem, it's often folks think their problem is similar. But the topics get confusing with several problem sources in them. And it is actually very rare that two folks have the same-enough problem to be in the same topic. Even a Virtualbox version difference is enough to warrant a different topic.

The VM has 4 processors. Please try two. If that does not work, please try disabling Hyper-V, see HMR3Init: Attempting fall back to NEM (Hyper-V is active).

I'll give that a shot and let you know how it goes...
Out of curiosity, why would giving a machine less processors help?...

More processors in a VM means more scheduling oversight on the host OS and so slightly slower individual instruction execution. We've had single-processor VMs run badly on Hyper-V-enabled hosts, but they've run better when set to two processors. I'm curious if your VM stabilizes when using 2 processors while Hyper-V is still enabled.

More processors can be used stably when Hyper-V is not enabled on the host. But more processors is only really beneficial when there's 3rd-party multi-processor-aware apps installed in the VM. Typical modern OS's by themselves without 3rd-party multi-processor-aware apps run swimmingly on 2 processors.

Apparently that was, indeed, the problem. Thank you!

Also, I double checked, but I don't have Windows Hypervisor Platform nor Virtual Machine Platform enabled in Windows Features. Should I?...

RyRyGuy wrote:Apparently that was, indeed, the problem.

Does this mean using two processors and leaving Hyper-V enabled works?

I'm not certain... From what I can tell, I never had Hyper-V enabled (it's not explicitly listed in the Windows Features window, but Windows Hypervisor Platform is listed, but it wasn't enabled). In other words, I did not change anything at all aside from reducing the 4 processors down to 2, so if Hyper-V was enabled elsewhere, then it is still enabled. Otherwise, no, it was never enabled.

Hyper-V gets used by lots of newer Windows services, please see the "Attempting" link.

Two processors has fixed up some recent VM issues with active host Hyper-V; yours seems to be one of them. Thanks for the info!

Note that OP has WSL installed. It may be that Hyper-V doesn't start until that's invoked, but given MS's general behavior I wouldn't be inclined to trust that it doesn't (or won't suddenly start doing so).