virtualbox.org

Hi I've been trying out virtualization on my 3900x and it is awfully slow. It was faster on my 8350.

Currently have 6441MB of RAM allocated, and task manager confirms this.

12 out of 24 threads allocated
executation cap = 100%
Paravirtualization Interface = Hyper-V
Hardware Virtualization = Enable Nested Paging
256MB of video memory allocated, which is 100% of the slider (seems kinda low?)
Graphics controller = VBoxSVGA
Acceleration = Enable 3d Acceleration

I really don't know what else I can do to make the VM faster. The hardware is capable, but it isn't being utilized. My CPU % of VirtualBox tops out at like 10%, GPU 0%, Disk 0 MB/s.
It takes forever to do anything. I've tried Windows 10 and a couple different Linux flavors and they are all laughably slow.

What version of VB are you using?
What Host OS are you using?
When you say "it is awfully slow", what are you doing that is slow?

Can you also supply a log as per the following (from another post):
Provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

AndyCot wrote:What version of VB are you using?
What Host OS are you using?
When you say "it is awfully slow", what are you doing that is slow?

Can you also supply a log as per the following (from another post):
Provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

Version 6.1.32-149290
Windows 10 Host
Everything within the VM is slow. Absolutely everything; loading onto the desktop, animations are choppy, it's like I'm using the world's slowest computer.
I've attached the VM log file.

00:00:06.408255 NumCPUs <integer> = 0x000000000000000c (12)
...
00:00:11.064705 CPUM: Physical host cores: 12

You have left no CPU for the host, which btw includes VirtualBox.

We only care about cores, not threads. Any unused cores in the VM add overhead without adding performance to make up for it. Try reducing the CPU allocation to 2 cores.

Did you mistype the RAM allocation too? 6GB is 6144MB, you typed 6441MB.

This one has the 6.1.32 Hyper-V glitch:

6.1.32 Hyper-V Glitch (remove right 9 characters, time offset in seconds, less than 1 second normal)
00:49:51.313115 /TM/VirtualSync/CurrentOffset 1783406522160 ns

Our forum guru 'fth0' has done some troubleshooting and pins down these possibilities to try (HCVI = Microsoft 'Memory Integrity'):
6.1.32 without Hyper-V
6.1.30 with Hyper-V but without HVCI
6.1.26 with Hyper-V and HVCI.

mpack wrote:

00:00:06.408255 NumCPUs <integer> = 0x000000000000000c (12)
...
00:00:11.064705 CPUM: Physical host cores: 12

You have left no CPU for the host, which btw includes VirtualBox.

We only care about cores, not threads. Any unused cores in the VM add overhead without adding performance to make up for it. Try reducing the CPU allocation to 2 cores.

Did you mistype the RAM allocation too? 6GB is 6144MB, you typed 6441MB.

Oh okay, I'll try 2 cores. I figured it was threads since it goes up to 24. Plus, my host doesn't slow down at all.

No, its correct. Actually touches 6500MB in Task manager. I didn't type in a specific number, just dragged the slider over to a number over 6000. Is that bad?

scottgus1 wrote:This one has the 6.1.32 Hyper-V glitch:

6.1.32 Hyper-V Glitch (remove right 9 characters, time offset in seconds, less than 1 second normal)
00:49:51.313115 /TM/VirtualSync/CurrentOffset 1783406522160 ns

Our forum guru 'fth0' has done some troubleshooting and pins down these possibilities to try (HCVI = Microsoft 'Memory Integrity'):
6.1.32 without Hyper-V
6.1.30 with Hyper-V but without HVCI
6.1.26 with Hyper-V and HVCI.

Without Hyper-V? So should I select "Default" instead or what else?

Using 6.1.30 with Hyper-V but without HVCI seems to have fixed it. Which is weird because I also tried Qtemu and that was having the same problem.

Here is an interesting comment on HCVI.

https://nakedsecurity.sophos.com/2020/0 ... %20shipped.

grahambo_j wrote:Without Hyper-V? So should I select "Default" instead or what else?

No, selecting "Default" is probably in the Paravirtualization setting, which is not the Hyper-V that causes problems with Virtualbox.

"Without Hyper-V" means to turn off Hyper-V on the host OS: see HMR3Init: Attempting fall back to NEM (Hyper-V is active).