-
Notifications
You must be signed in to change notification settings - Fork 421
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vmware-hostd crashes on unrecognized Linux distribution #31
Comments
Thanks for the report. I have reported an internal bug to track it. Could you please help with details of the Linux distro that we can use to reproduce this issue ourselves? This will also be helpful to test/verify any fixes we make for this. |
I'm seeing this on a 64-bit Arch install. Arch doesn't explicitly make releases, so I can't direct you to a specific version to try, but an up-to-date install should allow you to reproduce the issue. If there are any other details you need to know, please specify and I'll be happy to provide them. |
Hey, I just ran into this using a NetBSD 6.1 VM with openvmtools installed. |
I can confirm I see the same issue in ESXi (build 2809209): |
Centos 6 & 7. OracleLinux 6 & 7. ESX 6.0 (5572656) |
I figured out that somehow the vmx file on vmware was being configured to use a guestOS only compatible with 6.5 when running ESXi hosts 4,5 or 6 (not 6.5). i reconfigured the vmx to fix this issue, open vm tools had no further issues reporting. the vmx can be reloaded without vm shutdown |
I was able to resolve this on Arch Linux (Antergos) by doing the following. I did not have my server name and IP nor the localhost defined in /etc/hosts. 127.0.0.1 localhost localhost.local |
@a13xchan what was the setting in the VMX file that you changed? |
@splitbrained for me and cent os it was the guestOS field in the vmx. I corrected it also on a few other linux distro who was configured as guestOS = ... to something not supported by that version of vSphere. There is a difference to what you configure in the vmx file to what the tools detects as the running OS. This will obviously if you run tools/scripts to make sure that the guestos matches the actual guest os detected by tools flag up inconsistencies but it will not spam the log files/ syslog with "Unable to convert Vigor ...". |
While this is probably a Workstation bug, it's possible to work around it by patching vmtoolsd, so I thought I'd make a report here so that it can be forwarded to the right place. (BTW, you might want to indicate in the readme on the master branch that this repo isn't dead, because it looks like the code hasn't been touched for two years unless you click around and notice that there's been activity in the branches.)
I reported this on the VMware forum:
The patch in that thread is a hack to prevent vmtoolsd from providing the information that ultimately makes vmware-hostd crash. In case someone sees this thread hoping for a quick fix, here's an updated one for 9.10.2 (cd to
open-vm-tools-stable-9.10.2/open-vm-tools
and apply withpatch -p2
):The text was updated successfully, but these errors were encountered: