-
Notifications
You must be signed in to change notification settings - Fork 6
error while loading up mds02 #4
Comments
Which versions are you using?
also make sure there no old |
Closing, unable to reproduce with
and no response from the user. |
There were old vms present. |
You can see that there are several instances of the same VM. Try to reproduce again, after cleaning up: From the
From the folder where Windows stores VMs:
This may be not sufficient to remove all information from virtualbox, |
I'm able vagrant up mds01 followed by reload and same for oss01 and centos7. But it fails to up mds02 and oss02 with following error -
vagrant-lustre-tutorial>vagrant up mds02
Bringing machine 'mds02' up with 'virtualbox' provider...
==> mds02: Checking if box 'puppetlabs/centos-6.6-64-nocm' is up to date...
==> mds02: Clearing any previously set forwarded ports...
==> mds02: Fixed port collision for 22 => 2222. Now on port 2202.
==> mds02: Clearing any previously set network interfaces...
==> mds02: Preparing network interfaces based on configuration...
mds02: Adapter 1: nat
mds02: Adapter 2: hostonly
==> mds02: Forwarding ports...
mds02: 22 (guest) => 2202 (host) (adapter 1)
==> mds02: Running 'pre-boot' VM customizations...
==> mds02: Booting VM...
There was an error while executing
VBoxManage
, a CLI used by Vagrantfor controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "dfb0e6b8-2aa0-4fdc-93d0-d1cf235dadf1", "--type", "headless
"]
Stderr: VBoxManage.exe: error: Locking of attached media failed. A possible reas
on is that one of the media is attached to a running VM
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), c
omponent SessionMachine, interface IMachine
The text was updated successfully, but these errors were encountered: