win10 guest in win10 freeeze

[Skygazer]

Hi,

Im new here, I seek pardon if I missed any rules.
My client machine keeps on freezing. I notice that this only happens when I am in Microsft SQL Server Management Studio or I am copying some texts.

Host specs is Intel i7-8750H with 32GB RAM and 256GB SSD.
Guest is 6 cores with 16GB RAM and 21GB free disk space.

Please advice if I can change anything to make my guest more reliable.

Thanks,
skygazer

[mpack]

For future reference, please provide one relevant log, not 10 logs of unknown relevance. Where I come from, giving me 10 times more unpaid work than necessary is called "taking the piss" and my first impulse is to move to the next topic. I fought the urge this time.

The first thing I'd do is reduce the number of CPU cores allocated to the VM to 2. You have 6 cores TOTAL. The idea with a VM is to share resources, you can't assign ALL resources to the VM and expect good stability and performance.

The RAM allocation seems a bit high as well, but for the moment your host has enough. You might want to consider if the VM actually needs so much.

You have not installed the extension pack on the host, so you won't have access to USB2/USB3 and a few other things.

Otherwise, I'm seeing no sign of freezes - though I only looked at the first log in the first zip. The VM booted in about 45 seconds, total uptime was only about 12 minutes.

[Skygazer]

Hi mpak,

Thank you for the response and patience to reply for providing exessive logs.
I wasnt really sure which logs I was supposed to submit so I packed them all whenever the issue occurs.

This VM is a development machine so I have split resources with the host 6 threads to the guest and 6 to the host.
Does this make sense or I should lower it down to 5?

My guest needs 9GB RAM minimum to run stable, would you still recommend lowering it down to around 12GB or it should be lower?

It does freeze very often, first sign that it will freeze is that my mouse cursor changes to a garbled block with horizontal lines then it stops.

Thank you very much,
skygazer

[scottgus1]

I have split resources with the host 6 threads to the guest and 6 to the host.

Not quite, look at the 6-cores link Mpack posted, 'tis Intel's take on the subject. Hyperthreads don't help Virtualbox, so you have only 6 cores, and the guest is set to use all of them if it wants. If it does then the host can go unstable.

Re which log, usually the last log that showed the problem, or was logging when the problem occurred, is the log to zip and post. Some guest problems don't show in the log, like yours doesn't show, unfortunately. The hardening log is not needed if the last line Exit Code is 0x0.

If the guest was not freezing in the last log that you had, then start the guest from full power off, not save-state.

Start a stopwatch and run until you see the problem happen. Note the time on the stopwatch. Then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.

Please zip and post just the latest guest vbox.log, using the forum's Upload Attachment tab. Also, post the stopwatch time, so we know approximately how far into the log the issue developed.

Reduce core count to the point where the full load on the guest OS fills up all the set cores on the host. Example: if the 6-core guest uses average 66% of the host's core capability while the host is doing nothing, then you can use 66% of the cores you have set in the guest, or 4 cores. Extra cores only slow down a guest, due to extra scheduling overhead on the host. At least drop it to 5.

[Skygazer]

Hi scottgus1,

All of the Logs I have posted are zipped right after the freeze and I need to power off the guest VM.

Attached is the Log of a new one. It froze after 18minutes.

Thank you,
skygazer

[scottgus1]

I don't see any difficulties in the vbox.log. I did not check the other logs. I assume that vbox.log was the last log that showed the problem, per the instructions above.

Was this guest running your development environment when it crashed? What happens if you run an animated GIF or reasonable video in a media player on repeat and nothing else? Does the guest seize then?

Since it's Windows 10 guest, try 2 cores.

[mpack]

Every time VirtualBox starts it creates a new "VBox.log". The previously existing file of that name is renamed to "VBox.log.1" so that it won't be lost. The previous "VBox.log.1" file is renamed to "VBox.log.2", and so on. Logs from the last 4 sessions are kept.

We DO NOT need to see repeated logs, i.e. logs from multiple and overlapping session histories. We only need to see one log corresponding to one session that demonstrates the problem.

[Skygazer]

Hi everyone,

Dropping the cores to 4 made it more stable. Dropping to 2 made it rock solid.
However I can't work on 2 cores always so I always run it in 4 cores.

I have also tried watching youtube in different resolutions and watching HD and 4k videos in VLC but it doesnt trigger the freeze.

I wasnt able to catch the log when this happens but I have identified some specifics that almost certainly trigger the crash.
*when I type a chat message in the GoToMeeting app
*when I copy a lot of text in excel and put it somewhere else in Excel too
*viewing PDF's in iframes in Firefox

Hope you can recommend me more options to make rock solid like it was when it was in version 5 of virtualbox.

Thank you,
skygazer

[Skygazer]

Hi everyone,

Got a fresh crash log. I just visited is a site with with a alot of svg pictures using Firefox.

Thank you,
skygazer

[mpack]

That log contains no sign of a VM crash.

00:50:01.668502 GUI: User request to power VM off.
00:50:01.668792 GUI: Passing request to power VM off from machine-logic to UI session.

It then proceeds to an orderly shutdown. Please note that guest OS crashes are not the same as VirtualBox crashes, and the two don't have to be related at all.

[scottgus1]

Please note that guest OS crashes are not the same as VirtualBox crashes

To be able to tell the difference:

If the guest's Virtualbox window stays open, and the error/crash is something that typically appears in the OS installed in the guest, and no Virtualbox errors appear, then it is a guest crash, or a guest app crash, and you would troubleshoot it directly through the guest OS's or the app's help channels. Virtualbox is still working.

If the guest's Virtualbox window closes, seizes, no longer responds to the window's menu selections, a Virtualbox error box appears, etc, then it's a Virtualbox problem or a host problem.

We would not be able to diagnose guest OS or app problems typically. We have the goal of getting Virtualbox to run stably, and there may be host changes that need to be made to help that goal along.