[vbox] MOS 6.1 MU1 launch.sh fails network creation on Windows 10, vbox 4.3.12 or higher
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Maksim Malchuk |
Bug Description
$ bash launch.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:
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/MirantisOpe
Checking if SSH client installed... OK
Checking if ipconfig or ifconfig installed... OK
Setup is done.
Creating host-only interface
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "int __cdecl handleCreate(struct HandlerArg *,int,int *)" at line 66 of file VBoxManageHosto
Interface was successfully created
Disabling DHCP server on interface: ...
Configuring IP address 10.20.0.1 and network mask 255.255.255.0 on interface: ...
+ VBoxManage hostonlyif ipconfig '' --ip 10.20.0.1 --netmask 255.255.255.0
VBoxManage.exe: error: The host network interface with the given name could not be found
VBoxManage.exe: error: Details: code E_INVALIDARG (0x80070057), component Host, interface IHost, callee IUnknown
VBoxManage.exe: error: Context: "FindHostNetwor
VBoxManage.exe: error: Could not find interface ''
+ set +x
Verifying interface has IP 10.20.0.1 and mask 255.255.255.0 properly set.
New IP address 10.20.0.1 does not match the applied one
Looks like VirtualBox failed to apply settings for interface
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.
-------
Second, third and fourth attempt:
$ bash launch.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:
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/MirantisOpe
Checking if SSH client installed... OK
Checking if ipconfig or ifconfig installed... OK
Setup is done.
Creating host-only interface
0%...10%
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.
tags: | added: area-library |
Changed in fuel: | |
status: | Triaged → In Progress |
tags: | added: team-bugfix |
Changed in fuel: | |
assignee: | Serhii Ovsianikov (sovsianikov) → Maksim Malchuk (mmalchuk) |
Bruce, what were Virtual Box and Extension pack versions you ran under Windows 10 and got this error?
BTW, it is possible for Virtual Box to fail network creation at first run - it happens since Virtualbox is installed under administrative account but scripts should be run without administrative privileges and Windows should ask for administrative action to confirm.