← Back to team overview

fuel-dev team mailing list archive

Re: VBoxManage: error: The virtual machine 'fuel-master' has terminated unexpectedly

 

Greetings Gandhi,

Please do the following in order to finish setup and run Virtualbox scripts
correctly.

1. Do not run Virtualbox or related script under root or any superuser
account. It may not work everywhere in case of Virtualbox.
Instead, please use user account.
You must add this user account to "vboxusers" security group, which is
automatically created in scope of Virtualbox installation.
Please run the following command (change <your user name> to the user name
you want to add to vboxusers group:
sudo useradd -G vboxusers <your user name>


2. As Roman mentioned, in case your target server where you run Virtualbox
has no X running - you have to use headless mode to start VMs.
Attached is updated Virtualbox scripts version, which automatically
detects, should it start VMs in headless mode or no.
Please try using the attached version.

Kind regards,
Miroslav



On Tue, Apr 29, 2014 at 2:14 PM, Roman Alekseenkov <
ralekseenkov@xxxxxxxxxxxx> wrote:

> You may not have X11 installed on the machine. Try to modify the scripts
> to use the headless option "VBoxManage startvm ... --type headless"
>
> Roman
>
>
> On Tue, Apr 29, 2014 at 2:20 AM, Gandhirajan Mariappan (CW) <
> gmariapp@xxxxxxxxxxx> wrote:
>
>> Hi,
>>
>>
>>
>> While executing launch.sh, the process stopped with below error message
>> (highlighted).
>>
>> Kindly let us know how to proceed further. We waited for more than 15
>> minutes but no response is shown in terminal.
>>
>>
>>
>> *Snap :*
>>
>> root@U12:~/Downloads/virtualbox# ./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
>>
>> Checking if SSH client installed...
>>
>> OK
>>
>> Checking if ipconfig or ifconfig installed...
>>
>> OK
>>
>> Deleting host-only interface: vboxnet0...
>>
>> 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.
>>
>> Setup is done.
>>
>>
>>
>> Virtual machine 'fuel-master' is created and registered.
>>
>> UUID: c86a6342-9930-44fb-9677-cce46dbb32f9
>>
>> Settings file: '/root/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: 3a72f4e9-0473-4c4c-bd61-9349c53a929c
>>
>>
>>
>> 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...
>>
>>
>>
>> Waiting for VM "fuel-master" to power on...
>>
>> VBoxManage: error: The virtual machine 'fuel-master' has terminated
>> unexpectedly during startup with exit code 1
>>
>> VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component
>> Machine, interface IMachine
>>
>> Waiting for product VM to install. Please do NOT abort the script...
>>
>>
>>
>>
>>
>> Thanks and Regards,
>>
>> Gandhi Rajan
>>
>> --
>> 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
>>
>>
>
> --
> 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
>
>


-- 

*Kind Regards*

*Miroslav Anashkin**L2 support engineer**,*
*Mirantis Inc.*
*+7(495)640-4944 (office receptionist)*
*+1(650)587-5200 (office receptionist, call from US)*
*35b, Bld. 3, Vorontsovskaya St.*
*Moscow**, Russia, 109147.*

www.mirantis.com

manashkin@xxxxxxxxxxxx

Attachment: virtualbox_scripts_updated.zip
Description: Zip archive


References