Ubuntu host / Kali Guest: VM freezes any time it's left for a while

[socratis]

Did you try with 1 monitor instead of 3? Are the monitors all the same DPI?

[0xdf]

The monitors are different sizes and I assume different DPI. I've attached a screengrab that shows my setup.

[socratis]

1) You didn't tell me if you tried with 1 monitor only.
2) You're not the only one: [Meta] Ubuntu 18.04 freezes

[0xdf]

1) I have not tried with only one monitor. Would that be just unplugging the other two? Or do that and then reboot?
2) So I guess that's an issue with VBOX that's being looked at? Is that what that means?

I've solved this for now by just not letting my computer sleep. I'm not totally comfortable with this, but it's a temporary solution. Any other suggestions certainly welcome.

[socratis]

1. I would unplug the two secondary monitors, leaving just my main one, and reboot.
2. I don't know if it's been looked at or not. I simply realized that there were three (at least) threads dealing with essentially the same issue, and since it was too late to merge the threads, I put a temporary sticky so that we know how widespread the problem is.

[virtferbox]

Update, this is still happening.

Host: Windows 10, Virtualbox version 6.0.20 r137117 (Qt5.6.2)
Guest: Ubuntu 18.04 (up-to-date)

After host goes to sleep, the linux guest won't respond upon resume. However it IS alive and running, as the clock in the login screen keeps ticking and showing the correct time. Also, the icons at the top right (e.g. network) change if I disconnect the network cable, and put the host offline ...

So far it seems the guest is unresponsive to any mouse + keyboard input (sending Ctrl-Alt-Del or Ctrl-Break from the virtualbox statusbar buttons are also ignored).

Please investigate and fix this issue!

These are the last lines in the virtualbox VM log ... the last three entries may correspond to the Ctrl-Alt-Del + Ctrl-Break I sent:

Code: Select all

2:32:08.889659 TM: Giving up catch-up attempt at a 8 864 955 769 259 ns lag; new total: 39 513 446 390 919 ns
12:32:08.889728 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 8866 seconds ago
12:32:08.890315 TMR3UtcNow: nsNow=1 587 983 310 380 550 769 nsPrev=1 587 974 439 379 332 900 -> cNsDelta=8 871 001 217 869 (offLag=18 531 offVirtualSync=39 513 446 409 450 offVirtualSyncGivenUp=39 513 446 390 919, NowAgain=1 587 983 310 380 569 300)
12:32:08.890428 VMMDev: Guest Log: 10:26:57.225100 timesync vgsvcTimeSyncWorker: Radical host time change: 8 871 001 000 000ns (HostNow=1 587 983 310 380 000 000 ns HostLast=1 587 974 439 379 000 000 ns)
12:32:08.890477 VMMDev: Guest Log: 10:26:57.225199 timesync vgsvcTimeSyncWorker: Radical guest time change: 8 875 126 748 000ns (GuestNow=1 587 983 217 225 087 000 ns GuestLast=1 587 974 342 098 339 000 ns fSetTimeLastLoop=false)
12:32:08.895670 VMMDev: GuestHeartBeat: Guest is alive (gone 8 866 220 837 671 ns)
12:32:12.895925 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
12:38:38.194569 VMMDev: GuestHeartBeat: Guest is alive (gone 389 298 889 678 ns)
14:31:02.997776 TM: Giving up catch-up attempt at a 5 262 851 399 016 ns lag; new total: 44 776 297 789 935 ns
14:31:02.997854 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 5264 seconds ago
14:31:02.998133 VMMDev: GuestHeartBeat: Guest is alive (gone 5 264 039 087 990 ns)
14:31:02.998371 TMR3UtcNow: nsNow=1 587 990 444 488 614 300 nsPrev=1 587 985 177 994 596 248 -> cNsDelta=5 266 494 018 052 (offLag=0 offVirtualSync=44 776 297 789 935 offVirtualSyncGivenUp=44 776 297 789 935, NowAgain=1 587 990 444 488 614 300)
14:31:02.998483 VMMDev: Guest Log: 12:25:27.262863 timesync vgsvcTimeSyncWorker: Radical host time change: 5 266 494 000 000ns (HostNow=1 587 990 444 488 000 000 ns HostLast=1 587 985 177 994 000 000 ns)
14:31:02.998586 VMMDev: Guest Log: 12:25:27.262957 timesync vgsvcTimeSyncWorker: Radical guest time change: 5 269 081 750 000ns (GuestNow=1 587 990 327 262 850 000 ns GuestLast=1 587 985 058 181 100 000 ns fSetTimeLastLoop=false)
14:31:05.006833 NAT: Link down
14:31:06.999035 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
14:31:08.007661 NAT: Link up
14:31:08.012998 NAT: DNS#0: 192.168.0.1
14:31:08.665678 NAT: Link down
14:31:10.026116 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenWorkAreaResized: Screen 0 work area is formally resized to: 0x0 x 1920x1042
14:31:10.026143 GUI: UIMachineLogic: Host-screen available-area changed
14:31:10.282133 GUI: UIMachineView::sltPerformGuestResize: Sending guest size-hint to screen 0 as 1920x962 if necessary
14:31:10.294531 VMMDev: SetVideoModeHint: Got a video mode hint (1920x962x32)@(0x0),(1;0) at 0
14:31:10.300423 GUI: UIMediumEnumerator: Medium-enumeration finished!
14:31:10.321924 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=1920 h=1000 bpp=0 cbLine=0x0 flags=0x2 origin=0,0
14:31:10.457455 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000000e9ca000 w=1920 h=962 bpp=32 cbLine=0x1E00 flags=0x1 origin=0,0
14:31:10.458944 GUI: UIMachineLogic: Guest-screen count changed
14:31:11.665886 NAT: Link up
14:31:11.681066 NAT: DNS#0: 192.168.0.1
14:31:13.131375 NAT: DHCP offered IP address 10.0.2.15
14:32:10.530773 VMMDev: GuestHeartBeat: Guest is alive (gone 67 532 637 284 ns)
14:33:35.290132 GUI: UIMediumEnumerator: Medium-enumeration started...
14:33:35.323241 GUI: UIMediumEnumerator: Medium-enumeration finished!
14:33:39.895963 GUI: UIMediumEnumerator: Medium-enumeration finished!

[mpack]

Partial logs == no attention.

Only provide full logs, as zip attachments.

Also, this is a user discussion forum, none of us are in a position to "investigate and fix", unless you do it yourself of course.