VBoxClient futex_

[EgonF]

Virtualbox Version 5.0.10 r104061
Host Windows 10
Guest Mint 17.3

The guest starts with six processes VBoxClient. After a while there is a another process VBoxClient with WCHAN futex_ which consumes ca. 30% cpu time. After killing this process everything works normally.

Why is there this cpu consuming process?

Egon

[mpack]

Please post a VM log file. With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.

[EgonF]

Log file as attachment

[Perryg]

Code: Select all

Guest Log: VBoxService 4.3.34_Ubuntu r104062

First thing to do is remove the Ubuntu guest additions and install the VirtualBox guest additions by clicking the device tab and select to insert guest additions then run in a terminal.

[EgonF]

I've upgraded to VirtualBox 5.1.2 with extensions. After start there is a VBoxClient with futex_ again. The actual log is attached.

In line 962

Code: Select all

00:01:43.793926 VMMDev: Guest Additions information report: Version 4.3.34 r104062 '4.3.34_Ubuntu'

I read Version 4.3.34 Ubuntu but I cannot which is the source.

Egon

[Perryg]

My statement still stands. Replace the guest additions. Remember to remove the OSE fork of guest additions before you install the official version or there will be issues.

Note: there is a difference in guest additions and the extension pack

[EgonF]

Thank you for your note.

I deinstallled the ubuntu guest additions and installed the original.

Now there is another problem - maybe I should change the topic. But this problem is new after changing the guestaddittions.

The system is running. Then I had to work with an other computer. Back to Virtualbox VM I could nearly nothing. The start of a terminal takes over a minute. I closed the VM.

After a new start and another pause there was the same situation. I could not do anything. I looked at the log and found:

#

00:01:06.520737 DSound: Guest source 'Line In' is using host recording device with GUID '{Default device}'
02:07:20.812135 Pausing VM execution, reason 'host suspend'
02:07:20.812369 Changing the VM state from 'RUNNING' to 'SUSPENDING'
02:07:21.008671 PDMR3Suspend: 196 227 602 ns run time
02:07:21.008689 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
02:07:21.008701 Console: Machine state changed to 'Paused'
03:30:13.576729 Resuming VM execution, reason 'host resume'
03:30:13.582408 Changing the VM state from 'SUSPENDED' to 'RESUMING'
03:30:15.402339 Changing the VM state from 'RESUMING' to 'RUNNING'
03:30:15.402373 Console: Machine state changed to 'Running'
03:41:20.033174 Changing the VM state from 'RUNNING' to 'SUSPENDING'
03:41:20.102023 PDMR3Suspend: 68 815 917 ns run time
03:41:20.102068 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
03:41:20.102101 Console: Machine state changed to 'Paused'
03:41:25.152858 GUI: Request for close-action to power VM off.
03:41:25.152910 GUI: Passing request to power VM off from machine-logic to UI session.
03:41:25.152925 GUI: Powering VM down on UI session power off request...

What I see: 1 min 6 sec after start of the VM I could work.Nearly two hours later the host reacts as there were no activities with the computer.Three hours and 39 minutes after start I was back to the computer. The VM state changes to "Running". But I could do nothing. Therefore I closed the VM again.

Should I send the whole log?

Egon

[Perryg]

Should I send the whole log?

Always a good idea.

[EgonF]

Attached,

Egon

[Perryg]

Code: Select all

02:07:20.812135 Pausing VM execution, reason 'host suspend'
02:07:20.812369 Changing the VM state from 'RUNNING' to 'SUSPENDING'

Looks like you issue starts after the host is suspended and then resumed later. I don't do Windows and you should really start a new topic in the Windows host section to see if one of the Windows folks have seen this and can help.

[EgonF]

Thank you

Egon

[EgonF]

I changed in Windows suspend to never.

Now if I leave the VM and come back after a while I have to shutdown the VM and restart the VM. I have to shut down the VM because every keyboard or mouse action takes too much time.

Idea?