search

hashicorp / vagrant

Vagrant is a tool for building and distributing development environments.
https://www.vagrantup.com
Other
26.29k stars 4.43k forks source link

VMWare NFS Shares Hanging #2017

Closed dcramer closed 11 years ago

dcramer commented 11 years ago

Not sure what happened (tried reboot of OS X as well as halt/up several times), but now fusion is hanging trying to enable shared folders with NFS.

What can I do to actually get some debug information that might help with this?

With logging I only see:

[default] Enabling and configuring shared folders...
 INFO vmware_driver: Enabling shared folders...
 INFO subprocess: Starting process: ["/Applications/VMware Fusion.app/Contents/Library/vmrun", "enableSharedFolders", "/Users/cramer/Development/something/.vagrant/machines/default/vmware_fusion/1722f08e-4a1f-43fd-9a84-e47b9aa32b48/packer-vmware.vmx"]

Nothing fancy going on here, just have this in shared folders:

  config.vm.synced_folder "../vmsetup", "/home/vagrant/vmsetup", :nfs => true

Note: removing NFS doesn't change the behavior

This is on 0.8.3 of the plugin

dcramer commented 11 years ago

FYI I can also completely remove my shared folders, and the same issue happens (unless i disable the vagrant folder)

mitchellh commented 11 years ago

I've seen this before, sometimes that command takes really long (I'm not sure what VMware is doing). Have you tried just waiting a few minutes? It generally fixes itself.

Other times, it is waiting on something to happen in the kernel that will never happen. Did you update the kernel? Are your vmware tools properly installed/running? etc.

dcramer commented 11 years ago

Didn't make any changes to the VM's core packages/vmware tools.

I've let it go for a few minutes, but will try letting it sit for a while.

On Thursday, August 1, 2013 at 1:59 PM, Mitchell Hashimoto wrote:

I've seen this before, sometimes that command takes really long (I'm not sure what VMware is doing). Have you tried just waiting a few minutes? It generally fixes itself. Other times, it is waiting on something to happen in the kernel that will never happen. Did you update the kernel? Are your vmware tools properly installed/running? etc.

— Reply to this email directly or view it on GitHub (https://github.com/mitchellh/vagrant/issues/2017#issuecomment-21969172).

dcramer commented 11 years ago

Gave up and did a destroy && up and it's fine now, so definitely specific to the individual VM

On Thursday, August 1, 2013 at 2:01 PM, David Cramer wrote:

Didn't make any changes to the VM's core packages/vmware tools.

I've let it go for a few minutes, but will try letting it sit for a while.

On Thursday, August 1, 2013 at 1:59 PM, Mitchell Hashimoto wrote:

I've seen this before, sometimes that command takes really long (I'm not sure what VMware is doing). Have you tried just waiting a few minutes? It generally fixes itself. Other times, it is waiting on something to happen in the kernel that will never happen. Did you update the kernel? Are your vmware tools properly installed/running? etc.

— Reply to this email directly or view it on GitHub (https://github.com/mitchellh/vagrant/issues/2017#issuecomment-21969172).

mitchellh commented 11 years ago

Until we can repro, closing.