virtualbox.org

I'm trying to install Fuel7.0 cloud on VirtualBox 5.0.10.

My Env: Win 10 Pro, 64bit
VirtualBox: 5.0.10, 5.0.12r104815
Mirantis Fuel 7.0
Cygwin 64bit Terminal

$ ./launch_16GB.sh
Checking for 'free'... OK
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-7.0.iso
Checking if SSH client installed... OK
Checking if ipconfig or ifconfig installed... OK
Setup is done.
Creating host-only interface
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface VirtualBox Host-Only Ethernet Adapter was successfully created
Disabling DHCP server on interface: VirtualBox Host-Only Ethernet Adapter...
Configuring IP address 10.20.0.1 and network mask 255.255.255.0 on interface: VirtualBox Host-Only Ethernet Adapter...
+ VBoxManage hostonlyif ipconfig 'VirtualBox Host-Only Ethernet Adapter' --ip 10.20.0.1 --netmask 255.255.255.0
+ set +x
Verifying interface VirtualBox Host-Only Ethernet Adapter has IP 10.20.0.1 and mask 255.255.255.0 properly set.
New Net Mask 255.255.255.0 does not match the applied one 15.0.0.0
Looks like VirtualBox failed to apply settings for interface VirtualBox Host-Only Ethernet Adapter
Sometimes such error happens under Windows.
Please run launch.sh one more time.
If this error remains after several attempts, then something really went wrong.
Aborting.

Shouldn't this question be addressed to the Mirantis people?

I see the script was failing while updated the host-adaptor setting and I think it may the issue with VB. But I may be wrong also.

cloud-help wrote:But I may be wrong also.

Or the script could be wrong. That's why I proposed to ask the Mirantis people about their setup/script.

You are using a pre-written script to modify a standard VirtualBox setting. If it fails, I would think that the first port of call was the script writer.

This sort of problem often arises when the user is using a different version of the software from the writer-tester.