为什么Vagrant不在Windows 8 64位和32位上共享文件夹?

时间:2015-05-14 16:54:31

标签: ruby-on-rails ruby ubuntu vagrant virtualbox

我正在使用:

Windows 8 64-bit
vagrant 1.7.2
Virtual Box 4.3.28
GitBash 1.9.4 for SSH connection
Box Ubuntu 14:04:02 Trusty32 and
Box Ubuntu 14:04:02 Trusty64

我在ubuntu / trusty32上的rails上使用everioment开发ruby,在windows64上使用trusty / 64。 一切都运作良好,但我不能分享流浪汉之间的窗口上的文件夹。

这是我的Vagrant文​​件:

   # -*- mode: ruby -*-
   # vi: set ft=ruby :

   # All Vagrant configuration is done below. The "2" in Vagrant.configure 
   # configures the configuration version (we support older styles for
   # backwards compatibility). Please don't change it unless you know what 
   # you're doing.
   Vagrant.configure(2) do |config|
   # The most common configuration options are documented and commented below.
   # For a complete reference, please see the online documentation at
   # https://docs.vagrantup.com.

   # Every Vagrant development environment requires a box. You can search for
   # boxes at https://atlas.hashicorp.com/search.
   config.vm.box = "trusty64"

   # Disable automatic box update checking. If you disable this, then
   # boxes will only be checked for updates when the user runs
   # `vagrant box outdated`. This is not recommended.
   # config.vm.box_check_update = false

   # Create a forwarded port mapping which allows access to a specific port
   # within the machine from a port on the host machine. In the example below,
   # accessing "localhost:8080" will access port 80 on the guest machine.
   # config.vm.network "forwarded_port", guest: 80, host: 8080

   # Create a private network, which allows host-only access to the machine
   # using a specific IP.
   # config.vm.network "private_network", ip: "192.168.33.10"

   # Create a public network, which generally matched to bridged network.
   # Bridged networks make the machine appear as another physical device on
   # your network.
   # config.vm.network "public_network"

   # Share an additional folder to the guest VM. The first argument is
   # the path on the host to the actual folder. The second argument is
   # the path on the guest to mount the folder. And the optional third
   # argument is a set of non-required options.
   # config.vm.synced_folder "../data", "/vagrant_data"

   # Provider-specific configuration so you can fine-tune various
   # backing providers for Vagrant. These expose provider-specific options.
   # Example for VirtualBox:
   #
   # 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 = "1024"
   # end
   #
   # View the documentation for the provider you are using for more
   # information on available options.

   # Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
   # such as FTP and Heroku are also available. See the documentation at
   # https://docs.vagrantup.com/v2/push/atlas.html for more information.
   # config.push.define "atlas" do |push|
   #   push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
   # end

   # Enable provisioning with a shell script. Additional provisioners such as
   # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
   # documentation for more information about their specific syntax and use.
   # config.vm.provision "shell", inline: <<-SHELL
   #   sudo apt-get update
   #   sudo apt-get install -y apache2
   # SHELL
end 

Windows上的Trusty64无法连接。 Windows上的Trusty32确定,但不共享。

2 个答案:

答案 0 :(得分:0)

我在类似的配置上遇到了这个问题并修复了它:

  1. vagrant ssh
  2. sudo ln -s /opt/VBoxGuestAdditions-4.3.10/lib/VBoxGuestAdditions / usr / lib / VBoxGuestAdditions
  3. 出口
  4. vagrant reload

答案 1 :(得分:0)

我通过使用我在vagrantcloud中找到的另一个盒子解决了这个问题。 在一切正常工作后首先在Mac上设置,我生了一个垃圾箱(包),然后去了Windows 8专业版,做了正常的程序而且工作正常!

我重新使用64位,Window32不支持nfs,并在BIOS中启用虚拟化。