此问题是在拥有不异配置的环境中，项目在win10跑的慢而在win7就正常的情况下发明的，一步步调试之后发明是文件操纵的相关行为变的很慢，于是考虑到可能是系统问题，，后来在如下链接找到了解决步伐：
1。nfs方法
安置vagrant 插件 vagrant-winnfsd$ vagrant plugin install vagrant-winnfsd
但是这样安置会呈现以下错误
Installing the ‘vagrant-winnfsd‘ plugin. This can take a few minutes... 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: An error occurred while installing childprocess (0.5.8), and Bundler cannot continue. Make sure that `gem install childprocess -v ‘0.5.8‘` succeeds before bundling. Warning: this Gemfile contains multiple primary sources. Using `source` more than once without a block is a security risk, and may result in installing unexpected gems. To resolve this warning, use a block to indicate which gems should come from the secondary source. To upgrade this warning to an error, run `bundle config disable_multisource true`.Gem::RemoteFetcher::FetchError: Errno::ECONNABORTED: An established connection was aborted by the software in your host machine. - SSL_connect (https://rubygems.org/gems/childprocess-0.5.8.gem)
看来是缺少childprocess-0.5.8.gem这个对象
索性把需要的包都下载到本地,然后本地安置
https://rubygems.org/gems/childprocess-0.5.8.gem
https://rubygems.org/gems/vagrant-winnfsd-1.1.0.gem
然后
vagrant plugin install childprocess-0.5.8.gem vagrant plugin install vagrant-winnfsd-1.1.0.gem
看一看安置好的插件
$ vagrant plugin list childprocess (0.5.8) - Version Constraint: 0.5.8 vagrant-share (1.1.4, system) vagrant-winnfsd (1.1.0) - Version Constraint: 1.1.0
编纂项目下的Vagrantfile文件
Vagrant.configure(‘2‘) do |config| # other config here config.vm.network "private_network", ip: "192.168.33.10" #winfsd config.winnfsd.logging = "on" config.winnfsd.uid = 1 config.winnfsd.gid = 1 config.vm.synced_folder "./", "/vagrant", type: "nfs" end
2.SMB方法
Vagrant.configure(‘2‘) do |config| # other config here config.vm.network "private_network", ip: "192.168.33.10" #SMB config.vm.synced_folder "./", "/vagrant", type: "smb", smb_username: "母鸡Windows帐号", smb_password: "母鸡Windows暗码", owner: "www", group: "www" #mount_options: ["dmode=775,fmode=664"] end
启动vagrant虚拟机, 注意启动过程傍边需要输入windwos系统的帐号和暗码
d:\projects>vagrant up Bringing machine ‘default‘ up with ‘virtualbox‘ provider... ==> default: Fixed port collision for 22 => 2222. Now on port 2200. ==> default: Preparing SMB shared folders... default: You will be asked for the username and password to use for the SMB default: folders shortly. Please use the proper username/password of your default: Windows account. default: default: Username: administrator default: Password (will be hidden): ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat default: Adapter 2: hostonly ==> default: Forwarding ports... default: 22 => 2200 (adapter 1) ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... default: SSH address: 127.0.0.1:2200 default: SSH username: vagrant default: SSH auth method: private key default: Warning: Connection timeout. Retrying... default: Warning: Connection timeout. Retrying... default: Warning: Remote connection disconnect. Retrying... ==> default: Machine booted and ready! ==> default: Checking for guest additions in VM... default: The guest additions on this VM do not match the installed version of default: VirtualBox! In most cases this is fine, but in rare cases it can default: prevent things such as shared folders from working properly. If you see default: shared folder errors, please make sure the guest additions within the default: virtual machine match the version of VirtualBox you have installed on default: your host and reload your VM. default: default: Guest Additions Version: 4.3.26 default: VirtualBox Version: 5.0 ==> default: Configuring and enabling network interfaces... ==> default: Mounting SMB shared folders... default: D:/projects => /vagrant ==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision` ==> default: flag to force provisioning. Provisioners marked to run always will still run. d:\projects>