some times Vagrant is failed to synching share folders to guest VM

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

some times Vagrant is failed to synching share folders to guest VM

ashok vaddevalli

Vagrant version

2.0.1

Host operating system

Windows 7

Guest operating system

Windows 7

Vagrantfile

-- mode: ruby --

vi: set ft=ruby :

#Author: Ashok Vaddevalli

Vagrant.configure("2") do |config|

config.vm.box = 'dummy'
config.vm.box_url = 'dummy.box'

#config.vm.network "private_network", ip: ENV["ip"]

config.vm.communicator = "winrm"
config.winrm.username = "admin"
config.winrm.password = "admin@123"
config.winrm.timeout = 1800
config.vm.boot_timeout = 600

config.vm.synced_folder "./src", "/src", type: "smb", smb_username: "administrator", smb_password: "admin@123"

config.vm.synced_folder "./Result", "/Result", type: "smb", smb_username: "administrator", smb_password: "admin@123"

config.vm.synced_folder ".", "/vagrant", disabled: true

config.vm.provider :vsphere do |vsphere|
vsphere.host = 'X.X.X.X'
#vsphere.customization_spec_name = 'Win7-Custom_template'
vsphere.compute_resource_name = 'X.X.X.X'
vsphere.data_center_name = 'Demo'
vsphere.template_name = 'Templates/InstallerAutomation'
vsphere.name = 'InstallerAuto'
vsphere.user = '[hidden email]'
vsphere.password = ENV["vsphere.password"]
vsphere.insecure = true
end

config.vm.provision "shell", inline: "C:/src/setupandrunautomation.bat"

end

Expected behavior

==> default: Waiting for machine to boot. This may take a few minutes...
default: WinRM address: X.X.X.X:5985
default: WinRM username: admin
default: WinRM execution_time_limit: PT2H
default: WinRM transport: negotiate
==> default: Machine booted and ready!
==> default: Preparing SMB shared folders...
==> default: Mounting SMB shared folders...
default: C:/InstallerAutomation/src => /src
default: C:/InstallerAutomation/Result => /Result
==> default: Running provisioner: shell...
default: Running: inline PowerShell script
default: 1 file(s) moved.

Actual behavior

==> default: Mounting SMB shared folders...
default: C:/InstallerAutomation/src => /src
The following WinRM command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

cmdkey /add:X.X.X.X /user:administrator /pass:admin@123

Stdout from the command:

Stderr from the command:

Steps to reproduce

  1. Re run Vagrant up second time, it was synchronizing share folders, sometimes u can re run vagrant up multiple times for share folders synchronization.

I am facing share folders synchronization recent only, last ten builds i have not seen this issue.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/98d802cd-6924-477b-a890-53548804314e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: some times Vagrant is failed to synching share folders to guest VM

Alvaro Miranda Aguilera
hello

the box does and the host have all the needed to use smb?

how to reproduce? your vagrantfile says dummy for box

Alvaro

On Thu, Dec 14, 2017 at 7:25 AM, ashok vaddevalli <[hidden email]> wrote:

Vagrant version

2.0.1

Host operating system

Windows 7

Guest operating system

Windows 7

Vagrantfile

-- mode: ruby --

vi: set ft=ruby :

#Author: Ashok Vaddevalli

Vagrant.configure("2") do |config|

config.vm.box = 'dummy'
config.vm.box_url = 'dummy.box'

#config.vm.network "private_network", ip: ENV["ip"]

config.vm.communicator = "winrm"
config.winrm.username = "admin"
config.winrm.password = "admin@123"
config.winrm.timeout = 1800
config.vm.boot_timeout = 600

config.vm.synced_folder "./src", "/src", type: "smb", smb_username: "administrator", smb_password: "admin@123"

config.vm.synced_folder "./Result", "/Result", type: "smb", smb_username: "administrator", smb_password: "admin@123"

config.vm.synced_folder ".", "/vagrant", disabled: true

config.vm.provider :vsphere do |vsphere|
vsphere.host = 'X.X.X.X'
#vsphere.customization_spec_name = 'Win7-Custom_template'
vsphere.compute_resource_name = 'X.X.X.X'
vsphere.data_center_name = 'Demo'
vsphere.template_name = 'Templates/InstallerAutomation'
vsphere.name = 'InstallerAuto'
vsphere.user = '[hidden email]'
vsphere.password = ENV["vsphere.password"]
vsphere.insecure = true
end

config.vm.provision "shell", inline: "C:/src/setupandrunautomation.bat"

end

Expected behavior

==> default: Waiting for machine to boot. This may take a few minutes...
default: WinRM address: X.X.X.X:5985
default: WinRM username: admin
default: WinRM execution_time_limit: PT2H
default: WinRM transport: negotiate
==> default: Machine booted and ready!
==> default: Preparing SMB shared folders...
==> default: Mounting SMB shared folders...
default: C:/InstallerAutomation/src => /src
default: C:/InstallerAutomation/Result => /Result
==> default: Running provisioner: shell...
default: Running: inline PowerShell script
default: 1 file(s) moved.

Actual behavior

==> default: Mounting SMB shared folders...
default: C:/InstallerAutomation/src => /src
The following WinRM command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

cmdkey /add:X.X.X.X /user:administrator /pass:admin@123

Stdout from the command:

Stderr from the command:

Steps to reproduce

  1. Re run Vagrant up second time, it was synchronizing share folders, sometimes u can re run vagrant up multiple times for share folders synchronization.

I am facing share folders synchronization recent only, last ten builds i have not seen this issue.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/98d802cd-6924-477b-a890-53548804314e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0extDa70t0PFa2TMC2P2-A2YsRCYCANE%3DCW8-3JzbZXxVg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: some times Vagrant is failed to synching share folders to guest VM

ashok vaddevalli
In reply to this post by ashok vaddevalli

Downgrade 2.0 version, share folder synchronizing working fine, but getting the issue on destroy VM.

destroy VM
SSL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A



On Thursday, 14 December 2017 11:55:47 UTC+5:30, ashok vaddevalli wrote:

Vagrant version

2.0.1

Host operating system

Windows 7

Guest operating system

Windows 7

Vagrantfile

-- mode: ruby --

vi: set ft=ruby :

#Author: Ashok Vaddevalli

Vagrant.configure("2") do |config|

config.vm.box = 'dummy'
config.vm.box_url = 'dummy.box'

#config.vm.network "private_network", ip: ENV["ip"]

config.vm.communicator = "winrm"
config.winrm.username = "admin"
config.winrm.password = "admin@123"
config.winrm.timeout = 1800
config.vm.boot_timeout = 600

config.vm.synced_folder "./src", "/src", type: "smb", smb_username: "administrator", smb_password: "admin@123"

config.vm.synced_folder "./Result", "/Result", type: "smb", smb_username: "administrator", smb_password: "admin@123"

config.vm.synced_folder ".", "/vagrant", disabled: true

config.vm.provider :vsphere do |vsphere|
vsphere.host = 'X.X.X.X'
#vsphere.customization_spec_name = 'Win7-Custom_template'
vsphere.compute_resource_name = 'X.X.X.X'
vsphere.data_center_name = 'Demo'
vsphere.template_name = 'Templates/InstallerAutomation'
<a href="http://vsphere.name" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fvsphere.name\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGQW7qe92fmq9uws0WAvk2PCcsICA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fvsphere.name\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGQW7qe92fmq9uws0WAvk2PCcsICA&#39;;return true;">vsphere.name = 'InstallerAuto'
vsphere.user = '[hidden email]'
vsphere.password = ENV["vsphere.password"]
vsphere.insecure = true
end

config.vm.provision "shell", inline: "C:/src/setupandrunautomation.bat"

end

Expected behavior

==> default: Waiting for machine to boot. This may take a few minutes...
default: WinRM address: X.X.X.X:5985
default: WinRM username: admin
default: WinRM execution_time_limit: PT2H
default: WinRM transport: negotiate
==> default: Machine booted and ready!
==> default: Preparing SMB shared folders...
==> default: Mounting SMB shared folders...
default: C:/InstallerAutomation/src => /src
default: C:/InstallerAutomation/Result => /Result
==> default: Running provisioner: shell...
default: Running: inline PowerShell script
default: 1 file(s) moved.

Actual behavior

==> default: Mounting SMB shared folders...
default: C:/InstallerAutomation/src => /src
The following WinRM command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

cmdkey /add:X.X.X.X /user:administrator /pass:admin@123

Stdout from the command:

Stderr from the command:

Steps to reproduce

  1. Re run Vagrant up second time, it was synchronizing share folders, sometimes u can re run vagrant up multiple times for share folders synchronization.

I am facing share folders synchronization recent only, last ten builds i have not seen this issue.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/7a852c4c-41f4-460f-b08d-a5b4a89460da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: some times Vagrant is failed to synching share folders to guest VM

ashok vaddevalli
In reply to this post by Alvaro Miranda Aguilera
I am using Vagrant with Vsphere provider.
 
By default it is required dummy box, I am using template to create guest VM. The issue is not creating VM, synchronizing share folders.
 
On Thursday, 14 December 2017 16:44:54 UTC+5:30, Alvaro Miranda Aguilera wrote:
hello

the box does and the host have all the needed to use smb?

how to reproduce? your vagrantfile says dummy for box

Alvaro

On Thu, Dec 14, 2017 at 7:25 AM, ashok vaddevalli <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="rh2fh5OIAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">ashokva...@...> wrote:

Vagrant version

2.0.1

Host operating system

Windows 7

Guest operating system

Windows 7

Vagrantfile

-- mode: ruby --

vi: set ft=ruby :

#Author: Ashok Vaddevalli

Vagrant.configure("2") do |config|

config.vm.box = 'dummy'
config.vm.box_url = 'dummy.box'

#config.vm.network "private_network", ip: ENV["ip"]

config.vm.communicator = "winrm"
config.winrm.username = "admin"
config.winrm.password = "admin@123"
config.winrm.timeout = 1800
config.vm.boot_timeout = 600

config.vm.synced_folder "./src", "/src", type: "smb", smb_username: "administrator", smb_password: "admin@123"

config.vm.synced_folder "./Result", "/Result", type: "smb", smb_username: "administrator", smb_password: "admin@123"

config.vm.synced_folder ".", "/vagrant", disabled: true

config.vm.provider :vsphere do |vsphere|
vsphere.host = 'X.X.X.X'
#vsphere.customization_spec_name = 'Win7-Custom_template'
vsphere.compute_resource_name = 'X.X.X.X'
vsphere.data_center_name = 'Demo'
vsphere.template_name = 'Templates/InstallerAutomation'
<a href="http://vsphere.name" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fvsphere.name\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGQW7qe92fmq9uws0WAvk2PCcsICA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fvsphere.name\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGQW7qe92fmq9uws0WAvk2PCcsICA&#39;;return true;">vsphere.name = 'InstallerAuto'
vsphere.user = '<a href="javascript:" target="_blank" gdf-obfuscated-mailto="rh2fh5OIAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">admini...@...'
vsphere.password = ENV["vsphere.password"]
vsphere.insecure = true
end

config.vm.provision "shell", inline: "C:/src/setupandrunautomation.bat"

end

Expected behavior

==> default: Waiting for machine to boot. This may take a few minutes...
default: WinRM address: X.X.X.X:5985
default: WinRM username: admin
default: WinRM execution_time_limit: PT2H
default: WinRM transport: negotiate
==> default: Machine booted and ready!
==> default: Preparing SMB shared folders...
==> default: Mounting SMB shared folders...
default: C:/InstallerAutomation/src => /src
default: C:/InstallerAutomation/Result => /Result
==> default: Running provisioner: shell...
default: Running: inline PowerShell script
default: 1 file(s) moved.

Actual behavior

==> default: Mounting SMB shared folders...
default: C:/InstallerAutomation/src => /src
The following WinRM command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

cmdkey /add:X.X.X.X /user:administrator /pass:admin@123

Stdout from the command:

Stderr from the command:

Steps to reproduce

  1. Re run Vagrant up second time, it was synchronizing share folders, sometimes u can re run vagrant up multiple times for share folders synchronization.

I am facing share folders synchronization recent only, last ten builds i have not seen this issue.

--
This mailing list is governed under the HashiCorp Community Guidelines - <a href="https://www.hashicorp.com/community-guidelines.html" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.hashicorp.com%2Fcommunity-guidelines.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGHa_CaKfZaJiwbkUndUQbVGlQCDw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.hashicorp.com%2Fcommunity-guidelines.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGHa_CaKfZaJiwbkUndUQbVGlQCDw&#39;;return true;">https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: <a href="https://github.com/mitchellh/vagrant/issues" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fmitchellh%2Fvagrant%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHxcA5DuHlQlPInMi_k1Pz4pMNqNw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fmitchellh%2Fvagrant%2Fissues\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHxcA5DuHlQlPInMi_k1Pz4pMNqNw&#39;;return true;">https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="rh2fh5OIAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">vagrant-up+...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/vagrant-up/98d802cd-6924-477b-a890-53548804314e%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/vagrant-up/98d802cd-6924-477b-a890-53548804314e%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/vagrant-up/98d802cd-6924-477b-a890-53548804314e%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/vagrant-up/98d802cd-6924-477b-a890-53548804314e%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.



--
Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/e98884af-f9fb-44b9-ac3d-558ba44a34dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: some times Vagrant is failed to synching share folders to guest VM

Alvaro Miranda Aguilera
Hello

vsphere plugin is not native to vagrant

can you open an issue on the plugin repo?

Alvaro.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ewj-_5J_2WE3KCrLgMXfNn1NP8hErudpEoWX4tWzeAFAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: some times Vagrant is failed to synching share folders to guest VM

ashok vaddevalli
Hi Alvaro,

Yes, vsphere plugin is not native to vagrant. But the issue is not plugin, I think vagrant issue.

Please check below URL

https://stackoverflow.com/questions/31990885/vagrant-unable-to-mount-smb-after-upgrade-to-1-7-4

Regards,
Ashok

On Friday, 15 December 2017 00:38:13 UTC+5:30, Alvaro Miranda Aguilera wrote:
Hello

vsphere plugin is not native to vagrant

can you open an issue on the plugin repo?

Alvaro.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/2c47ab0f-0118-4a9c-9ce8-6798f1eab8dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: some times Vagrant is failed to synching share folders to guest VM

ashok vaddevalli
Sorry. looks  like the below URL is the credentials issue
https://stackoverflow.com/questions/31990885/vagrant-unable-to-mount-smb-after-upgrade-to-1-7-4

I have attached my vagrant vsphere debug log, can you please check once and let me know what is the issue on vagrant is not synching share folders.

Thanks in advance.

Regards,
Ashok

On Friday, 15 December 2017 08:03:49 UTC+5:30, ashok vaddevalli wrote:
Hi Alvaro,

Yes, vsphere plugin is not native to vagrant. But the issue is not plugin, I think vagrant issue.

Please check below URL

<a href="https://stackoverflow.com/questions/31990885/vagrant-unable-to-mount-smb-after-upgrade-to-1-7-4" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F31990885%2Fvagrant-unable-to-mount-smb-after-upgrade-to-1-7-4\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE1-0J4jP-uXEpJPZ-mvKhQPj0aog&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F31990885%2Fvagrant-unable-to-mount-smb-after-upgrade-to-1-7-4\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE1-0J4jP-uXEpJPZ-mvKhQPj0aog&#39;;return true;">https://stackoverflow.com/questions/31990885/vagrant-unable-to-mount-smb-after-upgrade-to-1-7-4

Regards,
Ashok

On Friday, 15 December 2017 00:38:13 UTC+5:30, Alvaro Miranda Aguilera wrote:
Hello

vsphere plugin is not native to vagrant

can you open an issue on the plugin repo?

Alvaro.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/c4de68de-c2b2-43e0-84fa-bc29969184c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Vagrant_Vsphere_Debuglog (623K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: some times Vagrant is failed to synching share folders to guest VM

ashok vaddevalli

I have not seen this issue after done few settings in both host machine and guest machine templates.

The below settings I have done,

  1. net config server /autodisconnect:-1
  2. Increased SMB timeout time.


On Friday, 15 December 2017 22:07:28 UTC+5:30, ashok vaddevalli wrote:
Sorry. looks  like the below URL is the credentials issue
<a href="https://stackoverflow.com/questions/31990885/vagrant-unable-to-mount-smb-after-upgrade-to-1-7-4" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F31990885%2Fvagrant-unable-to-mount-smb-after-upgrade-to-1-7-4\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE1-0J4jP-uXEpJPZ-mvKhQPj0aog&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F31990885%2Fvagrant-unable-to-mount-smb-after-upgrade-to-1-7-4\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE1-0J4jP-uXEpJPZ-mvKhQPj0aog&#39;;return true;">https://stackoverflow.com/questions/31990885/vagrant-unable-to-mount-smb-after-upgrade-to-1-7-4

I have attached my vagrant vsphere debug log, can you please check once and let me know what is the issue on vagrant is not synching share folders.

Thanks in advance.

Regards,
Ashok

On Friday, 15 December 2017 08:03:49 UTC+5:30, ashok vaddevalli wrote:
Hi Alvaro,

Yes, vsphere plugin is not native to vagrant. But the issue is not plugin, I think vagrant issue.

Please check below URL

<a href="https://stackoverflow.com/questions/31990885/vagrant-unable-to-mount-smb-after-upgrade-to-1-7-4" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F31990885%2Fvagrant-unable-to-mount-smb-after-upgrade-to-1-7-4\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE1-0J4jP-uXEpJPZ-mvKhQPj0aog&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F31990885%2Fvagrant-unable-to-mount-smb-after-upgrade-to-1-7-4\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE1-0J4jP-uXEpJPZ-mvKhQPj0aog&#39;;return true;">https://stackoverflow.com/questions/31990885/vagrant-unable-to-mount-smb-after-upgrade-to-1-7-4

Regards,
Ashok

On Friday, 15 December 2017 00:38:13 UTC+5:30, Alvaro Miranda Aguilera wrote:
Hello

vsphere plugin is not native to vagrant

can you open an issue on the plugin repo?

Alvaro.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/57f0247b-0296-473e-bae8-5ef7cb5c0279%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.