VM freezes (Ubuntu guest, Win Host)

[gggeek]

Recently, I started experiencing VM freezes, of VMs that I have been using for a long time.

Setup: Dell latitude 7290 laptop, 16GB ram. VBox 6.1.18. Host os: win10 64bit 20H2. Guest: Ubuntu 20.04 64bit.

Symptoms experienced: start the VM; use it for a while; suspend/unsuspend laptop; attach/detach different external monitors (samsung tv via hdmi, asus zenscreen via usb-c) while having the vm running. At some point, the VM "freezes": its UI becomes unresponsive, I can not access it via ssh or samba shares, nothing. The VirtualBox Manager can be started/stopped, and it shows the VM as 'running', but it clearly has troubles communicating with it (ie. it also gets 'stuck' when trying to act on that vm).
Note that this does not happen every day, and I have not been able to find a way to reproduce it reliably.

Things which changed recently in my previously working config: windows updates and linux kernel updates course, the introduction of the usb-c attached ZenScreen.

The vm log says:

Code: Select all

(snip)
111:27:13.338879 Resuming VM execution, reason 'host resume'
111:27:13.338956 Changing the VM state from 'SUSPENDED' to 'RESUMING'
111:27:13.341132 Changing the VM state from 'RESUMING' to 'RUNNING'
111:27:13.341158 Console: Machine state changed to 'Running'
111:27:15.706308 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
111:27:16.272975 VMMDev: GuestHeartBeat: Guest is alive (gone 4 566 671 773 ns)
111:27:18.570401 TMR3UtcNow: nsNow=1 617 260 432 862 486 857 nsPrev=1 617 233 175 026 520 101 -> cNsDelta=27 257 835 966 756 (offLag=137 643 offVirtualSync=137 643 offVirtualSyncGivenUp=0, NowAgain=1 617 260 432 862 624 500)
111:27:18.578996 VMMDev: Guest Log: 07:00:32.870519 timesync vgsvcTimeSyncWorker: Radical host time change: 27 257 836 000 000ns (HostNow=1 617 260 432 862 000 000 ns HostLast=1 617 233 175 026 000 000 ns)
111:27:20.437390 Audio: Device configuration of driver 'DSoundAudio' has changed
111:27:28.574773 VMMDev: Guest Log: 07:00:43.581704 timesync vgsvcTimeSyncWorker: Radical guest time change: 27 257 450 862 000ns (GuestNow=1 617 260 443 581 682 000 ns GuestLast=1 617 233 186 130 820 000 ns fSetTimeLastLoop=true )
111:28:09.858096 Audio: Device configuration of driver 'DSoundAudio' has changed
111:28:09.991549 Audio: Device configuration of driver 'DSoundAudio' has changed
111:28:09.993603 Audio: Device configuration of driver 'DSoundAudio' has changed
111:28:36.846476 Audio: Device configuration of driver 'DSoundAudio' has changed
116:07:31.133684 Audio: Device configuration of driver 'DSoundAudio' has changed
116:10:16.220118 Audio: Device configuration of driver 'DSoundAudio' has changed
117:25:01.676797 NAT: DHCP offered IP address 10.0.2.15
117:34:06.693056 Audio: Device configuration of driver 'DSoundAudio' has changed
118:21:29.593253 Audio: Device configuration of driver 'DSoundAudio' has changed
118:49:27.617564 Pausing VM execution, reason 'host suspend'
118:49:27.617677 Changing the VM state from 'RUNNING' to 'SUSPENDING'
124:38:57.027920 NAT: Link down
124:39:38.456077 GUI: UIMachineLogic: Host-screen count changed
135:58:41.752133 GUI: UIMachineLogic: Host-screen count changed
136:46:17.587653 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={10cd08d0-e8b8-4838-b10c-45ba193734c1} aComponent={MouseWrap} aText={Could not send the mouse event to the virtual mouse (VERR_PDM_NO_QUEUE_ITEMS)}, preserve=false aResultDetail=-2807

followed by a slew of identical messages about mouse events.

So far I managed to hard-reset the VM only by killing the vbox processes on the host, but I am afraid that ifthis keeps happening at some point I'll run into a non-recoverable disk corruption problem when restarting it...

Any help is appreciated

[gggeek]

ps. sorry, I wanted to post this in the windows-hosts forum... not sure how it can be moevd now :-O

[mpack]

Topic moved.

The log is truncated. Please do NOT copy logs out from VMs that are still running!

From the fragment of the log that has been provided, the issue seems to be a problem with the guest OS, not with the VM.

111:27:15.706308 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago

The various audio related log events look suspicious to me. I would test with audio in/out disabled.

A modern VM should have substantially more than 16MB of graphics RAM allocated to it. You have plenty of RAM on your host, so I'd allocate 128MB to the VM graphics section. Performance should also improve if you enabled 3D acceleration.

You should probably add a second CPU core as well, though that's debateable since you only have two in total.