Vagrant EDX-/tmp/vboxguestaditions.iso:设备上没有剩余空间（运行时错误）
在使用Eucalyptus 2 open release为EDX fullstack执行“vagrant up”时，我收到以下错误消息-Vagrant EDX-/tmp/vboxguestaditions.iso:设备上没有剩余空间（运行时错误）,vagrant,virtualbox,ubuntu-16.04,edx,Vagrant,Virtualbox,Ubuntu 16.04,Edx,在使用Eucalyptus 2 open release为EDX fullstack执行“vagrant up”时，我收到以下错误消息- /tmp/vboxguestaditions.iso:设备上没有剩余空间（运行时错误） 我正在运行Ubuntu 16.0.4 LTS 还有一个报告称，Guestaditions版本不匹配。 我知道这个主机还没有得到官方的支持，但我确实喜欢先锋=] Got different reports about installed GuestAdditions vers
/tmp/vboxguestaditions.iso:设备上没有剩余空间（运行时错误）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...
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)
~$ 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 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
我通过删除“~/.vagrant.d”下除box目录之外的所有内容来解决这个问题。并改为“开放发布/桉树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.
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
我通过删除“~/.vagrant.d”下除box目录之外的所有内容来解决这个问题。并改为“开放发布/桉树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.
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
不清楚这条消息是关于主机操作系统还是关于来宾操作系统？你能给我们看一下：sudo du-sh/*的输出吗？谢谢，内德，这是给来宾操作系统的。主机上有足够的空间。有另一个VirtualBox安装的残余。。我不确定我是否通过删除。。。我回到一个老问题。我将编辑帖子。不清楚该消息是关于主机操作系统还是来宾操作系统？你能给我们看一下：sudo du-sh/*的输出吗？谢谢，内德，这是给来宾操作系统的。主机上有足够的空间。有另一个VirtualBox安装的残余。。我不确定我是否通过删除。。。我回到一个老问题。我会编辑这篇文章