VM client keep unresponsive

[ryansiow]

hi all,
i am encounter newer VB version with new problem, the VM client keep freeze or unresponsive within 3-10sec at every 10mins interval.

VB version: 6.1.6r137129
VM Host : 32core with 196GB RAM, 1.8TB PCIe SSD, Windows Server 2019
VM Host BIOS: Disable Hyper-threading {to avoid CPU core allocation issue}
VM client : win2019 with Ms SQL , 100GB ram, 12core, 600GB

this happen when the VM host cpu core utilization as below, all 12core assign to VM client marking 100% utilization but under VM client the CPU usage is still low consumption

VM host CPU usage: <40%
VM host Memory usage: <50%

VM client CPU usage: <10%
VM client Memory usage: <20%

regards
ryan

[ryansiow]

VM Host and VM client cpu utilization
http://www.rentalanns.com/temp/cpu.jpg

[mpack]

Please provide a VM log file. With the VM fully shut down, right click it in the GUI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

[ryansiow]

thank for quick respond, as requested, the full log is attached

i did reduce the VM client from 100Gb RAM to 64GB but still same issue.

[ryansiow]

just curious, should i enable hyperthreading on VM Host BIOS?
will this help to improve performance on VM client with 12vCPU.

[scottgus1]

VM Host : 32core with 196GB RAM, 1.8TB PCIe SSD, Windows Server 2019

This matter will require hands-on testing. Please ship the computer to me, I will get you a shipping label shortly... JK. Very well-provisioned system!

As I have read, disabling host CPU hyperthreading slows down the host PC. So turn that hyperthreading back on.

Just remember that hyperthreading does not count for Virtualbox cores. Divide that host Task Manager core count by two when figuring out how many cores to give a guest.

I see a few "DevHeartbeatFlatlinedTimer"s in the log, indicating a 4-second failure in the heartbeat signals the guest sends the host. But I don't see why.

i am encounter newer VB version with new problem

Does this mean you had an older Virtualbox version that did not show this problem?

[ryansiow]

thanks for reply, previous ver 6.1.2 never encounter this problem

as refer to vbox.log, i saw few times the DevHeartbeatFlatlinedTimer and 4-second lost on heartbeat too, still no idea why it happens

[scottgus1]

If you revert to 6.1.2 does the problem go away? And go back to 6.1.6 does it come back?

[ryansiow]

i not plan to revert back, just worries the VM will crash or problem after revert back to 6.1.2

[scottgus1]

Reverting temporarily will show if it is a problem with 6.1.6 or a new problem with your guests. If you don't want to revert as a test then there may be nothing we can do.

[ryansiow]

i change VM host new setting as per today, so far never encounter any issue.

1. update latest bios
2. update latest windows 2019 patch
3. enable Hyperthreading on BIOS
4. compact VM image (360GB -> 260GB)
5. change VM version (win 2016->win 2019)

i will monitor it and keep update at here, thank for support.

[scottgus1]

OK, sounds fine. We will stay tuned. Curious if enabling hyperthreading again had something to do with it?

BTW, on the subject of a revert breaking the guest, we can't say it won't happen, but it is very rare, haven't seen any reports of such happening in the forum.

However, a complete FC-confirmed copy of the fully shut-down guest folder and all disk files related to the guest is a good reliable backup, and if the guest failed, a restore of the backup copy would put the guest back on good working order after the re-upgrade.

It would be a good idea to take backups anyway.

[ryansiow]

the VM client seen working fine, but after 1 day the same problem occur again.
multiple vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago show in log

i attached herewith the latest Vbox.log