在做“流浪”的时候＆＃39;对于带有Eucalyptus 2开放版本的EDX fullstack，我收到此错误消息 -
/tmp/VBoxGuestAdditions.iso: No space left on device (RuntimeError)
我正在运行Ubuntu 16.0.4 LTS
另外还有报告称GuestAdditions版本不匹配。 我知道这个主机还没有得到官方支持，但我确实喜欢开拓=]
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims: 4.2.0
VBoxService inside the vm claims: 5.0.20
Going on, assuming VBoxService is correct...
[default] GuestAdditions versions on your host (5.0.24) and guest (5.0.20) do not match.
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims: 4.2.0
VBoxService inside the vm claims: 5.0.20
Going on, assuming VBoxService is correct...
The guest's platform ("linux") is currently not supported, will try generic Linux method...
我有另一个VirtualBox安装的残余。在清除了另一个软件包之后，我得到了一个不同的错误 - 我在尝试更新版本的VirtualBox之前遇到了一个错误。所以我不确定原始错误是否已解决。
这是新错误 -
Installing the 'vagrant-hostsupdater' plugin. This can take a few minutes...
/usr/lib/ruby/2.3.0/rubygems/specification.rb:946:in `all=': undefined method `group_by' for nil:NilClass (NoMethodError)
在我使用devstack之前，我使用了一种解决方法来解决这个问题。 我将修改该文件并重试。
更多配置信息 -
~$ dpkg -l | grep virtualbox
ii unity-scope-virtualbox 0.1+13.10.20130723-0ubuntu1 all VirtualBox scope for Unity
ii virtualbox 5.0.24-dfsg-0ubuntu1.16.04.1 amd64 x86 virtualization solution - base binaries
ii virtualbox-dkms 5.0.24-dfsg-0ubuntu1.16.04.1 all x86 virtualization solution - kernel module sources for dkms
ii virtualbox-guest-additions-iso 5.0.24-0ubuntu1.16.04.1 all guest additions iso image for VirtualBox
ii virtualbox-qt 5.0.24-dfsg-0ubuntu1.16.04.1 amd64 x86 virtualization solution - Qt based user interface
~$ dpkg -l | grep vagrant
ii vagrant 1.8.1+dfsg-1
**我现在已经将Vagrant更新为1.8.5并解决了未定义的方法`group_by＆＃39;＆＃34;但空间问题仍然存在 这是最新的输出 -
vagrant up --provider virtualbox
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'eucalyptus-fullstack-2016-09-01'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: fullstack_default_1473446522717_26289
==> 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: Running 'pre-boot' VM customizations...
==> 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!
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims: 4.2.0
VBoxService inside the vm claims: 5.0.20
Going on, assuming VBoxService is correct...
[default] GuestAdditions versions on your host (5.0.24) and guest (5.0.20) do not match.
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims: 4.2.0
VBoxService inside the vm claims: 5.0.20
Going on, assuming VBoxService is correct...
The guest's platform ("linux") is currently not supported, will try generic Linux method...
Copy iso file /usr/share/virtualbox/VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
==> 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.2.0
default: VirtualBox Version: 5.0
==> default: [vagrant-hostsupdater] Checking for host entries
==> default: [vagrant-hostsupdater] found entry for: 192.168.33.10 preview.localhost
==> default: Forcing shutdown of VM...
==> default: Destroying VM and associated drives...
/opt/vagrant/embedded/gems/gems/net-scp-1.1.2/lib/net/scp.rb:392:in `await_response_state': scp: /tmp/VBoxGuestAdditions.iso: No space left on device (RuntimeError)
主机上的磁盘空间使用情况 -
$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 3.5G 0 3.5G 0% /dev
tmpfs 717M 9.4M 708M 2% /run
/dev/sda2 910G 13G 851G 2% /
tmpfs 3.6G 172K 3.6G 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.6G 0 3.6G 0% /sys/fs/cgroup
/dev/sda1 511M 3.6M 508M 1% /boot/efi
tmpfs 717M 44K 717M 1% /run/user/1000
更新 -
我注意到这个空间实际上并没有在客人身上使用，但我认为保留......
vagrant@precise64:~$ ls -alh /empty
-rw-r--r-- 1 root root 69G Sep 1 11:45 /empty
答案 0 :(得分：0)
我通过删除除“〜/ .vagrant.d”下的boxes目录之外的所有内容解决了这个问题。并改为“open-release / eucalyptus.1”
那里肯定有一个旧的配置项。
另一方面，我之后收到了这个错误 -
==> default: [vagrant-hostsupdater] found entry for: 192.168.33.10 preview.localhost
==> default: Configuring and enabling network interfaces...
Vagrant attempted to execute the capability 'configure_networks'
on the detect guest OS 'linux', 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.
但是通过编辑Vagrant文件解决了这个问题 -
config.vm.network :private_network, ip: "192.168.33.10"
到此 -
config.vm.network :private_network, ip: "192.168.33.10", type: "dhcp", auto_config: false