vmware fusion 10.0.0 support

[tcataldo]

Please note that the Vagrant issue tracker is reserved for bug reports and enhancements. For general usage questions, please use the Vagrant mailing list: https://groups.google.com/forum/#!forum/vagrant-up. Thank you!

Vagrant version

$ vagrant -v Vagrant 2.0.0 $ vagrant plugin list vagrant-hostmanager (1.8.7) vagrant-share (1.1.9, system) vagrant-vmware-fusion (4.0.24)

Host operating system

osx 10.13 high sierra

Guest operating system

ubuntu xenial, but it is not relevant

Expected behavior

The VM starts in vmware fusion 10.

Actual behavior

Bringing machine 'mapi' up with 'vmware_fusion' provider... This provider only works with VMware Fusion 8 or lower. You have Fusion '10.0.0'. Please install the proper version of VMware Fusion and try again.

Steps to reproduce

1. upgrade vmware fusion to 10
2. vagrant up

[mitchellh]

We're looking into it. We're seeing some orders come in successfully so we're not sure yet. We're running through the process now.

[mitchellh]

@terion-name Your email doesn't exist as a prior owner in our shopify history. The coupon code is restricted to prior owners for the upgrade. It doesn't affect new owners. Sorry if I didn't make that clear, but I did note in both my comments mentioning the coupon code that its for "upgrades"! When we ran through it with a new email we saw the same behavior as you.

If this isn't correct, please email our support and we'll work with you to look up your email or diagnose why it may not exist in our customer DB.

[sergeyklay]

I'm so sorry for annoying questions but...

anybody who purchased after August 8, 2017 has already been automatically upgraded for free. If you find your confirmation email and redownload then your license is ready to go with the new versions of VMware.

My invoice is from Oct 5, 2017 and I don't see any email. Is it ok?

[chrisroberts]

@sergeyklay Yes, your license was automatically upgraded. You can download the updated license from the link in your original order confirmation email.

[terion-name]

@mitchellh I own a licence for previous version and it was bought on mail@terion.name address at April 5 2017 UPD Ah, ok, I'll email support

[shawnho1018]

@mitchellh I followed your post to use only one coupon code. I do see my email was valid on upgrade page for a half price discount (79->39). However, when I use only the VMW10-SORRY coupon code, the website said "Customer information does not meet the requirements for the VMW10-SORRY discount code Remove discount". Why was that? I need my plugin to test something right away. It is killing me. ~_~

I submitted a support case.

[vdanen]

Same issue here. Add the second coupon to get it to the correct price and they both get removed.

[chrisroberts]

Hi everyone. The discount code has been updated and should resolve these "Customer information does not meet the requirements" messages being returned.

[back-2-95]

I got this question from our employees. Is Fusion 10 Pro needed for Vagrant or is normal version enough?

[mitchellh]

@terion-name See what @chrisroberts said above ^ and try again. We've been relaxing some of the constraints on the coupon and we hope it'll work for more now. Its been tricky to diagnose since it has been clearly working for some and not others and there are only so many knobs we have to turn with it, haha.

[terion-name]

@mitchellh @chrisroberts worked, thank you!

[shawnho1018]

Works for me too. Thanks!

[chrisroberts]

@back-2-95 Fusion Pro would be recommended. Fusion lacks some features like linked clones and advanced networking that the Vagrant provider utilizes. You would need to disable those things in your Vagrantfile to get things working as expected.

[ndobbs]

I'm having issues with HGFS, I can't seem to mount any ShareFolders, should I move this discussion to a new issue?

An error occurred while executing `vmrun`, a utility for controlling
VMware machines. The command and output are below:

Command: ["enableSharedFolders", "/Users/ndobbs/shspace/projects/infrastructure/dev-testing/.vagrant/machines/security_testing/vmware_fusion/ee48833a-2761-4b25-b376-2d9dfbc8d821/ubuntu-14.04-amd64.vmx", {:notify=>[:stdout, :stderr]}]

Stdout: Error: There was an error mounting the Shared Folders file system inside the guest operating system

Stderr:

[onedsc]

Hitting https://github.com/hashicorp/vagrant/issues/9047 - currently a show stopper for me

[chrisroberts]

@ndobbs Yes, please create a new issue.

and I'm going to close this as the original issue is now resolved. Cheers!

[ndobbs]

@onedsc I ran into this too, I deleted the .vagrant directory in my projects folder order to get it working again.

[onedsc]

@ndobbs I deleted the .vagrant dir in my project file and I get the same isssue: Bringing machine 'devtest0' up with 'vmware_fusion' provider... ==> devtest0: Cloning VMware VM: 'illumio/centos-7.3'. This can take some time... ==> devtest0: Verifying vmnet devices are healthy... ==> devtest0: Deleting the VM... /Users/dcook/.vagrant.d/gems/2.3.4/gems/vagrant-vmware-fusion-5.0.0/lib/vagrant-vmware-fusion/helper/nat_conf.rb:169:in `initialize': Permission denied @ rb_sysopen - /Users/dcook/.vagrant.d/data/vmware/vmware-nat.json.lock (Errno::EACCES)

[chrisroberts]

See here: https://github.com/hashicorp/vagrant/issues/9047#issuecomment-337672998

[onedsc]

@chrisroberts - Thanks that seems to have fixed it

[eatstoomuchjam]

Attempting to install the latest version of vagrant-vmware-fusion over ssh fails. Installing while logged in from the GUI works. It seems to have to do with how you're escalating privileges:

bash-3.2$ vagrant plugin install vagrant-vmware-fusion
Installing the 'vagrant-vmware-fusion' plugin. This can take a few minutes...
Building native extensions.  This could take a while...

Vagrant is installing the VMware plugin which requires
root access. You may be prompted for your password to
complete setup.

0:1252: execution error: The administrator user name or password was incorrect. (-60007)
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

ERROR: Failed to build gem native extension.

    current directory: /Users/danarchy/.vagrant.d/gems/2.3.4/gems/vagrant-vmware-fusion-5.0.0/ext/vagrant-vmware-desktop
/opt/vagrant/embedded/bin/ruby -r ./siteconf20171018-13889-egbfrw.rb extconf.rb
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Provided configuration options:
        --with-opt-dir
        --with-opt-include
        --without-opt-include=${opt-dir}/include
        --with-opt-lib
        --without-opt-lib=${opt-dir}/lib
        --with-make-prog
        --without-make-prog
        --srcdir=.
        --curdir
        --ruby=/opt/vagrant/embedded/bin/$(RUBY_BASE_NAME)

extconf failed, exit code 1

Gem files will remain installed in /Users/danarchy/.vagrant.d/gems/2.3.4/gems/vagrant-vmware-fusion-5.0.0 for inspection.
Results logged to /Users/danarchy/.vagrant.d/gems/2.3.4/extensions/x86_64-darwin-13/2.3.0/vagrant-vmware-fusion-5.0.0/gem_make.out

[mafrosis]

Thanks Hashicorp guys for continuing to support VMWare and how you've handled all the complaints in this thread! 🎉 ❤️

@back-2-95 I've been using Vagrant and Fusion since v4 - I've never used Pro or needed to have special commands in my Vagrantfile to support the normal version. I'd wager the majority of people out there are not running Pro. YMMV, of course.

[Fred78290]

Thanks Hashicorp, work fine now :) The coupon have been applied for me with 19USD value. (Need to verify the good charge with my bank :P)

In reponse of eatstoomuchjam , I got the same Issue

to solve it juste change the ownership of /Users/$USERNAME/.vagrant.d/data/vmware/, it's owned by root.

Cheers

[embusalacchi]

I was running into a strange issue after getting the new plugin and creating machines with packer. If you're having an issue installing a new VM w/vagrant, the new plugin, and OSX 10.13 please check out this link - https://communities.vmware.com/thread/573147. I wasted a ton of time on this so wanted to post here for everyone.

[Fred78290]

Got also this issue :P Solved by doing these 1 - Remove VirtualBox (incompatible with Fusion) 2 - Reboot and hit shit key at boot to force the cache kernel extension to be rebuild, (take a long) 3 - After don't logging, reboot again 4 - Log in account and execute these command sudo kextcache -system-prelinked-kernel sudo kextcache -system-caches

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.