PS: During the + minutes of the 2nd VM run, which are supposed to measure an idle period, take a short peek into the Performance Monitor, to check if the VMM Load is possibly always Vones: First of all: Apologies for not answering until now!
This will give the statistics to compare with the two baseline statistics.
When selecting the test, perhaps you can choose a test that you deem CPU bound and that takes at least several seconds with t(2V) > t(2H). In the test phase, it would be best if you could execute a single test multiple times so that it takes at least 3 minutes. Start a stopwatch, start the VM, wait for approximately 3 minutes, do a test phase of minutes, and shut down the VM from within the guest OS. This will give the 2nd baseline statistics. Start a stopwatch, start the VM, wait for approximately 3 + minutes, and shut down the VM from within the guest OS. This will give the 1st baseline statistics.Ģ. Start a stopwatch, start the VM, wait for approximately 3 minutes, and shut down the VM from within the guest OS. BTW, the 5th graph (missing in the screenshots) shows the VM-exit counts and would have been interesting, too.Īs a next step, I'd suggest the following procedure: Please run the VM three times (preferably, but not necessarily on the i5-8265U, with an otherwise idle host OS), according to the following instructions, and provide the VBox.log files:ġ. As you already guessed yourself, the blue VMM Load part of the CPU Load is what we should be after. Thank you for the statistics and the performance graphs, which clarify what you always stated.
0 kommentar(er)
