vagrant - network - La interfaz de red del host con el nombre dado no se pudo encontrar

vagrant public network

Question

Estoy ejecutando Windows 10, VirtualBox 5 y Vagrant 1.7.4 y tratando de ejecutar la plataforma platex.

Después de ejecutar vagrant up me dieron:

Bringing machine ''default'' up with ''virtualbox'' provider...
==> default: Clearing any previously set network interfaces...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["hostonlyif", "ipconfig", "VirtualBox Host-Only Ethernet Adapter #25", "--ip", "192.168.33.1", "--netmask", "255.255.255.0"]
Stderr: VBoxManage.exe: error: The host network interface with the given name could not be found
VBoxManage.exe: error: Details: code E_INVALIDARG (0x80070057), component HostWrap, interface IHost, callee IUnknown
VBoxManage.exe: error: Context: "FindHostNetworkInterfaceByName(Bstr(pszName).raw(), hif.asOutParam())" at line 204 of file VBoxManageHostonly.cpp

El archivo Vagrant:

Vagrant.require_version ">= 1.5.3"
VAGRANTFILE_API_VERSION = "2"
MEMORY = 4096
CPU_COUNT = 2
# map the name of the git branch that we use for a release
# to a name and a file path, which are used for retrieving
# a Vagrant box from the internet.
openedx_releases = {
"openedx/rc/aspen-2014-09-10" => {
:name => "aspen-fullstack-rc1", :file => "20141010-aspen-fullstack-rc1.box",
},
"aspen.1" => {
:name => "aspen-fullstack-1", :file => "20141028-aspen-fullstack-1.box",
},
"named-release/aspen" => {
:name => "aspen-fullstack-1", :file => "20141028-aspen-fullstack-1.box",
},
"named-release/birch.rc1" => {
:name => "birch-fullstack-rc1", :file => "20150204-birch-fullstack-rc1.box"
},
"named-release/birch.rc2" => {
:name => "birch-fullstack-rc2", :file => "20150211-birch-fullstack-rc2.box"
},
"named-release/birch.rc3" => {
:name => "birch-fullstack-rc3", :file => "20150213-birch-fullstack-rc3.box"
},
"named-release/birch" => {
:name => "birch-fullstack", :file => "20150224-birch-fullstack.box",
},
"named-release/birch.1" => {
:name => "birch-fullstack-1", :file => "birch-1-fullstack.box",
},
}
openedx_releases.default = {
:name => "kifli-fullstack", :file => "20140826-kifli-fullstack.box"
}
openedx_releases_vmware = {
"named-release/birch" => {
:name => "birch-fullstack-vmware", :file => "20150610-birch-fullstack-vmware.box",
},
}
openedx_releases_vmware.default = {
:name => "kifli-fullstack-vmware", :file => "20140829-kifli-fullstack-vmware.box",
}
rel = ENV[''OPENEDX_RELEASE'']
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
# Creates an edX fullstack VM from an official release
config.vm.box = openedx_releases[rel][:name]
config.vm.box_url = "http://files.edx.org/vagrant-images/#{openedx_releases[rel][:file]}"
config.vm.synced_folder ".", "/vagrant", disabled: true
config.ssh.insert_key = true
config.vm.network :private_network, ip: "192.168.33.10"
config.hostsupdater.aliases = ["preview.localhost"]
config.vm.provider :virtualbox do |vb|
vb.customize ["modifyvm", :id, "--memory", MEMORY.to_s]
vb.customize ["modifyvm", :id, "--cpus", CPU_COUNT.to_s]
# Allow DNS to work for Ubuntu 12.10 host
# http://askubuntu.com/questions/238040/how-do-i-fix-name-service-for-vagrant-client
vb.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
end
config.vm.provider :virtualbox do |v, override|
v.gui=true
end
["vmware_fusion", "vmware_workstation"].each do |vmware_provider|
config.vm.provider vmware_provider do |v, override|
override.vm.box = openedx_releases_vmware[rel][:name]
override.vm.box_url = "http://files.edx.org/vagrant-images/#{openedx_releases_vmware[rel][:file]}"
v.vmx["memsize"] = MEMORY.to_s
v.vmx["numvcpus"] = CPU_COUNT.to_s
end
end
end

Cuando comento esta línea, todo va bien.

config.vm.network :private_network, ip: "192.168.33.10"

Pero no puedo acceder a las páginas de LMS y CMS (Cuz i comentar esta línea, por supuesto)

Cualquier sugerencia será apreciada !

Answer 1

Finalmente ! ¡Lo resolví! Aquí está la solución:

1- VBox-Win10-fix-14040.exe como administrador (ver esta discusión )

2- Ejecutar el VirtualBox.exe como Admin + Compatibilidad con Windows 7

3- Y Vagrant up :)

Eso es !

Answer 2

Solución simple: elimine el Adaptador Ethernet del host solo creado (predeterminado) de las Preferencias de VirtualBox y ejecute sh launch.sh (si recibió un error al instalar el paquete Mirantis Openstack).

PD: No veo una razón por la que no debería funcionar para Vagrant también.

Answer 3

para Windows 7 x86, tal vez su caja virtual se actualice a la última versión. Intente volver a la versión 4. Puede elegir el lanzamiento en marzo o septiembre de 2014