-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
CentOs 7 on vmware has non existent VMWareTools #747
Comments
I think you should complain to VMware 😉 |
I think the centos 7 template should be consistent with others and not require specific files in specific directories. Go ahead and try and build it yourself, see how far you get. |
It's inconsistent because it's literally the only way to get it to build currently on 7.3 - please review the PR and commit for why this is - once vmware fixes it, I'll update but currently this is a problem on the VMware side. We're at the mercy of vmware so either nobody gets a bento/centos-7.3 or we sideload the drivers. A quick googling will reveal both the release notes and download link (does require a login) https://my.vmware.com/group/vmware/details?downloadGroup=VMTOOLS1010&productId=491 |
You can just download from vmware and replace For VMware Fusion, that's at The install script at that point would look like # Install FUSE Drivers (Filesystem in Userspace)
yum install -y fuse fuse-libs
# Install from Source
echo
echo 'Extracting VMware Tools, please wait...'
mkdir /tmp/vmwaretools
mkdir /tmp/vmwaretools-archive
mount -o loop /home/vagrant/linux.iso /tmp/vmwaretools
tar xzf /tmp/vmwaretools/VMwareTools-*.tar.gz -C /tmp/vmwaretools-archive
echo 'Installing VMware Tools, please wait...'
/tmp/vmwaretools-archive/vmware-tools-distrib/vmware-install.pl --default --force-install
systemctl restart vmware-tools.service
# Cleanup
umount /tmp/vmwaretools
rm -rf /tmp/vmwaretools
rm -rf /tmp/vmwaretools-archive
rm /home/vagrant/*.iso |
The reason I didn't do that is that asking folks to modify their application files out of band felt slightly worse than having them sideloaded via Packer. The common vmware.sh script should work for this so when vmware updates things we'll go back to using it. |
@cheeseplus Oh for sure, the real fix here is probably to get CentOS to update the open-vm-tools package updated to 10.1.0. I'll try and figure out how to request that. This line fixed it. https://github.com/vmware/open-vm-tools/blob/e0a7b4e98bd6d6af06d31212dfdc82610d37e4d3/open-vm-tools/modules/linux/vmhgfs/page.c#L1648 |
@bdwyertech I think CentOS will only receive an updated open-vm-tools when Red Hat releases one. It looks like 10.1.0 is in the works, at least for CentOS 6 - I've added a request for RHEL/CentOS 7 to their Bugzilla as well now. I'll be interested to try it out when available, as I had thought that the FUSE version of vmhgfs was not going to be supported with the older RHEL/CentOS kernels. The open-vm-tools release notes previously referred to a 4.0.0 kernel requirement, but that reference was removed when the docs were updated for 10.1, so maybe the requirement has changed. The VMware docs still refer to the need to install vmhgfs from the proprietary tools package though. |
@bdwyertech: Wait, I'm confused. I'm able to build a working CentOS 7.3.1611 Vagrant box with Packer and the Is there a hard dependency on the newer release that I'm missing? I had read (I can't remember where at the moment) that with CentOS 7, the classic VMware Tools package is deprecated in favor of OpenVM Tools.
Am I missing context? Update: Ah, the HGFS problem. I generally get around it by using NFS and explicitly disabling HGFS in my But I can see why you'd want to fix that. |
Yep, HGFS despite all the "everything works with open-vm-tools" statement we still need proprietary. I'm also going to side for more compatible vs more "free as in beer" because of how these are consumed by users and the expectations therein. |
This is caused by the following lines
https://github.com/chef/bento/blob/master/centos-7.3-x86_64.json#L138-L142
This was introduced here:
292a39f
The work around is to pre-download VMwareTools-10.1.0-4449150.tar.gz to your drive before running packer build. That is inconsistent with all other bento images, and is confusing if you aren't familiar with packer.
Furthermore you must have a vmware account to download specific versions of vmware tools. Even if you have an account, vmware does not make it easy to download previous versions. The current download revision is
VMware-Tools-10.0.0-3000743.tar.gz
and there is no link I can find to downloadVMwareTools-10.1.0-4449150.tar.gz
The text was updated successfully, but these errors were encountered: