Opened 5 years ago
Last modified 5 years ago
#19109 new defect
Host resume and VM does not respond
| Reported by: | Iain Waddell | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 6.0.14 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Windows |
Description
Twice today I've resumed my host (after the host has gone to sleep because I've been away from my desk) and the guest has been frozen. The screen display is restored but the mouse isn't active.
After a minute or so the VM crashes and I have to restart the VM.
Logs are attached from after second crash.
Attachments (1)
Change History (4)
by , 5 years ago
| Attachment: | CrashLogs.zip added |
|---|
comment:2 by , 5 years ago
FWIW I hardly ever had VirtualBox lock up (maybe 1 / year) until I upgraded my guest from Windows 10 Pro v1803 to Windows 10 Pro v1903.
I only upgraded because it was about to go out of support. If I'd known I'd have stuck with v1803.
comment:3 by , 5 years ago
This has happened a number of times since my original post. It appears #13874 is considered closed.
Should I upload logs each time it fails?
Would that help anyone who might want to investigate?
I can't reproduce it on demand but it has happened twice in the last 24 hours.
VM Crash logs