← Back to team overview

fuel-dev team mailing list archive

Re: Problems installing Fuel on VirtualBox

 

You're missing the Fuel 5.0 ISO in the virtualbox/iso directory. you
should copy it there

On Tue, Jun 17, 2014 at 1:47 PM, Meg McRoberts <mmcroberts@xxxxxxxxxxxx> wrote:
> Does anyone know what this error message means?
>
>  ./launch.sh
> Checking for 'expect'... OK
> If you run this script under Cygwin, you may have to add path to VirtualBox
> directory to your PATH.
> Usually it is enough to run "export PATH=$PATH:"/cygdrive/c/Program
> Files/Oracle/VirtualBox"
> Checking for "VBoxManage"...  OK
> Checking for VirtualBox Extension Pack... OK
> Checking for Mirantis OpenStack ISO image... OK
> Going to use Mirantis OpenStack ISO file iso/MirantisOpenStack-5.0.iso
> Checking if SSH client installed...
> OK
> Checking if ipconfig or ifconfig installed...
> OK
> Setup is done.
> Found existing VM: fuel-master. Deleting it...
> Deleting existing virtual machine fuel-master...
> 0%...10%...20%...30%...
> Progress state: VBOX_E_FILE_ERROR
> VBoxManage: error: Machine delete failed
> VBoxManage: error: Could not delete the medium storage unit
> '/home/megm/VirtualBox VMs/fuel-master/fuel-master_0.vdi'.
> VBoxManage: error: VD: error VERR_FILE_NOT_FOUND opening image file
> '/home/megm/VirtualBox VMs/fuel-master/fuel-master_0.vdi'
> (VERR_FILE_NOT_FOUND)
> VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component
> Medium, interface IMedium
> VBoxManage: error: Context: "int handleUnregisterVM(HandlerArg*)" at line
> 166 of file VBoxManageMisc.cpp
> Deleting host-only interface: vboxnet1...
> 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
> Deleting host-only interface: vboxnet0...
> 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
> Deleting host-only interface: vboxnet2...
> 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
> Creating host-only interface (name ip netmask): vboxnet0  10.20.0.1
> 255.255.255.0
> 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
> Interface 'vboxnet0' was successfully created
> Disabling DHCP server on interface: vboxnet0...
> + echo 'Configuring IP address 10.20.0.1 and network mask 255.255.255.0 on
> interface: vboxnet0...'
> Configuring IP address 10.20.0.1 and network mask 255.255.255.0 on
> interface: vboxnet0...
> + VBoxManage hostonlyif ipconfig vboxnet0 --ip 10.20.0.1 --netmask
> 255.255.255.0
> + set +x
> Verifying interface vboxnet0 has IP 10.20.0.1 and mask 255.255.255.0
> properly set.
> OK.
> Creating host-only interface (name ip netmask): vboxnet1  172.16.0.1
> 255.255.255.0
> 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
> Interface 'vboxnet1' was successfully created
> Disabling DHCP server on interface: vboxnet1...
> + echo 'Configuring IP address 172.16.0.1 and network mask 255.255.255.0 on
> interface: vboxnet1...'
> Configuring IP address 172.16.0.1 and network mask 255.255.255.0 on
> interface: vboxnet1...
> + VBoxManage hostonlyif ipconfig vboxnet1 --ip 172.16.0.1 --netmask
> 255.255.255.0
> + set +x
> Verifying interface vboxnet1 has IP 172.16.0.1 and mask 255.255.255.0
> properly set.
> OK.
> Creating host-only interface (name ip netmask): vboxnet2  172.16.1.1
> 255.255.255.0
> 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
> Interface 'vboxnet2' was successfully created
> Disabling DHCP server on interface: vboxnet2...
> + echo 'Configuring IP address 172.16.1.1 and network mask 255.255.255.0 on
> interface: vboxnet2...'
> Configuring IP address 172.16.1.1 and network mask 255.255.255.0 on
> interface: vboxnet2...
> + VBoxManage hostonlyif ipconfig vboxnet2 --ip 172.16.1.1 --netmask
> 255.255.255.0
> + set +x
> Verifying interface vboxnet2 has IP 172.16.1.1 and mask 255.255.255.0
> properly set.
> OK.
> Virtual machine 'fuel-master' is created and registered.
> UUID: 2c084f32-29c5-4b03-b2e5-1f07703fd902
> Settings file: '/home/megm/VirtualBox VMs/fuel-master/fuel-master.vbox'
> Adding hostonly adapter to fuel-master and bridging with host NIC
> vboxnet0...
> Adding disk to fuel-master, with size 65535 Mb...
> 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
> Disk image created. UUID: 2170ba06-f421-4a26-97c6-dbb00a658987
>
> Adding hostonly adapter to fuel-master and bridging with host NIC
> vboxnet1...
> Adding NAT adapter to fuel-master for outbound network access through the
> host system...
> VBoxManage: error: The medium
> '/home/megm/vbox-50/virtualbox/iso/MirantisOpenStack-5.0.iso' can't be used
> as the requested device type
> VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component
> Medium, interface IMedium, callee nsISupports
> VBoxManage: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(),
> enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at
> line 178 of file VBoxManageDisk.cpp
> VBoxManage: error: Invalid UUID or filename "iso/MirantisOpenStack-5.0.iso"
>
> Waiting for VM "fuel-master" to power on...
> VM "fuel-master" has been successfully started.
> Waiting for product VM to install. Please do NOT abort the script...
>
>
>
> --
> Mailing list: https://launchpad.net/~fuel-dev
> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help   : https://help.launchpad.net/ListHelp
>


Follow ups

References