High cpu usage in guest on several cores causes severe host lagging.

Discussions related to using VirtualBox on Windows hosts.
Post Reply
kotenok2000
Posts: 3
Joined: 18. Jul 2020, 14:40

High cpu usage in guest on several cores causes severe host lagging.

Post by kotenok2000 »

I have AMD Ryzen 3 3100 4-Core Processor hyperthreaded. When I run atlas simulation job from lhc@home on virtualbox with 4 cores system starts to lag.
I have created a support ticket, but no one responded.
https://www.virtualbox.org/ticket/20749
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: High cpu usage in guest on several cores causes severe host lagging.

Post by mpack »

You allocated 100% of available CPU cores to the VM, leaving none for the host. Host lagging is to be expected, as is instability of both guest and host.

I would not expect any response to your ticket - the BugTracker is not intended to be a discussion area. I wouldn't expect the issue to be given high priority either, given that I don't see an issue. You should really discuss these things in the forums before pestering the devs with it.
kotenok2000
Posts: 3
Joined: 18. Jul 2020, 14:40

Re: High cpu usage in guest on several cores causes severe host lagging.

Post by kotenok2000 »

Ter same happens when i allocate 3 cores.
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: High cpu usage in guest on several cores causes severe host lagging.

Post by mpack »

2 cores is the norm for most VMs.

Also, simulation jobs do typically use a lot of CPU.

Also, try enabling 3D acceleration if the simulation job does a lot of graphics. But first, 8MB graphics RAM is ridiculous: max this parameter out.

Also, you have chosen a generic Linux 2.6 template. Can you not choose something more specific that that?

Also, the VM primary disk is rather small (especially for Linux) at only 20GB. Why so small? Please tell me it isn't because you went for a fixed size VDI!
Post Reply