search

hashicorp / vagrant

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

vagrant boot error #9008

Closed snfnwgi closed 6 years ago

snfnwgi commented 6 years ago

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 1.8.1

Host operating system

mac

Guest operating system

windows7

Vagrantfile

Vagrant.configure("2") do |config|
  # WIN7 - IE11
  config.vm.box = "win7"
 config.vm.network :private_network, ip: "192.168.33.129"
  config.vm.boot_timeout = 5000
  config.vm.guest = :windows
  config.vm.communicator = :winrm       if provisioned?
  config.winrm.username = "IEUser"      if provisioned?
  config.winrm.password = "Passw0rd!"   if provisioned?
  config.winrm.timeout = 50000          if provisioned?
  config.winrm.retry_delay = 30         if provisioned?
  config.winrm.retry_limit = 1000       if provisioned?
  config.ssh.username = "IEUser"
  config.ssh.password = "Passw0rd!"
  config.ssh.insert_key = false
  #config.vbguest.auto_update = false

  config.vm.box_check_update = false

 config.vm.synced_folder "/Users/jians/php/www/work", "C:/vagrant_data", type: "smb"

  config.vm.provider "virtualbox" do |vb|
     # Display the VirtualBox GUI when booting the machine
     vb.gui = true

     # Customize the amount of memory on the VM:
     vb.memory = "2048"
  end

  config.vm.provision "file", source: "./tools/7z.exe", destination: "c:/users/IEUser/7z.exe"
  config.vm.provision "file", source: "./tools/7z.dll", destination: "c:/users/IEUser/7z.dll"
  config.vm.provision "file", source: "./tools/tools.zip", destination: "c:/users/IEUser/tools.zip"
  config.vm.provision "winrm", type: "ie_box_automation"
end

Debug output

boot error! Sorry, my English is not good！ ==> default: Forwarding ports... default: 5985 (guest) => 55985 (host) (adapter 1) default: 5986 (guest) => 55986 (host) (adapter 1) ==> default: Running 'pre-boot' VM customizations... ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... default: WinRM address: 127.0.0.1:55985 default: WinRM username: IEUser default: WinRM execution_time_limit: PT2H default: WinRM transport: plaintext ==> default: Machine booted and ready! ==> default: Checking for guest additions in VM... ==> default: Configuring and enabling network interfaces... ==> default: Exporting NFS shared folders... ==> default: Preparing to edit /etc/exports. Administrator privileges will be required... ==> default: Mounting NFS shared folders... Vagrant attempted to execute the capability 'mount_nfs_folder' on the detect guest OS 'windows', but the guest doesn't support that capability. This capability is required for your configuration of Vagrant. Please either reconfigure Vagrant to avoid this capability or fix the issue by creating the capability.

Expected behavior

What should have happened?

briancain commented 6 years ago

Hello @snfnwgi - You are attempting to use NFS on windows, which is not supported.

Windows users: NFS folders do not work on Windows hosts. Vagrant will ignore your request for NFS synced folders on Windows.

I recommend using a different method for synced folders. Thanks!

snfnwgi commented 6 years ago

@briancain Thank you. Isn't it possible to run WINDOWS on MAC? The official website said, "WINDOWS" can not refer to "active" or "virtual machine"? This is the way I support it, SMB doesn't seem to be able to do so

narration-sd commented 6 years ago

@snfnwgi When you are in the Windows-on-Mac, you are using the Windows operating system, and its filesystem, as Brian @briancain mentions. These are not conducive to NFS.

The Mac is only providing hardware in this situation -- display, cpu, disk but not Mac filesystem: rather Windows on that partition. I don't name it as NTFS to avoid confusing you as sounding like NFS -- not related.

I see you are eager, but imagining is not going to fix this situation.

snfnwgi commented 6 years ago

Thank you. Which way should I synchronize?Thank you very much for your kind reply @narration-sd

narration-sd commented 6 years ago

Well, it depends on what you want to do with your Vagrant vm.

If you want to get reasonable performance 'transparently', the best way I know is to run your vm with the commercial VMware Workstation provider. If you are not commercial, this is available free, but to get the better performance you'll still need to purchase the VMware Vagrant Provider, which costs about USD 100.

What I actually do is use the free Virtualbox provider, but with rsync to initiallly copy only the software I'm developing up to the Vagrant box. This is extremely rapid. You can look up how to use rsync online. As I edit and change the code, I have my developing environment automatically SFTP the changes, which occurs 'instantly'. The original is always on the workstation, so I don't need to copy back.

Rsync is in trouble with 2.0.0, but should shortly be working again in a fresh release. It has worked for years with earlier versions, so a current 1.9.6 should be fine if you want to practice ahead on rsync, given my way of working would be appropriate for you.

Otherwise, I would just get the VMware software packagess, and expect those to work usefully well.

Good fortune, Yang ZhiJian, Clive

p.s. if a database is involved, you'd back that up or reload it using a remote database tool such as Navicat. No matter how you run Vagrant, you wouldn't want to copy it up and down directly, as this could make corruption in the data, as is well understood.

snfnwgi commented 6 years ago

@narration-sd I'm so moved. Thank you for your patience.I've just tried two synchronization methods: SMB and RSYNC.

1.、smb

Bringing machine 'default' up with 'virtualbox' provider... SMB shared folders are only available when Vagrant is running on Windows. The guest machine can be running non-Windows. Please use another synced folder type.

2.rsync

Bringing machine 'default' up with 'virtualbox' provider... ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat ==> default: Forwarding ports... default: 5985 (guest) => 55985 (host) (adapter 1) default: 5986 (guest) => 55986 (host) (adapter 1) default: 22 (guest) => 2222 (host) (adapter 1) ==> default: Running 'pre-boot' VM customizations... ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... default: WinRM address: 127.0.0.1:55985 default: WinRM username: IEUser default: WinRM execution_time_limit: PT2H default: WinRM transport: negotiate

==> default: Machine booted and ready! ==> default: Checking for guest additions in VM... ==> default: The machine you're rsyncing folders to is configured to use ==> default: password-based authentication. Vagrant can't script rsync to automatically ==> default: enter this password, so you'll likely be prompted for a password ==> default: shortly. ==> default: ==> default: If you don't want to have to do this, please enable automatic ==> default: key insertion using config.ssh.insert_key. ==> default: Rsyncing folder: /vagrant/win7/modernie-winrm/ExtraFolder/ => /cygdrive/c/ExtraFolder /opt/vagrant/embedded/gems/gems/winrm-1.8.1/lib/winrm/http/response_handler.rb:64:in raise_if_wsman_fault': [WSMAN ERROR CODE: 2150859173]: <f:WSManFault Code='2150859173' Machine='127.0.0.1' xmlns:f='http://schemas.microsoft.com/wbem/wsman/1/wsmanfault'><f:Message>The WS-Management service cannot process the request. This user is allowed a maximum number of 5 concurrent shells, which has been exceeded. Close existing shells or raise the quota for this user. </f:Message></f:WSManFault> (WinRM::WinRMWSManFault) from /opt/vagrant/embedded/gems/gems/winrm-1.8.1/lib/winrm/http/response_handler.rb:51:inraise_if_error' from /opt/vagrant/embedded/gems/gems/winrm-1.8.1/lib/winrm/http/response_handler.rb:35:in parse_to_xml' from /opt/vagrant/embedded/gems/gems/winrm-1.8.1/lib/winrm/http/transport.rb:200:insend_request' from /opt/vagrant/embedded/gems/gems/winrm-1.8.1/lib/winrm/winrm_service.rb:492:in send_message' from /opt/vagrant/embedded/gems/gems/winrm-1.8.1/lib/winrm/winrm_service.rb:153:inopen_shell' from /opt/vagrant/embedded/gems/gems/winrm-1.8.1/lib/winrm/command_executor.rb:72:in block in open' from /opt/vagrant/embedded/gems/gems/winrm-1.8.1/lib/winrm/command_executor.rb:222:inretryable' from /opt/vagrant/embedded/gems/gems/winrm-1.8.1/lib/winrm/command_executor.rb:71:in open' from /opt/vagrant/embedded/gems/gems/winrm-1.8.1/lib/winrm/winrm_service.rb:359:increate_executor' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/communicators/winrm/shell.rb:176:in executor' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/communicators/winrm/shell.rb:59:inpowershell' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/communicators/winrm/communicator.rb:107:in block in ready?' from /opt/vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:inblock in timeout' from /opt/vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in block in catch' from /opt/vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:incatch' from /opt/vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in catch' from /opt/vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:intimeout' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/communicators/winrm/communicator.rb:106:in ready?' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/machine.rb:260:inguest' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/synced_folders/rsync/helper.rb:154:in rsync_single' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/synced_folders/rsync/synced_folder.rb:48:inblock in enable' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/synced_folders/rsync/synced_folder.rb:47:in each' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/synced_folders/rsync/synced_folder.rb:47:inenable' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/synced_folders.rb:93:in block in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/synced_folders.rb:90:ineach' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/synced_folders.rb:90:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/synced_folders/nfs/action_cleanup.rb:25:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/providers/virtualbox/action/prepare_nfs_valid_ids.rb:12:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:49:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/providers/virtualbox/action/prepare_forwarded_port_collision_params.rb:30:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/env_set.rb:19:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/provision.rb:80:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/providers/virtualbox/action/clear_forwarded_ports.rb:15:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/providers/virtualbox/action/set_name.rb:19:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/providers/virtualbox/action/clean_machine_folder.rb:17:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/providers/virtualbox/action/check_accessible.rb:18:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:95:in block in finalize_action' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builder.rb:116:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in block in run' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/util/busy.rb:19:inbusy' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in run' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/call.rb:53:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:95:inblock in finalize_action' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builder.rb:116:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:inblock in run' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/util/busy.rb:19:in busy' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:inrun' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/call.rb:53:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:95:in block in finalize_action' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builder.rb:116:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in block in run' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/util/busy.rb:19:inbusy' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in run' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/call.rb:53:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/box_check_outdated.rb:23:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/config_validate.rb:25:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/providers/virtualbox/action/check_virtualbox.rb:17:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:95:inblock in finalize_action' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:95:in block in finalize_action' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builder.rb:116:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in block in run' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/util/busy.rb:19:inbusy' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in run' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/call.rb:53:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/config_validate.rb:25:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:95:inblock in finalize_action' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:95:in block in finalize_action' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builder.rb:116:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in block in run' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/util/busy.rb:19:inbusy' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in run' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/call.rb:53:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/providers/virtualbox/action/check_virtualbox.rb:17:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builder.rb:116:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in block in run' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/util/busy.rb:19:inbusy' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in run' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/machine.rb:225:inaction_raw' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/machine.rb:200:in block in action' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/environment.rb:561:inlock' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/machine.rb:186:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/machine.rb:186:inaction' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/batch_action.rb:82:in block (2 levels) in run' from /opt/vagrant/embedded/gems/gems/logging-2.1.0/lib/logging/diagnostic_context.rb:450:incall' from /opt/vagrant/embedded/gems/gems/logging-2.1.0/lib/logging/diagnostic_context.rb:450:in `block in create_with_logging_context'

narration-sd commented 6 years ago

Well, again, you will have to be patient.

snfnwgi commented 6 years ago

Thank you. Isn't SMB also not in sync with WINDOWS?I have just tried a new version of vagrant. I have found the answers online, but I haven't found them.

boot error

Bringing machine 'default' up with 'virtualbox' provider... ==> default: Clearing any previously set forwarded ports... ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat ==> default: Forwarding ports... default: 5985 (guest) => 55985 (host) (adapter 1) default: 5986 (guest) => 55986 (host) (adapter 1) default: 22 (guest) => 2222 (host) (adapter 1) ==> default: Running 'pre-boot' VM customizations... ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... default: WinRM address: 127.0.0.1:55985 default: WinRM username: IEUser default: WinRM execution_time_limit: PT2H default: WinRM transport: negotiate ==> default: Machine booted and ready! ==> default: Checking for guest additions in VM... ==> default: The machine you're rsyncing folders to is configured to use ==> default: password-based authentication. Vagrant can't script rsync to automatically ==> default: enter this password, so you'll likely be prompted for a password ==> default: shortly. ==> default: ==> default: If you don't want to have to do this, please enable automatic ==> default: key insertion using config.ssh.insert_key. ==> default: Rsyncing folder: /vagrant/win7/modernie-winrm/ExtraFolder/ => /cygdrive/c/a IEUser@127.0.0.1's password: There was an error when attempting to rsync a synced folder. Please inspect the error message below for more info.

Host path: /vagrant/win7/modernie-winrm/ExtraFolder/ Guest path: /cygdrive/c/a Command: "rsync" "--verbose" "--archive" "--delete" "-z" "--copy-links" "--no-owner" "--no-group" "-e" "ssh -p 2222 -o LogLevel=FATAL -o ControlMaster=auto -o ControlPath=/var/folders/lh/30g3_bms2ns1mq5d7y1t9rtc0000gn/T/ssh.308 -o ControlPersist=10m -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null" "--exclude" ".vagrant/" "/vagrant/win7/modernie-winrm/ExtraFolder/" "IEUser@127.0.0.1:/cygdrive/c/a" Error: sh: rsync: command not found rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(601) [sender=3.0.7]

narration-sd commented 6 years ago

To use rsync, you have to install it.

To use the kind of development software Vagrant is, you're expected to look up how to do things like this. The information is there; and against further questions, sometimes you have to look for the most recent instructions or experiences which modify from these, to be successful.

snfnwgi commented 6 years ago

Hello, I have installed rsync.

rsync -v rsync version 3.0.7 protocol version 30 Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, no iconv, symtimes, file-flags

rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU

narration-sd commented 6 years ago

@snfnwgi I have to go. It isn't enough often to just install things -- this is not phone apps land. You have to work out how to make their connections.

I checked, and the version of rsync that works for me is MinGW msys. I would uninstall and get this if you aren't using it, as versions differ. I think this version is recommended in the Vagrant documentation for rsync.

Then you need to assure that your path contains the directory under MinGW where rsync is. The Windows command 'where rsync' should show if you have this set up correctly, as the MinGW installer should do.

Then Vagrant booting will find rsync.

snfnwgi commented 6 years ago

@narration-sd I'm using MAC OS, haha, thank you, I'm looking for other answers, cheers

narration-sd commented 6 years ago

Well, my young friend, you opened this long conversation saying you were using Windows on Mac hardware.

I think you will now work this out yourself.

snfnwgi commented 6 years ago

Haha, what do you mean? I am a little dizzy. My question is clear at the beginning. Vagrant version

vagrant 1.8.1

Host operating system

mac

Guest operating system

windows7

Vagrantfile

narration-sd commented 6 years ago

Well, then, the same needs hold -- in this case rsync must be findable on the PATH of the guest machine. And also on the host, the Mac. Both ends must have rsync installed and executable from a shell -- in understanding of how it works.

The advice will change then for what arrangements are possible and work, besides rsync.

I suggest again that you use google and learn what the most recent advice is. Which seems it would include not using High Sierra yet. It and 2.0 Vagrant appear to be released before ready, and for each other..

snfnwgi commented 6 years ago

Thank you for your valuable advice. My last question, if it's MACOS running WINDOWS, can you use NFS?

narration-sd commented 6 years ago

Well, here we are back to @briancain 's first reply, I believe.

narration-sd commented 6 years ago

You know, it must occur to ask -- if you want Windows on a Mac, why not run Parallels, or whatever the latest good flavor of co-working is?

No Vagrant then. Maybe you want Windows versions which don't work with those however?

The other thought is what I mentioned above about running the VMware provider. There is a question whether the online doc is out of date as far as which VMware Fusion versions can run the Homestead/Vagrant boxes, which you would have to work out.

This I suspect is the limit of what I usefully am aware of for your case.

snfnwgi commented 6 years ago

It's just synchronous, the default vagrant synchronization mode, the access is a little bit slow, so I want to change it a different way.Because of my work, my environment must run under WINDOWS, so WINDOWS7 is installed.I just try once, I also installed the RSYNC inside the virtual machine, but the same error when I sync or a newspaper, good helpless, is there any better way, I'm sorry my English is not good, I said is through the translation software and you said..

narration-sd commented 6 years ago

Ok, I understand about languages, have lived in Asia (Korea) and Europe many years. Good to take advantage of the translation tools.

That error you show seems simple: that the rsync executable can't be found; I am not sure on which end, but it seems the Windows end. In either case, setting and verifying the PATHs on both host and guest rsyncs should clear this problem.

Yes, the virtualbox implementation is slow.

snfnwgi commented 6 years ago

Ha ha ha, thank you, you are full of awe. But actually I'm in the terminal and there is an implementation of rsync and I can find it. How can I check this problem?

narration-sd commented 6 years ago

So, at the Mac command line terminal, you can verify rsync --version there.

Using then vagrant sshcommand on the same terminal sessioni, you can log in to the Windows guest. If it asks user/password, use vagrant/vagrant. Then see if rsync --version gets you the expected result there.

If not, you can look into setting Windows PATH -- it's in the System interface, Advanced tab I think, but look this up with pictures via google.

narration-sd commented 6 years ago

I need to go for a walk now, and then will sleep. I will check once more in between, if I think you have enough informtion to work with now -- cheers...

snfnwgi commented 6 years ago

It's hard for you to go to bed after the walk. Cheers

narration-sd commented 6 years ago

yes, but I have to do it :)

snfnwgi commented 6 years ago

Ha ha ha, have a good rest, thank you big brother

narration-sd commented 6 years ago

Most welcome, and for that memory of speaking...

snfnwgi commented 6 years ago

Ha ha ha, I am also glad to have your guidance today

snfnwgi commented 6 years ago

I installed rsync on the virtual machine windows in this way

  1. Download the Cygwin from https://mingw-w64.org/doku.php/download/cygwin 2.Install the Cygwin with rsync + openssh modules. It's important bacause they is basent on a Window (you may select packages to install during installation on the Select packages phase) 3.Add x:\cygwin\bin, where 'x' is the drive on which you have installed the cygwin distribution, to the SYSTEM PATH.

I feel the problem will soon be resolved, but do not know where the problem boot error

ringing machine 'default' up with 'virtualbox' provider... ==> default: Clearing any previously set forwarded ports... ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat ==> default: Forwarding ports... default: 5985 (guest) => 55985 (host) (adapter 1) default: 5986 (guest) => 55986 (host) (adapter 1) default: 22 (guest) => 2222 (host) (adapter 1) ==> default: Running 'pre-boot' VM customizations... ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... default: WinRM address: 127.0.0.1:55985 default: WinRM username: IEUser default: WinRM execution_time_limit: PT2H default: WinRM transport: negotiate ==> default: Machine booted and ready! ==> default: Checking for guest additions in VM... ==> default: The machine you're rsyncing folders to is configured to use ==> default: password-based authentication. Vagrant can't script rsync to automatically ==> default: enter this password, so you'll likely be prompted for a password ==> default: shortly. ==> default: ==> default: If you don't want to have to do this, please enable automatic ==> default: key insertion using config.ssh.insert_key. ==> default: Rsyncing folder: /vagrant/win7/modernie-winrm/ExtraFolder/ => /cygdrive/c/ExtraFolder IEUser@127.0.0.1's password: There was an error when attempting to rsync a synced folder. Please inspect the error message below for more info.

Host path: /vagrant/win7/modernie-winrm/ExtraFolder/ Guest path: /cygdrive/c/ExtraFolder Command: "rsync" "--verbose" "--archive" "--delete" "-z" "--copy-links" "--no-owner" "--no-group" "-e" "ssh -p 2222 -o LogLevel=FATAL -o ControlMaster=auto -o ControlPath=/var/folders/lh/30g3_bms2ns1mq5d7y1t9rtc0000gn/T/ssh.485 -o ControlPersist=10m -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null" "--exclude" ".vagrant/" "/vagrant/win7/modernie-winrm/ExtraFolder/" "IEUser@127.0.0.1:/cygdrive/c/ExtraFolder" Error: rsync version 3.1.2 protocol version 31 Copyright (C) 1996-2015 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, no xattrs, iconv, symtimes, prealloc

rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details.

rsync is a file transfer program capable of efficient remote update via a fast differencing algorithm.

Usage: rsync [OPTION]... SRC [SRC]... DEST or rsync [OPTION]... SRC [SRC]... [USER@]HOST:DEST or rsync [OPTION]... SRC [SRC]... [USER@]HOST::DEST or rsync [OPTION]... SRC [SRC]... rsync://[USER@]HOST[:PORT]/DEST or rsync [OPTION]... [USER@]HOST:SRC [DEST] or rsync [OPTION]... [USER@]HOST::SRC [DEST] or rsync [OPTION]... rsync://[USER@]HOST[:PORT]/SRC [DEST] The ':' usages connect via remote shell, while '::' & 'rsync://' usages connect to an rsync daemon, and require SRC or DEST to start with a module name.

Options -v, --verbose increase verbosity --info=FLAGS fine-grained informational verbosity --debug=FLAGS fine-grained debug verbosity --msgs2stderr special output handling for debugging -q, --quiet suppress non-error messages --no-motd suppress daemon-mode MOTD (see manpage caveat) -c, --checksum skip based on checksum, not mod-time & size -a, --archive archive mode; equals -rlptgoD (no -H,-A,-X) --no-OPTION turn off an implied OPTION (e.g. --no-D) -r, --recursive recurse into directories -R, --relative use relative path names --no-implied-dirs don't send implied dirs with --relative -b, --backup make backups (see --suffix & --backup-dir) --backup-dir=DIR make backups into hierarchy based in DIR --suffix=SUFFIX set backup suffix (default ~ w/o --backup-dir) -u, --update skip files that are newer on the receiver --inplace update destination files in-place (SEE MAN PAGE) --append append data onto shorter files --append-verify like --append, but with old data in file checksum -d, --dirs transfer directories without recursing -l, --links copy symlinks as symlinks -L, --copy-links transform symlink into referent file/dir --copy-unsafe-links only "unsafe" symlinks are transformed --safe-links ignore symlinks that point outside the source tree --munge-links munge symlinks to make them safer (but unusable) -k, --copy-dirlinks transform symlink to a dir into referent dir -K, --keep-dirlinks treat symlinked dir on receiver as dir -H, --hard-links preserve hard links -p, --perms preserve permissions -E, --executability preserve the file's executability --chmod=CHMOD affect file and/or directory permissions -A, --acls preserve ACLs (implies --perms) -o, --owner preserve owner (super-user only) -g, --group preserve group --devices preserve device files (super-user only) --specials preserve special files -D same as --devices --specials -t, --times preserve modification times -O, --omit-dir-times omit directories from --times -J, --omit-link-times omit symlinks from --times --super receiver attempts super-user activities -S, --sparse handle sparse files efficiently --preallocate allocate dest files before writing them -n, --dry-run perform a trial run with no changes made -W, --whole-file copy files whole (without delta-xfer algorithm) -x, --one-file-system don't cross filesystem boundaries -B, --block-size=SIZE force a fixed checksum block-size -e, --rsh=COMMAND specify the remote shell to use --rsync-path=PROGRAM specify the rsync to run on the remote machine --existing skip creating new files on receiver --ignore-existing skip updating files that already exist on receiver --remove-source-files sender removes synchronized files (non-dirs) --del an alias for --delete-during --delete delete extraneous files from destination dirs --delete-before receiver deletes before transfer, not during --delete-during receiver deletes during the transfer --delete-delay find deletions during, delete after --delete-after receiver deletes after transfer, not during --delete-excluded also delete excluded files from destination dirs --ignore-missing-args ignore missing source args without error --delete-missing-args delete missing source args from destination --ignore-errors delete even if there are I/O errors --force force deletion of directories even if not empty --max-delete=NUM don't delete more than NUM files --max-size=SIZE don't transfer any file larger than SIZE --min-size=SIZE don't transfer any file smaller than SIZE --partial keep partially transferred files --partial-dir=DIR put a partially transferred file into DIR --delay-updates put all updated files into place at transfer's end -m, --prune-empty-dirs prune empty directory chains from the file-list --numeric-ids don't map uid/gid values by user/group name --usermap=STRING custom username mapping --groupmap=STRING custom groupname mapping --chown=USER:GROUP simple username/groupname mapping --timeout=SECONDS set I/O timeout in seconds --contimeout=SECONDS set daemon connection timeout in seconds -I, --ignore-times don't skip files that match in size and mod-time -M, --remote-option=OPTION send OPTION to the remote side only --size-only skip files that match in size --modify-window=NUM compare mod-times with reduced accuracy -T, --temp-dir=DIR create temporary files in directory DIR -y, --fuzzy find similar file for basis if no dest file --compare-dest=DIR also compare destination files relative to DIR --copy-dest=DIR ... and include copies of unchanged files --link-dest=DIR hardlink to files in DIR when unchanged -z, --compress compress file data during the transfer --compress-level=NUM explicitly set compression level --skip-compress=LIST skip compressing files with a suffix in LIST -C, --cvs-exclude auto-ignore files the same way CVS does -f, --filter=RULE add a file-filtering RULE -F same as --filter='dir-merge /.rsync-filter' repeated: --filter='- .rsync-filter' --exclude=PATTERN exclude files matching PATTERN --exclude-from=FILE read exclude patterns from FILE --include=PATTERN don't exclude files matching PATTERN --include-from=FILE read include patterns from FILE --files-from=FILE read list of source-file names from FILE -0, --from0 all *-from/filter files are delimited by 0s -s, --protect-args no space-splitting; only wildcard special-chars --address=ADDRESS bind address for outgoing socket to daemon --port=PORT specify double-colon alternate port number --sockopts=OPTIONS specify custom TCP options --blocking-io use blocking I/O for the remote shell --stats give some file-transfer stats -8, --8-bit-output leave high-bit chars unescaped in output -h, --human-readable output numbers in a human-readable format --progress show progress during transfer -P same as --partial --progress -i, --itemize-changes output a change-summary for all updates --out-format=FORMAT output updates using the specified FORMAT --log-file=FILE log what we're doing to the specified FILE --log-file-format=FMT log updates using the specified FMT --password-file=FILE read daemon-access password from FILE --list-only list the files instead of copying them --bwlimit=RATE limit socket I/O bandwidth --outbuf=N|L|B set output buffering to None, Line, or Block --write-batch=FILE write a batched update to FILE --only-write-batch=FILE like --write-batch but w/o updating destination --read-batch=FILE read a batched update from FILE --protocol=NUM force an older protocol version to be used --iconv=CONVERT_SPEC request charset conversion of filenames --checksum-seed=NUM set block/file checksum seed (advanced) --noatime do not alter atime when opening source files -4, --ipv4 prefer IPv4 -6, --ipv6 prefer IPv6 --version print version number (-h) --help show this help (-h is --help only if used alone)

Use "rsync --daemon --help" to see the daemon-mode command-line options. Please see the rsync(1) and rsyncd.conf(5) man pages for full documentation. See http://rsync.samba.org/ for updates, bug reports, and answers rsync error: syntax or usage error (code 1) at main.c(1569) [client=3.1.2] rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(601) [sender=3.0.7]

==> default: The previous process exited with exit code 1.

snfnwgi commented 6 years ago

@narration-sd @briancain God for help

ghost commented 4 years ago

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.