I'm trying to create mini DCOS cluster in Mac OS.
My minidcos version is -
$ minidcos --version
minidcos, version 2019.02.17.1
When I run the below command to create the cluster I get the error -
$ minidcos vagrant create ./dcos_generate_config.sh --agents 0
Bringing machine 'dcos-e2e-f2c21a1a-a220-4a33-a528-493a11f16440-master-0' up with 'virtualbox' provider...
Bringing machine 'dcos-e2e-f2c21a1a-a220-4a33-a528-493a11f16440-public-agent-0' up with 'virtualbox' provider...
==> dcos-e2e-f2c21a1a-a220-4a33-a528-493a11f16440-master-0: Importing base box 'mesosphere/dcos-centos-virtualbox'...
Progress: 90%There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["import", "/Users/rajkumar.natarajan/.vagrant.d/boxes/mesosphere-VAGRANTSLASH-dcos-centos-virtualbox/0.9.2/virtualbox/box.ovf", "--vsys", "0", "--vmname", "packer-virtualbox-iso-1500059987_1551037690830_88506", "--vsys", "0", "--unit", "8", "--disk", "/Users/rajkumar.natarajan/VirtualBox VMs/packer-virtualbox-iso-1500059987_1551037690830_88506/packer-virtualbox-iso-1500059987-disk001.vmdk"]
Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /Users/rajkumar.natarajan/.vagrant.d/boxes/mesosphere-VAGRANTSLASH-dcos-centos-virtualbox/0.9.2/virtualbox/box.ovf...
OK.
0%...
Progress state: VBOX_E_OBJECT_NOT_FOUND
VBoxManage: error: Appliance import failed
VBoxManage: error: Error opening '/Users/rajkumar.natarajan/.vagrant.d/boxes/mesosphere-VAGRANTSLASH-dcos-centos-virtualbox/0.9.2/virtualbox/packer-virtualbox-iso-1500059987-disk001.vmdk' for reading (VERR_FILE_NOT_FOUND)
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component ApplianceWrap, interface IAppliance
VBoxManage: error: Context: "RTEXITCODE handleImportAppliance(HandlerArg *)" at line 886 of file VBoxManageAppliance.cpp
Error creating cluster.
Full error:
Command '['/usr/local/bin/vagrant', 'up']' returned non-zero exit status 1.
Try "minidcos vagrant doctor" for troubleshooting help.
I'm not sure what is the root cause of this error?
Related
there! I tried to install microk8s version 2.3.1, having VirtualBox 7.0.6 already installed.
Making a long story short, I’m facing the following problem:
C:\Users\lucas>microk8s status --wait-ready
MicroK8s is not installed. Please run `microk8s install`.
C:\Users\lucas>microk8s install
[2023-02-10T16:05:20.013] [error] [microk8s-vm] Could not unregister VM: VBoxManage.exe: error: Cannot unregister the machine 'microk8s-vm' while it is locked
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee IUnknown
VBoxManage.exe: error: Context: "Unregister(fDeleteAll ? CleanupMode_DetachAllReturnHardDisksAndVMRemovable :CleanupMode_DetachAllReturnHardDisksOnly, ComSafeArrayAsOutParam(aMedia))" at line 236 of file VBoxManageMisc.cpp
launch failed: Could not start VM: VBoxManage.exe: error: UUID {9aa00452-a0c7-46fd-934d-039c9ddaac76} of the medium 'C:\ProgramData\Multipass\data\virtualbox\vault\instances\microk8s-vm\ubuntu-18.04-server-cloudimg-amd64.vdi' does not match the value {d1773776-824f-4773-8173-a89394a8a2a6} stored in the media registry ('C:\windows\system32\config\systemprofile\.VirtualBox\VirtualBox.xml')
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MediumWrap, interface IMedium
Waiting for VM "microk8s-vm" to power on...
And then this message repeats every ~5 seconds.
The list of virtual machines on VirtualBox is empty.
I’m pretty stuck on it. Anybody has an idea on how to solve it?
Thanks!
I'm trying to learn Vagrant but facing an issue at the beginning of my way.. I was googling for a while but didn't find useful answer.
Setup details: Windows 10 Vagrant 2.1.5 VirtualBox 5.2.18 r124319
Problem description:
While running "vagrant up" command I get following error:
PS C:\Users\Michał\Desktop\desktop\vagrant_test> vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==>
default: Importing base box 'geerlingguy/centos7'... There was an
error while executing VBoxManage, a CLI used by Vagrant for
controlling VirtualBox. The command and stderr is shown below.
Command: ["import", "\?\C:\HashiCorp;\boxes\geerlingguy-VAGRANTSLASH-centos7\1.2.10\virtualbox
\box.ovf", "--vsys", "0", "--vmname",
"packer-centos-7-x86_64_1539008587672_41094", "--vsys", "0", "--
unit", "8", "--disk", "C:\Users\Micha\u2502\VirtualBox
VMs\packer-centos-7-x86_64_1539008587672_41094
\packer-centos-7-x86_64-disk001.vmdk"]
Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting
\?\C:\HashiCorp;\boxes\geerlingguy-VAGRANTSLASH-centos7\1.2.10\virtualbox\box.ovf...
OK. 0%... Progress state: VBOX_E_IPRT_ERROR VBoxManage.exe: error:
Appliance import failed VBoxManage.exe: error: Could not create the
directory 'C:\Users\MichaÔöé\VirtualBox
VMs\packer-centos->7-x86_64_1539008587672_41094' (VERR_ACCESS_DENIED)
VBoxManage.exe: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005),
component ApplianceWrap, interface IAppliance VBoxManage.exe: error:
Context: "enum RTEXITCODE __cdecl handleImportAppliance(struct
HandlerArg *)" at line 886 of file VBoxManageAppliance.cpp
For some reason VBoxManage.exe tool is not able to access the directory where my VirtualBox VMs are stored.
VBoxManage.exe: error: Could not create the directory
'C:\Users\MichaÔöé\VirtualBox
VMs\packer-centos-7-x86_64_1539008587672_41094' (VERR_ACCESS_DENIED)
Username contains one Polish letter "ł" that's why we see in the path:
C:\Users\MichaÔöé\VirtualBox VMs
But I don't think it is a problem.
This is default installation so I would expect it to be running.
BR
I found the answer, running PowerShell console as administrator resolved the issue.
try to download Vagrant box on my mac system and this is the message I get.
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'bahmni-team/bahmni' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Loading metadata for box 'bahmni-team/bahmni'
default: URL: https://atlas.hashicorp.com/bahmni-team/bahmni
==> default: Adding box 'bahmni-team/bahmni' (v0.80) for provider: virtualbox
default: Downloading: https://atlas.hashicorp.com/bahmni-team/boxes/bahmni/versions/0.80/providers/virtualbox.box
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
transfer closed with 963850334 bytes remaining to read
how do I resolve this?
After Successful Installing Vagrant box, Got this error
default: Importing base box 'bahmni-team/bahmni'...
Progress: 10%There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["import", "/Users/Paul/.vagrant.d/boxes/bahmni-team-VAGRANTSLASH-bahmni/0.80/virtualbox/box.ovf", "--vsys", "0", "--vmname", "packer-virtualbox-iso-1459089960_1463772163009_23494", "--vsys", "0", "--unit", "7", "--disk", "/Users/Paul/VirtualBox VMs/packer-virtualbox-iso-1459089960_1463772163009_23494/packer-virtualbox-iso-1459089960-disk1.vmdk"]
Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /Users/Paul/.vagrant.d/boxes/bahmni-team-VAGRANTSLASH-bahmni/0.80/virtualbox/box.ovf...
OK.
0%...10%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance import failed
VBoxManage: error: Could not create the imported medium '/Users/Paul/VirtualBox VMs/packer-virtualbox-iso-1459089960_1463772163009_23494/packer-virtualbox-iso-1459089960-disk1.vmdk'.
VBoxManage: error: VMDK: cannot write allocated data block in '/Users/Paul/VirtualBox VMs/packer-virtualbox-iso-1459089960_1463772163009_23494/packer-virtualbox-iso-1459089960-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
I think the error "VERR_DISK_FULL" is the error you should focus at. Your disk might have been full. So, solution would be to free some space on the disk and try the command again.
Vagrant is internally using curl and there are issues with curl.
You can try wget on the URL as it usually works better than curl
wget https://atlas.hashicorp.com/bahmni-team/boxes/bahmni/versions/0.80/providers/virtualbox.box
once you have the box file you still need to add to vagrant (vagrant box add bahmni-team/bahmni <path to box file>)
I am getting the below error when i try to run "vagrant up" command.
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'precise32'...
Progress: 30%There was an error while executing VBoxManage, a CLI used by Vagr
ant
for controlling VirtualBox. The command and stderr is shown below.
Command:
["import", "C:/Users/username/.vagrant.d/boxes/precise32/0/virtualbox/b
ox.ovf", "--vsys", "0", "--vmname", "precise32_1417450998781_63238", "--vsys", "
0", "--unit", "9", "--disk", "X:\\VirtualBox VMs\\precise32_1417450998781_63238\
\box-disk1.vmdk"]
Stderr:
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting C:\Users\username\.vagrant.d\boxes\precise32\0\virtualbox\box.ovf..
.
OK.
0%...10%...20%...30%...
Progress state:
VBOX_E_FILE_ERROR
VBoxManage.exe: error: Appliance import failed
VBoxManage.exe: error: Could not create the imported medium 'X:\VirtualBox VMs\p
recise32_1417450998781_63238\box-disk1.vmdk'.
VBoxManage.exe: error: VMDK: cannot write allocated data block in 'X:\VirtualBox
VMs\precise32_1417450998781_63238/box-disk1.vmdk' (VERR_DISK_FULL)
VBoxManage.exe: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component A
ppliance, interface IAppliance
VBoxManage.exe: error: Context: "int __cdecl handleImportAppliance(struct Handle
rArg *)" at line 779 of file VBoxManageAppliance.cpp
I am not using an 'X' drive and I have already set the "VAGRANT_HOME" variable to the home directory in the environment variables, i.e, VAGRANT_HOME and its value C:\Users\username.vagrant.d
I already have the ".vagrant" directory and other dirs inside it.
Can anyone please tell me why I am still getting the above error when i run "vagrant up" command and any solution for it.
Thanks
The error VERR_DISK_FULL seems to tell that your disk is full.
VBoxManage.exe: error: VMDK: cannot write allocated data block in 'X:\VirtualBox
VMs\precise32_1417450998781_63238/box-disk1.vmdk' (VERR_DISK_FULL)
Try freeing some space on your C:/ drive. I don't know the minimum but I think you have to have more then 1 gb free.
I had the same error and I found that the .vmdk file was missing inside of the box directory within .vagrant.d
Simply copying the file there solved it
It's laravel/Homestead box in a debian machine by the way.
I am using Vagrant on Windows 7.
After I run vagrant up,I showed me:
Progress state: VBOX_E_FILE_ERROR
VBoxManage.exe: error: Appliance import failed
VBoxManage.exe: error: Could not create the clone medium 'L:\VirtualBox VMs\ubun
tu-cloudimg-trusty-vagrant-amd64\box-disk1.vmdk'.
VBoxManage.exe: error: VMDK: could not create new grain directory in 'L:\Virtual
Box VMs\ubuntu-cloudimg-trusty-vagrant-amd64/box-disk1.vmdk' (VERR_DISK_FULL).
VBoxManage.exe: error: VMDK: error writing descriptor in 'L:\VirtualBox VMs\ubun
tu-cloudimg-trusty-vagrant-amd64\box-disk1.vmdk' (VERR_DISK_FULL)
VBoxManage.exe: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component A
ppliance, interface IAppliance
VBoxManage.exe: error: Context: "int __cdecl handleImportAppliance(struct Handle
rArg *)" at line 779 of file VBoxManageAppliance.cpp
Maybe the reason is that my L disk is full.So how can I set a different disk?
It certainly looks like some drive issue, maybe disk space, maybe user permissions.
In your case the error comes from VBoxManage, so the error happens when Vagrant is importing its box into VirtualBox.
In order to change the location of VirtualBox's VMs you need to set it in VirtualBox properties ('Default Machine Folder').
For more info check the docs
You need set VAGRANT_HOME. The property "machinefolder" in VirtualBox has to be set through "VBoxManage setproperty machinefolder "