virtualbox.org

Just updated to Version 5.0.22 r108108.

Within a few minutes of running the system hangs with no response. Only solution is to close from VB Manager.

I can replicate the behavior.

I have attached the log files.

Any help or suggestion would be appreciated.

The log shows a VM running for >2 hours, so I assume it is not the correct log.

Was left idol for that time, as soon as you start moving the mouse around doing anything like moving a cell in Excel or typing text in an email it hangs...

Well, I'm still seeing no evidence of a VM problem. The VM closed down smartly when commanded to do so, so the VM hadn't hung, as distinct from the guest OS.

So are you saying Windows is at fault here?

Was running okay until the update.

No, I'm saying that I see no evidence. Without evidence there isn't much I can say. OTOH yes, it looks like a problem inside the guest OS, but not necessarily the guest OS itself. Does the guest task manager pop up if you inject Ctrl+Alt+Del?

This is happening to me as well. Prior to this upgrade, my Windows host (Windows 10) was running fine. Now, after some use of my Windows host, the whole OS freezes (no response even after ctrl-alt-del).

Is there a way to go back to the previous version before 5.0.22 r108108?

Is there a way to go back to the previous version

Yes, just uninstall this version and re-install the earlier one. Don't forget to change the extension pack back to the older version if you had it installed. If you changed the Guest Additions in the guests, those will probably have to be un/reinstalled, too, for a version downgrade.

Unfortunately, I am running into the same issue.

I have Windows 10 on the guest & Host, and I have encountered this freezing almost 4 times already in the last 4-5 hours. I didnt find a pattern, but attached are the logs (had to compress it to be able to upload it).

It only responds to reset through the Menu, Cntrl Alt Del - no response, ACPI shutdown - No response

I had this issue too on 5.0.22. Windows 10 UI appeared to completely hang. The VM itself appeared to be running from a VirtualBox perspective, just had a completely unresponsive Windows UI.

I also have a Oracle Linux VM - this failed to properly boot after updating to 5.0.22 - the base OS would run, but it failed to boot up the UI.

I reverted back to 5.0.18, and all is well again - no idea if it is the extension pack or the guest additions, or the core VirtualBox, and as I have already rolled back I am unfortunately unable to provide any logs. This was running with a Mac host.

Mike

This feedback should really be happening in the Discuss the 5.0.22 release topic if you want to be sure the devs are aware of the issue.

Happily, the issue is already reported and someone even seems to have raised a proper BugTracker ticket for it (15529). Evidently the problem only happens when you allocate >1 vCPUs to the guest. In that case I'd certainly recommend adding to the ticket and then downgrading to your previous version. I wouldn't reduce the number of cores because that could have activation implications, either for Windows itself or other guest software.