{"update": {"autokarma": true, "autotime": false, "stable_karma": 1, "stable_days": 0, "unstable_karma": -1, "require_bugs": true, "require_testcases": true, "display_name": "", "notes": "Use systemd-detect-virt to detect VMware platform (RHBZ#1251656).", "type": "bugfix", "status": "stable", "request": null, "severity": "unspecified", "suggest": "unspecified", "locked": false, "pushed": true, "critpath": false, "critpath_groups": null, "close_bugs": false, "date_submitted": "2016-06-20 20:13:06", "date_modified": null, "date_approved": null, "date_testing": "2016-06-22 01:31:51", "date_stable": "2016-06-22 23:06:44", "alias": "FEDORA-2016-3037b0acb9", "test_gating_status": null, "from_tag": null, "date_pushed": "2016-06-22 23:06:44", "meets_testing_requirements": false, "url": "https://bodhi.fedoraproject.org/updates/FEDORA-2016-3037b0acb9", "title": "open-vm-tools-10.0.5-3.fc23", "version_hash": "aee8a78263eafd61fd36f5c18ebdf97a1e1da0f7", "release": {"name": "F23", "long_name": "Fedora 23", "version": "23", "id_prefix": "FEDORA", "branch": "f23", "dist_tag": "f23", "stable_tag": "f23-updates", "testing_tag": "f23-updates-testing", "candidate_tag": "f23-updates-candidate", "pending_signing_tag": "f23-signing-pending", "pending_testing_tag": "f23-updates-testing-pending", "pending_stable_tag": "f23-updates-pending", "override_tag": "f23-override", "mail_template": "fedora_errata_template", "state": "archived", "composed_by_bodhi": true, "create_automatic_updates": null, "package_manager": "dnf", "testing_repository": "updates-testing", "released_on": null, "eol": null, "critpath_mandatory_days_in_testing": 14, "mandatory_days_in_testing": 7, "critpath_min_karma": 2, "min_karma": 1, "setting_status": null}, "user": {"name": "ravindrakumar", "email": "ravindrakumar@vmware.com", "id": 454, "avatar": "https://seccdn.libravatar.org/avatar/55a3e70bb7644666f9a8b0c9abea91b6195a4b4ab0ab8d84fc8af8ab23f1efa7?s=24&d=retro", "openid": "ravindrakumar.id.fedoraproject.org", "groups": [{"name": "packager"}]}, "comments": [{"karma": 0, "karma_critpath": 0, "text": "This update has been submitted for testing by ravindrakumar. ", "timestamp": "2016-06-20 20:13:06", "update_id": 60899, "user_id": 91, "id": 448933, "bug_feedback": [], "testcase_feedback": [], "user": {"name": "bodhi", "email": null, "id": 91, "avatar": "https://apps.fedoraproject.org/img/icons/bodhi-24.png", "openid": "bodhi.id.fedoraproject.org", "groups": []}}, {"karma": 1, "karma_critpath": 0, "text": "I have tried the update open-vm-tools-10.0.5-3.fc23  (64bit) in a FC23 KDE live Vbox session.\n\nsteps:\nverify that vmtoolsd hooks cpu on boot=> login => yes\n\nkilled and removed open-vm-tools-10.0.0-7\n\ninstalled open-vm-tools-10.0.5-3 => no CPU hooked\n\nenabled and started vmtoolsd via systemctl => no CPU hooked\n\nsystemctl status vmtoolsd says =>start condition faild...= vmware was not met\n\nSo far a succes\n\nJust remember that the bug behavior are related to AMD CPU....it happends on no Intel HW I have", "timestamp": "2016-06-21 15:25:39", "update_id": 60899, "user_id": 2105, "id": 449279, "bug_feedback": [{"karma": 1, "comment_id": 449279, "bug_id": 1251656, "bug": {"bug_id": 1251656, "title": "vmtoolsd load 1 core of cpu 100% in Virtualbox environment", "security": false, "parent": false}}], "testcase_feedback": [], "user": {"name": "knudch", "email": "knud.skrald@guldberg.info", "id": 2105, "avatar": "https://seccdn.libravatar.org/avatar/1923b00c4c4426a40bb9e180e94ed101ec4e7d6999f03151fb65c87c161f657c?s=24&d=retro", "openid": "knudch.id.fedoraproject.org", "groups": []}}, {"karma": 0, "karma_critpath": 0, "text": "Thanks for verifying this. There are two aspects of this fix 'vmware-checkvm' called by RPM and 'vmtoolsd' started after login. This fix applies to only RPM, there is no change in vmtoolsd. 'vmtoolsd' issue needs to be fixed in upstream first. So, expectation is that RPM should not get stuck in vmware-checkvm, but vmtoolsd may still take 100% CPU. There are two instances of vmtoolsd usually, one running as system (what you have tried) and one running as logged in user. To get vmtoolsd started as logged in user, you need to \"reboot and login\" or \"logout and login\" after \"installed open-vm-tools-10.0.5-3 => no CPU hooked\". Could you please try that? We will consider this update is good as long as RPM issue is solved.", "timestamp": "2016-06-21 21:17:21", "update_id": 60899, "user_id": 454, "id": 449388, "bug_feedback": [{"karma": 0, "comment_id": 449388, "bug_id": 1251656, "bug": {"bug_id": 1251656, "title": "vmtoolsd load 1 core of cpu 100% in Virtualbox environment", "security": false, "parent": false}}], "testcase_feedback": [], "user": {"name": "ravindrakumar", "email": "ravindrakumar@vmware.com", "id": 454, "avatar": "https://seccdn.libravatar.org/avatar/55a3e70bb7644666f9a8b0c9abea91b6195a4b4ab0ab8d84fc8af8ab23f1efa7?s=24&d=retro", "openid": "ravindrakumar.id.fedoraproject.org", "groups": [{"name": "packager"}]}}, {"karma": 0, "karma_critpath": 0, "text": "This update has been pushed to testing.", "timestamp": "2016-06-22 02:55:41", "update_id": 60899, "user_id": 91, "id": 449579, "bug_feedback": [], "testcase_feedback": [], "user": {"name": "bodhi", "email": null, "id": 91, "avatar": "https://apps.fedoraproject.org/img/icons/bodhi-24.png", "openid": "bodhi.id.fedoraproject.org", "groups": []}}, {"karma": 0, "karma_critpath": 0, "text": "This update has been submitted for stable by bodhi. ", "timestamp": "2016-06-22 02:55:47", "update_id": 60899, "user_id": 91, "id": 449589, "bug_feedback": [], "testcase_feedback": [], "user": {"name": "bodhi", "email": null, "id": 91, "avatar": "https://apps.fedoraproject.org/img/icons/bodhi-24.png", "openid": "bodhi.id.fedoraproject.org", "groups": []}}, {"karma": 0, "karma_critpath": 0, "text": "This update has been pushed to stable.", "timestamp": "2016-06-23 04:54:12", "update_id": 60899, "user_id": 91, "id": 450011, "bug_feedback": [], "testcase_feedback": [], "user": {"name": "bodhi", "email": null, "id": 91, "avatar": "https://apps.fedoraproject.org/img/icons/bodhi-24.png", "openid": "bodhi.id.fedoraproject.org", "groups": []}}], "builds": [{"nvr": "open-vm-tools-10.0.5-3.fc23", "signed": true, "release_id": 11, "type": "rpm", "epoch": 0}], "bugs": [{"bug_id": 1251656, "title": "vmtoolsd load 1 core of cpu 100% in Virtualbox environment", "security": false, "parent": false, "feedback": [{"karma": 1, "comment_id": 449279, "bug_id": 1251656, "comment": {"karma": 1, "karma_critpath": 0, "text": "I have tried the update open-vm-tools-10.0.5-3.fc23  (64bit) in a FC23 KDE live Vbox session.\n\nsteps:\nverify that vmtoolsd hooks cpu on boot=> login => yes\n\nkilled and removed open-vm-tools-10.0.0-7\n\ninstalled open-vm-tools-10.0.5-3 => no CPU hooked\n\nenabled and started vmtoolsd via systemctl => no CPU hooked\n\nsystemctl status vmtoolsd says =>start condition faild...= vmware was not met\n\nSo far a succes\n\nJust remember that the bug behavior are related to AMD CPU....it happends on no Intel HW I have", "timestamp": "2016-06-21 15:25:39", "update_id": 60899, "user_id": 2105, "id": 449279, "testcase_feedback": [], "user": {"name": "knudch", "email": "knud.skrald@guldberg.info", "id": 2105, "avatar": "https://seccdn.libravatar.org/avatar/1923b00c4c4426a40bb9e180e94ed101ec4e7d6999f03151fb65c87c161f657c?s=24&d=retro", "openid": "knudch.id.fedoraproject.org", "groups": []}}}, {"karma": 0, "comment_id": 449388, "bug_id": 1251656, "comment": {"karma": 0, "karma_critpath": 0, "text": "Thanks for verifying this. There are two aspects of this fix 'vmware-checkvm' called by RPM and 'vmtoolsd' started after login. This fix applies to only RPM, there is no change in vmtoolsd. 'vmtoolsd' issue needs to be fixed in upstream first. So, expectation is that RPM should not get stuck in vmware-checkvm, but vmtoolsd may still take 100% CPU. There are two instances of vmtoolsd usually, one running as system (what you have tried) and one running as logged in user. To get vmtoolsd started as logged in user, you need to \"reboot and login\" or \"logout and login\" after \"installed open-vm-tools-10.0.5-3 => no CPU hooked\". Could you please try that? We will consider this update is good as long as RPM issue is solved.", "timestamp": "2016-06-21 21:17:21", "update_id": 60899, "user_id": 454, "id": 449388, "testcase_feedback": [], "user": {"name": "ravindrakumar", "email": "ravindrakumar@vmware.com", "id": 454, "avatar": "https://seccdn.libravatar.org/avatar/55a3e70bb7644666f9a8b0c9abea91b6195a4b4ab0ab8d84fc8af8ab23f1efa7?s=24&d=retro", "openid": "ravindrakumar.id.fedoraproject.org", "groups": [{"name": "packager"}]}}}]}], "updateid": "FEDORA-2016-3037b0acb9", "karma": 1, "content_type": "rpm", "test_cases": []}, "can_edit": false, "ci_allowed": false}