CPU intensive

[lanayotech]

CPU intensive

[amitailanciano]

I can't seem to reproduce the issue, can you try quitting Vagrant Manager and deleting the preferences file by issuing rm ~/Library/Preferences/lanayo.Vagrant-Manager.plist from your terminal, as well as killing the cfprefsd process running under your user, then restart Vagrant Manager?

[kostaspt]

I did what you said and it was fine for a while. Then I did a "vagrant halt" and then a "vagrant up" to my main vm machine and CPU usage is back to 88,4%. Could it be related to the specific VM?

[troymccabe]

I'm also seeing this on a daily basis:

I've got just a single VM, even.

[amitailanciano]

I've been unsuccessful recreating this issue, can you please provide your Vagrantfile contents and output of VBoxManage showvminfo <your-troubled-machine-id-here> --machinereadable? Does it happen on every machine you bring up or just the one?

[troymccabe]

The Vagrantfile was generated using PuPHPet (http://puphpet.com). If you pull down a generic local box from there it should exhibit the symptoms we're seeing. I don't have permission to share out our specific box, unfortunately.

The output from showvminfo is here though:

$ VBoxManage showvminfo fbff6f28-6c60-4cf2-ac5e-041c8a4875f3 --machinereadable
name="vm-gsc_default_1400862757434_49488"
groups="/"
ostype="Red Hat (64 bit)"
UUID="fbff6f28-6c60-4cf2-ac5e-041c8a4875f3"
CfgFile="/Users/a464344/VirtualBox VMs/vm-gsc_default_1400862757434_49488/vm-gsc_default_1400862757434_49488.vbox"
SnapFldr="{USER_FOLDER}VirtualBox VMs/vm-gsc_default_1400862757434_49488/Snapshots"
LogFldr="{USER_FOLDER}VirtualBox VMs/vm-gsc_default_1400862757434_49488/Logs"
hardwareuuid="fbff6f28-6c60-4cf2-ac5e-041c8a4875f3"
memory=512
pagefusion="off"
vram=8
cpuexecutioncap=100
hpet="off"
chipset="piix3"
firmware="BIOS"
cpus=1
pae="on"
longmode="on"
synthcpu="off"
bootmenu="messageandmenu"
boot1="disk"
boot2="dvd"
boot3="none"
boot4="none"
acpi="on"
ioapic="on"
Time offset=0rtcuseutc="on"
hwvirtex="on"
nestedpaging="on"
largepages="on"
vtxvpid="on"
vtxux="on"
VMState="running"
VMStateChangeTime="2014-06-02T18:20:31.624000000"
monitorcount=1
accelerate3d="off"
accelerate2dvideo="off"
teleporterenabled="off"
teleporterport=0
teleporteraddress=""
teleporterpassword=""
tracing-enabled="off"
tracing-allow-vm-access="off"
tracing-config=""
autostart-enabled="off"
autostart-delay=0
defaultfrontend=""
storagecontrollername0="IDE Controller"
storagecontrollertype0="PIIX4"
storagecontrollerinstance0="0"
storagecontrollermaxportcount0="2"
storagecontrollerportcount0="2"
storagecontrollerbootable0="on"
"IDE Controller-0-0"="{USER_FOLDER}VirtualBox VMs/vm-gsc_default_1400862757434_49488/packer-virtualbox-iso-disk1.vmdk"
"IDE Controller-ImageUUID-0-0"="035982db-9691-4ccd-8db5-2715ab8df5c8"
"IDE Controller-0-1"="none"
"IDE Controller-1-0"="none"
"IDE Controller-1-1"="none"
natnet1="nat"
macaddress1="0800271A0253"
cableconnected1="on"
nic1="nat"
nictype1="82540EM"
nicspeed1="0"
mtu="0"
sockSnd="64"
sockRcv="64"
tcpWndSnd="64"
tcpWndRcv="64"
Forwarding(0)="ssh,tcp,127.0.0.1,2222,,22"
Forwarding(1)="tcp8033,tcp,,8033,,22"
hostonlyadapter2="vboxnet5"
macaddress2="080027AD5BCD"
cableconnected2="on"
nic2="hostonly"
nictype2="82540EM"
nicspeed2="0"
nic3="none"
nic4="none"
nic5="none"
nic6="none"
nic7="none"
nic8="none"
hidpointing="ps2mouse"
hidkeyboard="ps2kbd"
uart1="off"
uart2="off"
lpt1="off"
lpt2="off"
audio="none"
clipboard="disabled"
draganddrop="disabled"
SessionType="headless"
VideoMode="720,400,0"@0,0
vrde="off"
usb="off"
ehci="off"
SharedFolderNameMachineMapping1="NIIY04ey5Y29"
SharedFolderPathMachineMapping1="{USER_FOLDER}Development/G S"
SharedFolderNameMachineMapping2="vagrant"
SharedFolderPathMachineMapping2="{USER_FOLDER}Development/G S/vm-gsc"
SharedFolderNameMachineMapping3="tmp_vagrant-puppet-3_manifests"
SharedFolderPathMachineMapping3="{USER_FOLDER}Development/G S/vm-gsc/puphpet/puppet"
SharedFolderNameMachineMapping4="tmp_vagrant-puppet-3_modules-0"
SharedFolderPathMachineMapping4="{USER_FOLDER}Development/G S/vm-gsc/puphpet/puppet/modules"
VRDEActiveConnection="off"
VRDEClients=0
vcpenabled="off"
vcpscreens=0
vcpfile="{USER_FOLDER}VirtualBox VMs/vm-gsc_default_1400862757434_49488/vm-gsc_default_1400862757434_49488.webm"
vcpwidth=1024
vcpheight=768
vcprate=512
vcpfps=25
GuestMemoryBalloon=0
GuestOSType="Linux26_64"
GuestAdditionsRunLevel=2
GuestAdditionsVersion="4.3.10 r93012"
GuestAdditionsFacility_VirtualBox Base Driver=50,1401391817024
GuestAdditionsFacility_VirtualBox System Service=50,1401391823588
GuestAdditionsFacility_Seamless Mode=0,1401727860601
GuestAdditionsFacility_Graphics Mode=0,1401727860601

[amitailanciano]

just pulled down the default box and I'm still unable to reproduce the issue, out of curiosity I'm assuming you replaced all occurrences of /Users/a464344/ with {USER_FOLDER}, or is that the exact output?

[troymccabe]

Yeah--missed that specific one, sorry.

I don't know what else would be able to help. I'll pull down just an arbitrary config this weekend and run just that machine to see if it'd be something I can share out. Maybe @kostaspt has more insight at this point?

[amitailanciano]

Just a stab in the dark here, but maybe try sudo opensnoop | grep 'Vagrant Manager' while the CPU is pegged like that and see if that gives you anything useful?

[troymccabe]

Just kicked it back on--will let you know what the output is when I see it
again.

On Tue, Jun 3, 2014 at 11:43 PM, Amitai Lanciano [email protected]
wrote:

Just a stab in the dark here, but maybe try sudo opensnoop | grep
'Vagrant Manager' while the CPU is pegged like that and see if that gives
you anything useful?

—
Reply to this email directly or view it on GitHub
#18 (comment)
.

[kostaspt]

With 90-105% CPU usage, I run this command sudo opensnoop | grep 'Vagrant Manager' and I got this output after a while:

  501  25562 com.apple.IconS   4 /Applications/Vagrant Manager.app/Contents/Resources/AppIcon.icns 
dtrace: 30 dynamic variable drops with non-empty dirty list
    0  25610 spindump       4 /Applications/Vagrant Manager.app 
    0  25610 spindump       4 /Applications/Vagrant Manager.app/Contents 
    0  25610 spindump       4 /Applications/Vagrant Manager.app/Contents/Info.plist 
    0  25610 spindump       4 /Applications/Vagrant Manager.app/Contents/Resources 
    0  25610 spindump       4 /Applications/Vagrant Manager.app/Contents/Resources 
    0  25610 spindump       4 /Applications/Vagrant Manager.app/Contents/Resources/en.lproj 
    0  25610 spindump       4 /Applications/Vagrant Manager.app/Contents/Resources/Base.lproj 
    0  25610 spindump       4 /Applications/Vagrant Manager.app/Contents/Resources/en.lproj/InfoPlist.strings 
dtrace: 247 dynamic variable drops with non-empty dirty list
dtrace: 1 dynamic variable drop with non-empty dirty list

[chriswayoub]

Do you have the "Instruments" application available on your machine? If so, you can follow these instructions to try to get some more info about what might be causing the CPU load.

When the application is using a lot of CPU:

• Start Instruments
• Create a new profile using the "OS X -> CPU -> Time Profiler" template
• In the dropdown at the top of the window that says "All Processes", select "Attach to Process" and choose the Vagrant Manager process from the list
• Hit the record button to start recording data
• Let it run for a while (a minute or so) during the heavy CPU load
• Hit the stop button
• Choose "File -> Save" from the menu, check the box that says "Save Current Run Only"

Send that .trace file that you just saved to [email protected] and we will take a look at it. Hopefully it will provide some hint as to what is eating up all the CPU.

[chriswayoub]

It looks like this might be due to the task output window being open after the task is complete, and it goes into an infinite loop checking for task output.

I've put together a fix for this, but if anyone having the issue can verify that this is the case it would be helpful. Do the people experiencing the issue have "Auto-close task window" unchecked in Preferences? If so, when you experience the issue, can you choose "Windows -> Bring all to front" from the menu when you see the issue happening, and see if there is a task window open? Close the task window and see if the CPU usage goes down.

In any case, I was able to get my CPU to spike when I had an open task window, so we'll be pushing out a fix for this soon.

[chriswayoub]

This is resolved in Release 1.5.4

[travisdetert]

I can verify that version 2.2.1 still has issues. To reproduce the problem, enabling the animated icon on yosemite pegs cpu usage overall at 100%, I suspect it has to do with the windowserver actually rendering the animated icon constantly and the transparency has to have something to do with it.

1). Set refresh to 5 seconds
2). Enable animated icon
3). Watch activity monitor cpu activity go to 100% within minute or less.

4). Disable animated icon, cpu goes back to normal.