After VirtualBox 7.0 upgrade, Windows 7 host freezes

[Normann1974]

After upgrading to VB 7 (currently 7.0.6), my Windows 7 freezes regularly. If I pause the VM and unpauses it, Windows wakes up and runs for a while again, then freezes. Lots of unresponsive/heartbeat entries in the logs:

Code: Select all   Expand viewCollapse view

00:15:06.996760 TM: Giving up catch-up attempt at a 752 049 666 037 ns lag; new total: 752 049 666 037 ns
00:15:06.996778 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 752 seconds ago
00:15:06.996789 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:15:07.003301 AIOMgr: Endpoint for file 'D:\VirtualBox VMs\Windows 7\Windows 7.vdi' (flags 000c0781) created successfully
00:15:07.004132 PDMR3Suspend: 7 288 359 ns run time
00:15:07.004139 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:15:07.004145 Console: Machine state changed to 'Paused'
00:15:07.157360 Changing the VM state from 'SUSPENDED' to 'RESUMING'
00:15:07.157562 AIOMgr: Endpoint for file 'D:\VirtualBox VMs\Windows 7\Windows 7.vdi' (flags 000c0723) created successfully
00:15:07.158549 Changing the VM state from 'RESUMING' to 'RUNNING'
00:15:07.158569 Console: Machine state changed to 'Running'
00:15:07.389840 AIOMgr: Async flushes not supported
00:15:08.352930 VMMDev: GuestHeartBeat: Guest is alive (gone 754 068 812 732 ns)
00:15:14.172800 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 5 seconds ago
00:15:15.161453 VMMDev: GuestHeartBeat: Guest is alive (gone 6 808 522 927 ns)
00:15:45.692992 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 30 seconds ago
00:15:46.827884 VMMDev: GuestHeartBeat: Guest is alive (gone 31 666 431 591 ns)


My VM runs on Windows 11 with, 2 GB RAM, 2 processors, 128 MB video RAM, nested paging, Hyper-V paravirtualization.

Any advice?

/Jan

[scottgus1]

Windows 7 host freezes

My VM runs on Windows 11

Is the host, the physical PC, 7 or 11?

Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. In the "Logs" subfolder, zip the VM's "vbox.log", and post the zip file, using the forum's Upload Attachment tab. (Configure your host OS to show all extensions so you can find the "vbox.log", not "vbox.log.1", etc.)

[Normann1974]

Here's a log after the VM froze for a few seconds and then woke up again by itself. As previously stated, physical machine runs Win11.

[scottgus1]

As previously stated

No, you actually said both 7 and 11 were your host OS, per the quotes I put in above, one from the post, other from the title. I didn't put those quotes in because I had extra typing to throw around. You were unclear. The "host" is the physical PC, not the VM. Thanks for fixing that ambiguity!

The log doesn't show anything particularly unusual that I can see right off. You're running 7.0.6 Virtualbox and Guest Additions, no Extension Pack, and not using 3D acceleration in the VM. Windows host Hyper-V is enabled.

7.0 is still in bug-hunt phase. Could you please try uninstalling the Guest Additions inside the VM and see if it seizes up?

[Normann1974]

As previously stated

No, you actually said both 7 and 11 were your host OS, per the quotes

Yes, that was a bit confusing. I can't seem to change the title. The host is Windows 11, the VM is Windows 7.

I uninstalled the guest additions and restarted, but the VM still freezes. But there are no heartbeat/unresponsive entries in the logs any more. Instead, there's a lot of these:

Code: Select all   Expand viewCollapse view

00:23:25.874070 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={25360a74-55e5-4f14-ac2a-f5cf8e62e4af} aComponent={MouseWrap} aText={Could not send the mouse event to the virtual mouse (VERR_PDM_NO_QUEUE_ITEMS)}, preserve=false aResultDetail=-2807

/Jan

[Normann1974]

I just tried installing Debian 11.6 in a VM. The text based installer froze twice during installation. Both times, I had to suspend and resume the VM to wake it up. Nothing of interest in the logs from that time.

/Jan

[scottgus1]

There are some mouse glitches being reported elsewhere. Can you please try the PS/2 mouse in the System > Motherboard settings?

[Normann1974]

Changing to PS/2 got rid of the log entries (which appeared when the guest additions were uninstalled). But it seemed to make the freezing worse both with and without the guest additions installed. Now, after the VM starts freezing (which may take a minute or two, I don't know what triggers it), the VM freezes in less than a second every time there is no movement of the mouse. With the guest additions installed, I am able to make the VM unfreeze by moving the mouse inside the VM. Without the guest additions, I have to suspend/resume (right Ctrl-P) to unfreeze.

[scottgus1]

Thanks for trying.

I'm not sure what else to do, we'd need a forum guru to come along, or you could fall back to 6.1.40 or .42, and wait until 7.0 matures some more.

[mpack]

I would say to enable at least USB2 hardware in the VM settings, but make sure that you don't have any USB filters configured that could be grabbing ownership of the host mouse.

Also, Hyper-v is enabled and will interfere.

00:00:05.092676 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:05.101595 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={The VBoxGuestPropSvc service call failed with the error VERR_HGCM_SERVICE_NOT_FOUND}, preserve=false aResultDetail=-2900
00:00:05.105219 GUI: UIMediumEnumerator: Medium-enumeration finished!
00:00:05.113784 NEM: info: Found optional import WinHvPlatform.dll!WHvQueryGpaRangeDirtyBitmap.
00:00:05.113793 NEM: info: Found optional import vid.dll!VidGetHvPartitionId.
00:00:05.113795 NEM: info: Found optional import vid.dll!VidGetPartitionProperty.
00:00:05.113838 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

See HMR3Init: Attempting fall back to NEM (Hyper-V is active). That said, the "VERR_HGCM_SERVICE_NOT_FOUND" message is not familiar to me. HGCM is "Host Guest Comms Manager", but I don't see any mismatch between host and GAs version that might easily explain it.

[Normann1974]

I have tried downgrading to both v6.1.42 and v6.1.40 with their respective guest additions. The problem now persists. My VM seems to be now broken. Was it the VB7.0 upgrade (or possibly its guest additions) that triggered it? Was it a recent upgrade of a piece of software that I use in the VM (possibly Firefox)? Or did the problem occur some time ago without me realizing it? I can't know and I would know how to find out. My notice of the issue came after I started intense use of Firefox that I didn't do much of before. I guess I'll try reinstaling my VM from scratch and see if the problem is gone.

[Normann1974]

This doesn't seem to be a VB7 issue after all, because the issue is the same in both 6.1.40 and 6.1.42 as previously written. If I stay away from installing Firefox (latest release), the VM doesn't seem to freeze at any point (and for the most time I receive none of the heartbeat entries in the logs) during normal use. So I'm using VB VB 7.0.6 again at this point without Firefox installed in the VM.

/Jan

[fth0]

00:00:05.101595 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005)
  aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}
  aComponent={ConsoleWrap}
  aText={The VBoxGuestPropSvc service call failed with the error VERR_HGCM_SERVICE_NOT_FOUND},
  preserve=false
  aResultDetail=-2900

That said, the "VERR_HGCM_SERVICE_NOT_FOUND" message is not familiar to me. HGCM is "Host Guest Comms Manager", but I don't see any mismatch between host and GAs version that might easily explain it.

FWIW, the log message above comes very early, at a time when neither the guest OS nor the VMMDev (VMM Device) have been started yet. It probably indicates that some host-side VirtualBox component tried to access a Guest Property too early.

[Normann1974]

I strongly believe this is an issue that has its root in Firefox. I have another VM that worked fine until yesterday when Tor Browser updated itself to v12.0.3 (not sure from which version). Now this VM is broken too when Tor is running with the same problematic logs.

/Jan