VB 6.1.32 Ubuntu Locks Up
-
tempralstorm
- Posts: 1
- Joined: 11. Feb 2022, 16:58
VB 6.1.32 Ubuntu Locks Up
I have had multiple different guests lock up since upgrading to VB 6.1.32. Here is the latest log file after reinstalling Ubuntu
- Attachments
-
- Ubuntu-2022-02-11-08-55-33.zip
- (21.23 KiB) Downloaded 5 times
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: VB 6.1.32 Ubuntu Locks Up
Thanks for the log, but unless the VM environment crashed completely, the log was taken while the VM was still open, which cuts off some diagnostic data needed to diagnose this.
Two things right off: Hyper-V is enabled on the host OS, and host RAM is too taxed:
If you can provide a 6.1.32 log from after the VM has been shut down, and also revert to your previous version and see if the VMs go back to running fine, provide a complete log for that run too, ti would help.
Start the VM from full power off, not save-state. Run until you see the problem happen, then shut down the VM from within the VM OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
Please right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.
Two things right off: Hyper-V is enabled on the host OS, and host RAM is too taxed:
The missing diagnostic data might help pin this down further, since Ubuntu is reported to possibly work OK in a Virtualbox VM while Hyper-V is enabled.00:00:14.501808 Host RAM: 7542MB (7.3GB) total, 1136MB available
00:00:14.655747 RamSize <integer> = 0x00000000c0000000 (3 221 225 472, 3 072 MB, 3.0 GB)
If you can provide a 6.1.32 log from after the VM has been shut down, and also revert to your previous version and see if the VMs go back to running fine, provide a complete log for that run too, ti would help.
Start the VM from full power off, not save-state. Run until you see the problem happen, then shut down the VM from within the VM OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
Please right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.