virtualbox.org

Upgrading from 4.3.28-100309 to 5.0.0-101573

After the upgrade VirtualBox on Debian Jessie 8.1 - increased load handling 6x
The processor used on one virtual machine 12-15% - in a virtual machine vCPU-intensive nothing

Before - Normally 2-3%

Also load has increased?

Reason system load for this: vboxdrv

Here is the error - the system load.
When I stopped vboxdrv load on the system back to normal.
Then I ran and checked, how it behaves in /proc/loadavg

09:02:19 up 55 min, 1 user, load average: 0,00, 0,02, 0,09
Starting VirtualBox kernel modules ...done.
After 1 minute:
09:03:19 up 56 min, 1 user, load average: 0,63, 0,20, 0,14
09:04:19 up 57 min, 1 user, load average: 0,87, 0,35, 0,20
09:05:19 up 58 min, 1 user, load average: 1,00, 0,48, 0,25
09:06:19 up 59 min, 1 user, load average: 1,00, 0,58, 0,30
09:07:19 up 1:00, 1 user, load average: 1,00, 0,65, 0,34
09:10:19 up 1:03, 1 user, load average: 1,00, 0,81, 0,46
09:13:19 up 1:06, 1 user, load average: 1,00, 0,90, 0,55
and
09:31:53 up 1:25, 1 users, load average: 1,87, 1,77, 1,32

What data do You need to diagnose?

Just to be clear, this happens when you don't run *any* VMs at all right? Just having vboxdrv loaded?

1. Could you paste the dmesg output after you load vboxdrv?

2. If you can upload VBox.log after starting a VM with VirtualBox 5.0, that would be useful.

Yes of course
The module itself vboxdrv

I will send the LOG file - priv messages

Please attach VBox.log here to this thread, there is no need for sending it as a private message.

Could you also please post output of:
after loading vboxdrv.

Excuse me, I did:

1.--
lsmod |grep vb
vboxpci 23078 0
vboxnetadp 25443 0
vboxnetflt 27648 0
vboxdrv 367029 3 vboxnetadp,vboxnetflt,vboxpci

2.--
csi-02:/# rmmod vboxpci vboxnetadp vboxnetflt vboxdrv

3.--
/etc/init.d/vboxdrv start

[21470.479046] vboxdrv: Found 8 processor cores
[21470.495764] vboxdrv: TSC mode is Invariant, tentative frequency 3499976295 Hz
[21470.495766] vboxdrv: Successfully loaded version 5.0.0 (interface 0x00230001)
[21470.698914] VBoxNetFlt: Successfully started.
[21470.700309] VBoxNetAdp: Successfully started.
[21470.701693] VBoxPciLinuxInit
[21470.702534] vboxpci: IOMMU not found (not registered)

4.--
Start one VM, only Desktop, wait 30 s.

dudekm 22422 29.8 3.2 4944440 1078500 ? SLl 14:07 0:26 /usr/lib/virtualbox/VirtualBox --comment Win7-64bit-Temp --startvm b9cbd6ea-8d8a-443d-9d58-922ef7c9eb09 --no-startvm-errormsgbox

In case it was missed, as I edited the previous post of mine;

Could you also please post output of: after loading vboxdrv.

Are you sure vboxdrv was loaded when you took the "ps" output? I was expecting to see 2 VBox kernel thread in the output...

Ramshankar wrote:In case it was missed, as I edited the previous post of mine;

Could you also please post output of:

Code: Select all

    ps -elf

after loading vboxdrv.

I thought that it was unnecessary
No, I have not seen

Ramshankar wrote:Are you sure vboxdrv was loaded when you took the "ps" output? I was expecting to see 2 VBox kernel thread in the output...

I thought you check if nothing else overloading the system.
See the previous answer.

I think that the attached data sufficient for diagnosis.
And certainly sufficient for this - to get the bug.

No guest and host.

"Virtual PC" shows vCPUs 0%
Host maintaining a "Virtual PC" - shows CPU 12-16%

Read carefully.

Please see: Load average
On the Host as you have it a lot.

Ps. Do not Ubuntu and Debian

Per your request I have removed my posts and will not reply to you again. However I finally figured out what you were seeing and have found the issue. Ram if you like you can PM me for my findings.

Perryg wrote:Per your request I have removed my posts and will not reply to you again. However I finally figured out what you were seeing and have found the issue. Ram if you like you can PM me for my findings.

Thank You

Perryg wrote:Per your request I have removed my posts and will not reply to you again. However I finally figured out what you were seeing and have found the issue. Ram if you like you can PM me for my findings.

Just for the record, this has been taken to the vboxdev mailing list with the subject "Excessive load averages with nothing running". We'll continue tracking this issue there as I'm more likely to get direct feedback there. If it turns out to not be fixed within a patch or two, we should open a proper bug ticket for it.