Skip to content
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

Workstation 11.1.2 Tools incompatible with current builds #377

Closed
thasmo opened this issue Jun 29, 2015 · 17 comments
Closed

Workstation 11.1.2 Tools incompatible with current builds #377

thasmo opened this issue Jun 29, 2015 · 17 comments
Labels
Type: Bug Does not work as expected.

Comments

@thasmo
Copy link

thasmo commented Jun 29, 2015

I've upgraded Workstation to version 11.1.2 on Windows and encountered problems with the current builds on Atlas. Vagrant wasn't able to create synced folders. After I had re-installed the VMware Tools manually it worked again. Seems like the currently installed Tools version is not compatible with Workstation 11.1.2.

@thasmo
Copy link
Author

thasmo commented Jun 29, 2015

The new Ubuntu 15.04 64-bit box works well (except a vagrant bug). The problem occured when using the 14.10 64-bit box.

@fnichol
Copy link
Contributor

fnichol commented Jun 30, 2015

Interesting, I wonder if VMware Workstation and VMware Fusion install different versions (or implementations) of VMware Tools.

Does this only happen for the older Ubuntu releases (like 14.10 as you mentioned), but not for 15.04 (aside from the Vagrant bug)? Currently the Atalas boxes haven't been rebuilt since their initial publish and therefore may have older VMware Tools installed. Getting more frequent/fresh builds is something we're working towards, but still a bit down the road (i.e. not next week kinda thing).

Looks like I should get a license for Workstion in the meantime though.

@fnichol
Copy link
Contributor

fnichol commented Jun 30, 2015

Adding the VMware Workstation 11.1.2 release notes for future reference,

@thasmo
Copy link
Author

thasmo commented Jun 30, 2015

Yes, as mentioned it seems the VMware Tools which are installed on the 15.04 box are compatible with Workstation 11.1.2. Problems occur with the 14.10 box.

@rfc1459
Copy link

rfc1459 commented Jul 4, 2015

I just ran an Ubuntu 14.04 build on VMware Workstation and there's a serious issue with kernel package handling (which ultimately leads to this bug): essentially, the update script does not take the LTS HWE packages into account, defaulting instead to linux-server and linux-headers-server. This causes the -lts-utopic packages (which are the ones brought in by the 12.04.2 installer) to be kept back.

Furthermore, the cleanup script brings in the kernel packages which should have been installed by the update phase: coupled with the fact that at this point the tools are installed already and the autoupdate feature is disabled this leads to a running kernel without the relevant VMware modules built and installed.

I'm not entirely sure how to fix this without rewriting a large portion of the involved scripts, I'll try to give it a shot in the next few days.

@cheeseplus
Copy link
Contributor

We've rebuilt all the boxes @8a424e2900148bb8d732604844b4e18bce064d07 - is this still an issue? I don't have access to VMware workstation but of Fusion installs the updated tools this may have gone away.

@tisba
Copy link

tisba commented Sep 6, 2015

@cheeseplus I tried to use https://atlas.hashicorp.com/bento/boxes/ubuntu-14.04/versions/2.2.0 with VMware Fusion Version 8.0.0 (2985594) on OS X 10.10.5 but ran into the same problem: Vagrant hangs at ==> default: Waiting for HGFS kernel module to load....

@einkoro
Copy link

einkoro commented Sep 12, 2015

I'm seeing the same issue with VMware Fusion Version 8.0.0 on OS X 10.11 GM.

@thasmo
Copy link
Author

thasmo commented Sep 20, 2015

The latest version of the Ubuntu 15.04 box on Atlas, version 2.2.1 stopped working with VMware Workstation 11.1.2. Version 2.2.0 is working well with it, just tested it again. @fnichol, is this a known issue?

The HGFS kernel module was not found on the running virtual machine.
This must be installed for shared folders to work properly. Please
install the VMware tools within the guest and try again. Note that
the VMware tools installation will succeed even if HGFS fails
to properly install. Carefully read the output of the VMware tools
installation to verify the HGFS kernel modules were installed properly.

@cheeseplus
Copy link
Contributor

@thasmo so the 2.2.1 boxes were built with Fusion 8.0.0 but otherwise same templates (at least for Ubuntu). We haven't systematically tackled and tested all the permutations of tooling versions with operating systems yet - this seems to be further complicated by increasing Fusion and Workstation versions.

@thasmo
Copy link
Author

thasmo commented Sep 26, 2015

Ye, seems like every VMware update introduces the same problems over and over. Does #454 fix it?

@cheeseplus
Copy link
Contributor

@thasmo so from the testing I've done it does fix it for some value of fix - testing has only been done with Fusion 8 however as we do not currently have a VMware workstation license. That said the 2.2.2 boxes (not yet released) all seem to load the HGFS module fine and mounts the folders as intended. I'll be closing this issue once I release those boxes and any new issues that present we can troubleshoot against specific versions.

@thasmo
Copy link
Author

thasmo commented Sep 26, 2015

Sounds great!

@odilontalk
Copy link

Or just use: https://github.com/rasa/vmware-tools-patches

Works nice on VMWare Fusion 7.1.2 and Debian 8.2.

@davidmnoriega
Copy link
Contributor

I'm running VMware Fusion 7 and when I built the ubuntu-14.04 box, the --force-install option doesn't exist.

@cheeseplus
Copy link
Contributor

@davidmnoriega supporting past versions is going to be difficult from an infrastructure standpoint - mostly because of the forced upgrades to support particular OSX revisions. That said we'll probably look at using the aformentioned project https://github.com/rasa/vmware-tools-patches to try to make this a little less onerous - just that testing all the permutations will still be difficult.

@cheeseplus
Copy link
Contributor

Closing this as fixed efeb14a

That said I do not expect this to fix all the problems in this thread but these need to be opened as individual issues with the as many version specifics as possible i.e. packer, VMware Fusion/Workstation Version, host OS, bento artifact OS.

@cheeseplus cheeseplus removed the Triaged label Oct 7, 2015
@tas50 tas50 added Type: Bug Does not work as expected. and removed Bug labels Jan 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Does not work as expected.
Projects
None yet
Development

No branches or pull requests

10 participants