P4-vSwitch / vagrant

PISCES Simulation Environment
30 stars 15 forks source link

issue in 'vagrant up' #8

Open namratalimaye opened 7 years ago

namratalimaye commented 7 years ago

I am getting following error - root@osboxes vagrant]# vagrant up Bringing machine 'switch' up with 'libvirt' provider... Bringing machine 'generator' up with 'libvirt' provider... Bringing machine 'receiver' up with 'libvirt' provider... ==> receiver: Box 'pisces-ubuntu-trusty64' could not be found. Attempting to find and install... receiver: Box Provider: libvirt receiver: Box Version: >= 0 ==> receiver: Box file was not detected as metadata. Adding it directly... ==> receiver: Adding box 'pisces-ubuntu-trusty64' (v0) for provider: libvirt receiver: Downloading: pisces-ubuntu-trusty64 ==> generator: Box 'pisces-ubuntu-trusty64' could not be found. Attempting to find and install... ==> receiver: An error occurred. The error will be shown after all tasks complete. generator: Box Provider: libvirt generator: Box Version: >= 0 ==> generator: Box file was not detected as metadata. Adding it directly... ==> generator: Adding box 'pisces-ubuntu-trusty64' (v0) for provider: libvirt generator: Downloading: pisces-ubuntu-trusty64 ==> generator: An error occurred. The error will be shown after all tasks complete. ==> switch: Box 'pisces-ubuntu-trusty64' could not be found. Attempting to find and install... switch: Box Provider: libvirt switch: Box Version: >= 0 ==> switch: Box file was not detected as metadata. Adding it directly... ==> switch: Adding box 'pisces-ubuntu-trusty64' (v0) for provider: libvirt switch: Downloading: pisces-ubuntu-trusty64 ==> switch: An error occurred. The error will be shown after all tasks complete. An error occurred while executing multiple actions in parallel. Any errors that occurred are shown below.

An error occurred while executing the action on the 'switch' machine. Please handle this error then try again:

An error occurred while downloading the remote file. The error message, if any, is reproduced below. Please fix this error and try again.

Couldn't open file /home/osboxes/vagrant/pisces-ubuntu-trusty64

An error occurred while executing the action on the 'generator' machine. Please handle this error then try again:

An error occurred while downloading the remote file. The error message, if any, is reproduced below. Please fix this error and try again.

Couldn't open file /home/osboxes/vagrant/pisces-ubuntu-trusty64

An error occurred while executing the action on the 'receiver' machine. Please handle this error then try again:

An error occurred while downloading the remote file. The error message, if any, is reproduced below. Please fix this error and try again.

Couldn't open file /home/osboxes/vagrant/pisces-ubuntu-trusty64

The first command worked fine. [root@osboxes osboxes]# vagrant box add pisces-ubuntu-trusty64 http://www.cs.princeton.edu/~mshahbaz/projects/pisces/vagrant/ubuntu-trusty64.box --force ==> box: Box file was not detected as metadata. Adding it directly... ==> box: Adding box 'pisces-ubuntu-trusty64' (v0) for provider: box: Downloading: http://www.cs.princeton.edu/~mshahbaz/projects/pisces/vagrant/ubuntu-trusty64.box ==> box: Successfully added box 'pisces-ubuntu-trusty64' (v0) for 'virtualbox'!

How do I resolve this? Nam

haazy commented 7 years ago

Hello, Please I am having issue with the provider, I have just installed virtualbox 5.0 on my xenial ubuntu but vagrant is complaining about this version.

ubuntu@haazy:~/vagrant$ vagrant up --provider=virtualbox The provider 'virtualbox' that was requested to back the machine 'switch' is reporting that it isn't usable on this system. The reason is shown below:

Vagrant has detected that you have a version of VirtualBox installed that is not supported by this version of Vagrant. Please install one of the supported versions listed below to use Vagrant:

4.0, 4.1, 4.2, 4.3, 5.0

A Vagrant update may also be available that adds support for the version you specified. Please check www.vagrantup.com/downloads.html to download the latest version.

Does anyone use ubuntu 16.04 and virtualbox 5.o with the latest vagrant?

Kindly help

haazy commented 7 years ago

ubuntu@haazy:~/vagrant$ vagrant up --provider=virtualbox Bringing machine 'switch' up with 'virtualbox' provider... Bringing machine 'generator' up with 'virtualbox' provider... Bringing machine 'receiver' up with 'virtualbox' provider... ==> switch: Importing base box 'pisces-ubuntu-trusty64'... Progress: 50%There was an error while executing VBoxManage, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below.

Command: ["import", "/home/ubuntu/.vagrant.d/boxes/pisces-ubuntu-trusty64/0/virtualbox/box.ovf", "--vsys", "0", "--vmname", "ubuntu64_1499453259088_24295", "--vsys", "0", "--unit", "10", "--disk", "/home/ubuntu/VirtualBox VMs/ubuntu64_1499453259088_24295/box-disk1.vmdk"]

Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% Interpreting /home/ubuntu/.vagrant.d/boxes/pisces-ubuntu-trusty64/0/virtualbox/box.ovf... OK. 0%...10%...20%...30%...40%...50%... Progress state: VBOX_E_FILE_ERROR VBoxManage: error: Appliance import failed VBoxManage: error: Could not create the imported medium '/home/ubuntu/VirtualBox VMs/ubuntu64_1499453259088_24295/box-disk1.vmdk'. VBoxManage: error: VMDK: cannot write allocated data block in '/home/ubuntu/VirtualBox VMs/ubuntu64_1499453259088_24295/box-disk1.vmdk' (VERR_DISK_FULL) VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component ApplianceWrap, interface IAppliance VBoxManage: error: Context: "RTEXITCODE handleImportAppliance(HandlerArg*)" at line 877 of file VBoxManageAppliance.cpp

haazy commented 7 years ago

Hello Nam,

Have you been able to resolve this issue?

I am having a similar issue too.

Kindly let me know what you did to get it resolved.

Thanks