Use systemd-detect-virt to detect VMware platform (#1251656).
sudo dnf upgrade --advisory=FEDORA-2016-3037b0acb9
This update has been submitted for testing by ravindrakumar.
I have tried the update open-vm-tools-10.0.5-3.fc23 (64bit) in a FC23 KDE live Vbox session.
verify that vmtoolsd hooks cpu on boot=> login => yes
killed and removed open-vm-tools-10.0.0-7
installed open-vm-tools-10.0.5-3 => no CPU hooked
enabled and started vmtoolsd via systemctl => no CPU hooked
systemctl status vmtoolsd says =>start condition faild...= vmware was not met
So far a succes
Just remember that the bug behavior are related to AMD CPU....it happends on no Intel HW I have
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.
This update has been pushed to testing.
This update has been submitted for stable by bodhi.
This update has been pushed to stable.
Please login to add feedback.
Submitting this will the tests again.
Copyright © 2007-2019 Red Hat, Inc. and
bodhi is Free Software.
if you have any problems. Read the documentation.