{"action":"created","issue":{"url":"https://api.github.com/repos/vmware/open-vm-tools/issues/126","repository_url":"https://api.github.com/repos/vmware/open-vm-tools","labels_url":"https://api.github.com/repos/vmware/open-vm-tools/issues/126/labels{/name}","comments_url":"https://api.github.com/repos/vmware/open-vm-tools/issues/126/comments","events_url":"https://api.github.com/repos/vmware/open-vm-tools/issues/126/events","html_url":"https://github.com/vmware/open-vm-tools/issues/126","id":196754778,"number":126,"title":"vmhgfs-fuse keeping one core at 99% CPU","user":{"login":"bosconi","id":5504972,"avatar_url":"https://avatars.githubusercontent.com/u/5504972?v=3","gravatar_id":"","url":"https://api.github.com/users/bosconi","html_url":"https://github.com/bosconi","followers_url":"https://api.github.com/users/bosconi/followers","following_url":"https://api.github.com/users/bosconi/following{/other_user}","gists_url":"https://api.github.com/users/bosconi/gists{/gist_id}","starred_url":"https://api.github.com/users/bosconi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bosconi/subscriptions","organizations_url":"https://api.github.com/users/bosconi/orgs","repos_url":"https://api.github.com/users/bosconi/repos","events_url":"https://api.github.com/users/bosconi/events{/privacy}","received_events_url":"https://api.github.com/users/bosconi/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-12-20T19:14:24Z","updated_at":"2016-12-20T22:01:07Z","closed_at":null,"body":"\r\nI have some Python scripts that run multiple instances of https://www.consul.io/ in the same VM, for a few minutes and then terminate them. The processes write a modest amount of logs to /tmp - of the order of 200 files, totaling around 5-100MB of text - which I then move to the host fs via the shared mount. I used to write the logs straight to shared, and had the same issue.\r\n\r\nAll this works fine. But if I leave the VM idle (for some as yet undetermined amount of time ) within a few hours I often notice that vmhgfs-fuse is monopolizing a core:\r\n\r\nFrom top:\r\n```\r\n  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND\r\n 1308 root      20   0 1210144 106840    928 S  99.3  2.6 132:50.77 vmhgfs-fuse\r\n  598 root      20   0  185728  10128   8892 S   2.3  0.3   1:47.54 vmtoolsd\r\n23675 root      20   0       0      0      0 S   1.0  0.0   0:34.54 kworker/1:0\r\n22173 root      20   0    7448   2284   2044 S   0.3  0.1   1:02.70 updatedb.mlocat\r\n```\r\n\r\nIt looks like it is sat in a spinlock:\r\n```\r\nvagrant@ubuntu-1604-vmware:~/shared$ sudo strace -p 1308\r\nstrace: Process 1308 attached\r\nfutex(0x7fffdd52fa40, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, ffffffff\r\n```\r\n\r\n```\r\nvagrant@ubuntu-1604-vmware:~/shared$ sudo perf record -F 99 -p 1308 -g -- sleep 10\r\nvagrant@ubuntu-1604-vmware:~/shared$ sudo perf report -f --stdio\r\n...\r\n# Children      Self  Command      Shared Object                 Symbol\r\n# ........  ........  ...........  ............................  ...............................\r\n#\r\n   97.34%     0.00%  vmhgfs-fuse  vmhgfs-fuse                   [.] 0xffffffffffc087a4\r\n           |\r\n           ---0x87a4\r\n              |\r\n              |--0.10%-- apic_timer_interrupt\r\n              |          smp_apic_timer_interrupt\r\n              |          irq_exit\r\n              |          __do_softirq\r\n              |          rcu_process_callbacks\r\n              |          rcu_report_qs_rnp\r\n              |          rcu_gp_kthread_wake\r\n              |          __wake_up\r\n              |          _raw_spin_unlock_irqrestore\r\n              |\r\n               --0.10%-- retint_user\r\n                         prepare_exit_to_usermode\r\n                         exit_to_usermode_loop\r\n\r\n   97.13%    97.13%  vmhgfs-fuse  vmhgfs-fuse                   [.] 0x00000000000087a4\r\n           |\r\n           ---0x87a4\r\n\r\n    1.23%     0.00%  vmhgfs-fuse  vmhgfs-fuse                   [.] 0xffffffffffc0870d\r\n           |\r\n           ---0x870d\r\n```\r\n\r\nRestarting the VM with `shutdown -r now` brings the VM back without the shared fs mounted (`/home/vagrant/shared` is empty). `vagrant reload` brings the share back properly, but the problem returns eventually. Not immediately, and not immediately after running the scripts that produce and move the log files.\r\n\r\nOutput of `vagrant --debug reload` is here: https://gist.github.com/bosconi/c8e020e3e3ab3254dc57e9ab6c8a3c65\r\n\r\nEnvironment info below. Let me know if there are any tests I can run to help isolate this.\r\n\r\nJon.\r\n\r\nHost: OS X 10.11.6\r\nFusion Version: Pro 8.5.3\r\nGuest: cbednarski/ubuntu-1604 v2 (https://atlas.hashicorp.com/cbednarski/boxes/ubuntu-1604)\r\nVagrant: Installed Version: 1.9.1\r\nVagrant plugins:\r\nvagrant-aws (0.7.2)\r\n - Version Constraint: > 0\r\nvagrant-share (1.1.6)\r\n - Version Constraint: > 0\r\nvagrant-vmware-fusion (4.0.15)\r\n - Version Constraint: > 0\r\nVagrantfile: https://gist.github.com/bosconi/3cafd90cca0f6eb951cd60419695fe6f\r\n"},"comment":{"url":"https://api.github.com/repos/vmware/open-vm-tools/issues/comments/268372072","html_url":"https://github.com/vmware/open-vm-tools/issues/126#issuecomment-268372072","issue_url":"https://api.github.com/repos/vmware/open-vm-tools/issues/126","id":268372072,"user":{"login":"lousybrit","id":15133080,"avatar_url":"https://avatars.githubusercontent.com/u/15133080?v=3","gravatar_id":"","url":"https://api.github.com/users/lousybrit","html_url":"https://github.com/lousybrit","followers_url":"https://api.github.com/users/lousybrit/followers","following_url":"https://api.github.com/users/lousybrit/following{/other_user}","gists_url":"https://api.github.com/users/lousybrit/gists{/gist_id}","starred_url":"https://api.github.com/users/lousybrit/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lousybrit/subscriptions","organizations_url":"https://api.github.com/users/lousybrit/orgs","repos_url":"https://api.github.com/users/lousybrit/repos","events_url":"https://api.github.com/users/lousybrit/events{/privacy}","received_events_url":"https://api.github.com/users/lousybrit/received_events","type":"User","site_admin":false},"created_at":"2016-12-20T22:01:07Z","updated_at":"2016-12-20T22:01:07Z","body":"Hi there,\r\n\r\nJust some general informational questions:\r\nwhat version of VMware tools do you have installed?\r\n(/usr/bin/vmware-toolbox-cmd -v)\r\n\r\nCan you report the output  of the following:\r\n/usr/bin/vmhgfs-fuse --version\r\n\r\nWhat is the kernel version of the Ubuntu 16.04 install?\r\n\r\nI will take a look into this and see I can find out what is going on.\r\n\r\nAlso have you tried any other FUSE file systems and if so can you produce the same issue with any of those?\r\n\r\nThanks\r\nSteve\r\n\r\n"}}
{"actor":{"display_login":"lousybrit"}}