2017-08-15 2 views
1

windowsマシン上のフォルダ全体を、ubuntu/trusty64をホストするVMにコピーします。悪意のあるゲストアドオンが正しくインストールされているようですが(5.1.20)、実行されていません。

しかし、私はいつも私の悪口を持ってきてみると、私は下のエラーメッセージを受け取ります。

vagrant up 
Bringing machine 'default' up with 'virtualbox' provider... 
==> default: Checking if box 'ubuntu/trusty64' is up to date... 
==> 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: Adapter 2: hostonly 
==> default: Forwarding ports... 
    default: 22 (guest) => 2222 (host) (adapter 1) 
==> default: Booting VM... 
==> default: Waiting for machine to boot. This may take a few minutes... 
    default: SSH address: 127.0.0.1:2222 
    default: SSH username: vagrant 
    default: SSH auth method: private key 
==> default: Machine booted and ready! 
==> default: Configuring proxy for Apt... 
==> default: Configuring proxy environment variables... 
[default] GuestAdditions seems to be installed (5.1.20) correctly, but not running. 
vboxadd: unrecognized service 
vboxadd-service: unrecognized service 
bash: line 4: setup: command not found 
==> default: Checking for guest additions in VM... 
The following SSH command responded with a non-zero exit status. 
Vagrant assumes that this means the command failed! 

setup 

Stdout from the command: 



Stderr from the command: 

bash: line 4: setup: command not found 

注:3行目に見ることができるよう
Ubuntuのバージョンは最新です。
ベイグラントバージョン:1.9.3ベイグラント
Windows版:Windows 7のエンタープライズのService Pack 1
のOracle VirtualBoxのバージョン:状態vbguestコマンドを実行するにはバージョン5.1.20 r114628(Qt5.6.2)

私が手

$ vagrant vbguest --status 
[default] GuestAdditions seems to be installed (5.1.20) correctly, but not running. 

私の放浪ファイルの内容が

# 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 = "ubuntu/trusty64" 
    config.ssh.insert_key = false 
    # 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: "xxxxx" 

    # 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" , "/vagrant" 
    config.vm.synced_folder ".", "/mydata", :mount_options => ['dmode=775','fmode=664'] 
    #config.vm.synced_folder "./", "/vagrant", id: "vagrant-root", type: "nfs" 

    # 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 
    # apt-get update 
    # apt-get install -y apache2 
    # SHELL 
    if Vagrant.has_plugin?("vagrant-proxyconf") 
    config.proxy.http  = "xxxxx" 
    config.proxy.https  = "xxxxx" 
    config.proxy.ftp  = "xxxxx" 
    config.apt_proxy.http = "xxxxx" 
    config.apt_proxy.https = "xxxxx" 
    config.proxy.no_proxy = "xxxxx" 
    end 

    if !Vagrant.has_plugin?("vagrant-proxyconf") 
    system('vagrant plugin install vagrant-proxyconf')  
    raise("vagrant-proxyconf installed. Run command again."); 
    end 

end 

ある
を提案して下さい 1.このエラーを修正するにはどうすればよいですか?
2. WindowsからVmまでの完全なフォルダを共有しますか?

+1

これは[公式の仮想ボックスフォーラム](https://forums.virtualbox.org)で質問する必要がありますようなようです。 – APC

+0

同じ問題が発生しました。あなたはそれを解決することができましたか? –

+0

実際、私はそれに多くの努力を払うことができませんでした...そして、その瞬間に私の与えられた仕事を終わらせるための仕事を見つけました。 しかし、解決策を見つけて私にも分かれば素晴らしいことでしょう。 –

答えて

0

WinSCPを使用してゲストVMを接続します。 VBoxGuestAddition.isoをホストマシンからコピーします。私の場合、VBoxGuestAdditionはC:\ ProgramFiles \ Oracle \ VirtualBoxにあります。

ゲストVMにisoファイルがコピーされたら、puttyを使用してゲストVMにログインします。そして

mkdir /media/GuestAdditionsISO 

一旦

cd /media/GuestAdditionsISO 
sudo ./VBoxLinuxGuestAddition.run 

再度開始VM、正常に実行されたコマンドをマウント

mount -o loop /path/of/VBoxGuestAddition.iso /media/GuestAdditionsISO 

以下のコマンドを実行します。これは私のために働きます

関連する問題