VB 7.0.9 - Windows VM freezes on Ventura 13.3.1 (a)

[chavito]

Hi,

I have a VM instance with Windows as a OS that was created using VirtualBox 6.1.x

Everything worked just fine for quite a time until I recently updated both my macOS to Ventura 13.3.1 (a) (22E772610a) and the VirtualBox Host to 7.0.9 r156991 (Qt5.15.2). Since then, I've been unable to work properly with the VM.
The symptoms are that the guest simply freezes shortly after startup. No response from mouse input, no activity on the open apps... The only option then is to force a shutdown on the machine. The time-to-freeze window doesn't seem to follow a pattern, sometimes merely seconds upon startup, sometimes a few minutes... Always too little time for me to be able to work.

I've tried to change some settings in the VM configuration following advice on other threads in this forum, but to no avail.

Attached are the zipped logs of my last attempt. Unfortunately, the only line I understand in those logs is this one that appears at the end:

Code: Select all

00:00:52.421241 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago

Any help would be much appreciated

[mpack]

Possibly it is due to memory over-committment. Your host should have RAM available before you assign it to a guest.

00:00:00.956813 Host RAM: 16384MB (16.0GB) total, 9054MB (8.8GB) available
...
00:00:01.006032 RamSize <integer> = 0x0000000240000000 (9 663 676 416, 9.0 GiB)
00:00:01.006244 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128.0 MiB)

Try reducing VM RAM to 6GB (6144MB).

Otherwise, the VM log is truncated and it's an unsupported test build (7.0.9), so there isn't much else I can say.

[multiOS]

In addition to mpack's suggestion I noticed that the Log states:

00:00:12.228525 VMMDev: Guest Additions information report: Version 7.0.9 r156986 '7.0.9'

I'd suggest that you update the guest additions to the to the latest Test Build version, i.e. r157031 or later. That combination is working for me with a Windows 10 VM, but earlier Test Build and also Release versions up to 7.0.8 resulted in a similar issue to the one you describe.

[chavito]

Hi,

First of all, thanks for the attention and the time committed to help.

Possibly it is due to memory over-committment. Your host should have RAM available before you assign it to a guest.
...
Try reducing VM RAM to 6GB (6144MB).

Thanks for the tip, that makes quite a lot sense, one more thing learnt. Unfortunately, this setting change hasn't resolved the issue.

Otherwise, the VM log is truncated and it's an unsupported test build (7.0.9), so there isn't much else I can say.

My fault, I wasn't aware that I was dealing with a test build, I can clearly see that the upfront main version is 7.0.8; I might have to try with that one.

I'd suggest that you update the guest additions to the to the latest Test Build version, i.e. r157031 or later.

Thanks for the suggestion, I'll give it a try.
The following question would be how to access the version you mention; up until now I was used to install Guest Additions via the *.iso present in the Virtual Box Installation. Also, is there a way to install Guest Additions without the VM running??

Again, thanks a lot for your help and your time .

[multiOS]

https://www.virtualbox.org/wiki/Testbuilds

[chavito]

Hi,

Thanks a lot again, I'll keep trying.

[fth0]

Your problems should be fixed in the VirtualBox test builds 7.0.9r157071 and newer. For details, see 21596. I think you should update the whole VirtualBox installation, not only the VirtualBox Guest Additions.

[chavito]

Your problems should be fixed in the VirtualBox test builds 7.0.9r157071 and newer. For details, see 21596. I think you should update the whole VirtualBox installation, not only the VirtualBox Guest Additions.

Hi,

Thanks so much for everybody's help, it's greatly appreciated.

I reinstalled the whole VirtualBox taking into account the indicated test build; but it didn't seem to do the trick, the guest kept freezing.

Curiously, I've managed to keep the thing running for a few hours by booting up Windows in "safe mode"
This is enough for me to run the apps I need the VM for... I think I won't invest much more time on this issue.

Anyway, thanks again for your help and your time.