Ошибка nonexistent host networking interface - ErrorsMaster.ru - большая энциклопедия ошибок и их решений

Виртуалка подключена к сетевой карте компьютера через сетевой мост. Сохранил состояние включенной виртуалки, отправил основной компьютер в перезагрузку для установки обновлений. После перезагрузки при попытке продолжить работу виртуалки ничего не выходит – выскакивает ошибка «Nonexistent host networking interface… (VERR_INTERNAL_ERROR)»

Для профилактики делаем снимок текущего состояния
Сбрасываем виртуальную машину
Становятся доступными её свойства – заходим в её сетевые адаптеры, отключаем сетевой мост
Нажимаем старт

5. Машина успешно запускается, теперь включаем сетевой мост обратно, всё заработает как прежде

Источник

Содержание

	Введение
	your current centos software installation requires of available space
	(rc=-1908) Kernel driver not installed
	This system is currently not set up to build kernel modules
	(rc=-1912) The VirtualBox kernel modules do not match this version of VirtualBox
	Nonexistent host networking interface
	Cannot unregister the machine
	Missing Dependencies Python Core / win32api

Возможные проблемы

Если что-то не получилось, особенно в самом начале, например возникла ошибка 1908

rc=-1908

wwww.andreyolegovich.ru

Советую подумать:

Всё ли сделано по инструкции с сайта debian.org
Обновлено ли у вас ядро хотя бы до той версии, что у меня.

Если все так — попробуйте сделать то, что советует virtualbox

/etc/init.d/vboxdrv setup

Однако, этого пути может и не существовать.

Есть форумы, где обсуждалась эта проблема — поyahooярьте, пояндексите. Правда, когда
у меня на ноутбуке возникла такая проблема, ничего
оттуда не помогло. Но у меня было старое ядро!

your current centos software installation requires of available space

При попытке установить новую вирутальную ОС может появиться
следующая ошибка

virtualbox your current centos software installation requires of available space including for software and for swap space

Нажмите Reclaim Space

reclaim space

ww.andreyolegovich.ru

Создание host-only адаптера в VirtualBox изображение с сайта www.andreyolegovich.ru

reclaim space

ww.andreyolegovich.ru

Kernel driver not installed (rc=-1908)

Довольно затруднительная ситуация когда при выполнении

virtualbox

Получаете предупреждение

WARNING: The character device /dev/vboxdrv does not exist.
Please install the virtualbox-dkms package and the appropriate
headers, most likely linux-headers-generic.

You will not be able to start VMs until this problem is fixed.

А в UI следующая ошибка

rc=-1908

ww.andreyolegovich.ru

Попытки установить всё перечисленное выше и сделать apt upgrade могут не принести результата

sudo apt install virtualbox-dkms

Reading package lists… Done
Building dependency tree
Reading state information… Done
The following packages were automatically installed and are no longer required:
libfprint-2-tod1 libllvm10 libllvm10:i386 linux-headers-5.4.0-59
linux-headers-5.4.0-59-generic linux-headers-5.6.0-1020-oem
linux-headers-5.6.0-1036-oem linux-headers-5.6.0-1039-oem
linux-image-5.4.0-59-generic linux-image-5.6.0-1020-oem
linux-image-5.6.0-1036-oem linux-image-5.6.0-1039-oem
linux-modules-5.4.0-59-generic linux-modules-5.6.0-1020-oem
linux-modules-5.6.0-1036-oem linux-modules-5.6.0-1039-oem
linux-modules-extra-5.4.0-59-generic
linux-modules-nvidia-450-5.4.0-59-generic linux-oem-5.6-headers-5.6.0-1020
linux-oem-5.6-headers-5.6.0-1036 linux-oem-5.6-headers-5.6.0-1039
Use ‘sudo apt autoremove’ to remove them.
The following additional packages will be installed:
linux-headers-5.4.0-60 linux-headers-5.4.0-60-generic
The following NEW packages will be installed:
linux-headers-5.4.0-60 linux-headers-5.4.0-60-generic linux-headers-generic
0 upgraded, 3 newly installed, 0 to remove and 1 not upgraded.
Need to get 12.2 MB of archives.
After this operation, 85.4 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://fi.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-headers-5.4.0-60 all 5.4.0-60.67 [11.0 MB]
Get:2 http://fi.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-headers-5.4.0-60-generic amd64 5.4.0-60.67 [1,232 kB]
Get:3 http://fi.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-headers-generic amd64 5.4.0.60.63 [2,468 B]
Fetched 12.2 MB in 2s (6,333 kB/s)
Selecting previously unselected package linux-headers-5.4.0-60.
(Reading database … 382700 files and directories currently installed.)
Preparing to unpack …/linux-headers-5.4.0-60_5.4.0-60.67_all.deb …
Progress: [ 8%] [#####………………………………………………………..]
Selecting previously unselected package linux-headers-5.4.0-60-generic……………………..]
Preparing to unpack …/linux-headers-5.4.0-60-generic_5.4.0-60.67_amd64.deb …
Unpacking linux-headers-5.4.0-60-generic (5.4.0-60.67) …
Selecting previously unselected package linux-headers-generic.
Preparing to unpack …/linux-headers-generic_5.4.0.60.63_amd64.deb …
Unpacking linux-headers-generic (5.4.0.60.63) …
Setting up linux-headers-5.4.0-60 (5.4.0-60.67) …
Setting up linux-headers-5.4.0-60-generic (5.4.0-60.67) …
/etc/kernel/header_postinst.d/dkms:
* dkms: running auto installation service for kernel 5.4.0-60-generic

Kernel preparation unnecessary for this kernel. Skipping…
applying patch disable_fstack-clash-protection_fcf-protection.patch…patching file Kbuild
Hunk #1 succeeded at 84 (offset 13 lines).

Building module:
cleaning build area…
unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 ‘make’ -j8 NV_EXCLUDE_BUI
LD_MODULES=» KERNEL_UNAME=5.4.0-60-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/mod
Progress: [ 69%] [#######################################………..#####…………………….]
Signing module:
— /var/lib/dkms/nvidia/450.80.02/5.4.0-60-generic/x86_64/module/nvidia-uvm.ko
— /var/lib/dkms/nvidia/450.80.02/5.4.0-60-generic/x86_64/module/nvidia.ko
— /var/lib/dkms/nvidia/450.80.02/5.4.0-60-generic/x86_64/module/nvidia-modeset.ko
— /var/lib/dkms/nvidia/450.80.02/5.4.0-60-generic/x86_64/module/nvidia-drm.ko
Nothing to do.
cleaning build area…

DKMS: build completed.

nvidia.ko:
Running module version sanity check.
— Original module
— No original module exists within this kernel
— Installation
— Installing to /lib/modules/5.4.0-60-generic/updates/dkms/

nvidia-modeset.ko:
Running module version sanity check.
— Original module
— No original module exists within this kernel
— Installation
— Installing to /lib/modules/5.4.0-60-generic/updates/dkms/

nvidia-drm.ko:
Running module version sanity check.
— Original module
— No original module exists within this kernel
— Installation
— Installing to /lib/modules/5.4.0-60-generic/updates/dkms/

nvidia-uvm.ko:
Running module version sanity check.
— Original module
— No original module exists within this kernel
— Installation
— Installing to /lib/modules/5.4.0-60-generic/updates/dkms/

depmod…

DKMS: install completed.

Kernel preparation unnecessary for this kernel. Skipping…

Building module:
cleaning build area…
make -j8 KERNELRELEASE=5.4.0-60-generic -C /lib/modules/5.4.0-60-generic/build M=/var/lib/dkms/virtual
box/6.1.10/build……
Signing module:
— /var/lib/dkms/virtualbox/6.1.10/5.4.0-60-generic/x86_64/module/vboxdrv.ko
— /var/lib/dkms/virtualbox/6.1.10/5.4.0-60-generic/x86_64/module/vboxnetadp.ko
— /var/lib/dkms/virtualbox/6.1.10/5.4.0-60-generic/x86_64/module/vboxnetflt.ko
Nothing to do.
cleaning build area…

DKMS: build completed.

vboxdrv.ko:
Running module version sanity check.
— Original module
— No original module exists within this kernel
— Installation
— Installing to /lib/modules/5.4.0-60-generic/updates/dkms/

vboxnetadp.ko:
Running module version sanity check.
— Original module
— No original module exists within this kernel
— Installation
— Installing to /lib/modules/5.4.0-60-generic/updates/dkms/

vboxnetflt.ko:
Running module version sanity check.
— Original module
— No original module exists within this kernel
— Installation
— Installing to /lib/modules/5.4.0-60-generic/updates/dkms/

depmod…

DKMS: install completed.
…done.
Setting up linux-headers-generic (5.4.0.60.63) …

sudo modprobe vboxdrv

modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/5.8.0-34-generic

sudo dpkg-reconfigure virtualbox-dkms

——— Uninstall Beginning ———
Module: virtualbox
Version: 6.1.10
Kernel: 5.4.0-60-generic (x86_64)
————————————-

Status: Before uninstall, this module version was ACTIVE on this kernel.

vboxdrv.ko:
— Uninstallation
— Deleting from: /lib/modules/5.4.0-60-generic/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

vboxnetadp.ko:
— Uninstallation
— Deleting from: /lib/modules/5.4.0-60-generic/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

vboxnetflt.ko:
— Uninstallation
— Deleting from: /lib/modules/5.4.0-60-generic/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

depmod…

DKMS: uninstall completed.

——— Uninstall Beginning ———
Module: virtualbox
Version: 6.1.10
Kernel: 5.6.0-1036-oem (x86_64)
————————————-

Status: Before uninstall, this module version was ACTIVE on this kernel.

vboxdrv.ko:
— Uninstallation
— Deleting from: /lib/modules/5.6.0-1036-oem/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

vboxnetadp.ko:
— Uninstallation
— Deleting from: /lib/modules/5.6.0-1036-oem/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

vboxnetflt.ko:
— Uninstallation
— Deleting from: /lib/modules/5.6.0-1036-oem/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

depmod…

DKMS: uninstall completed.

——— Uninstall Beginning ———
Module: virtualbox
Version: 6.1.10
Kernel: 5.6.0-1039-oem (x86_64)
————————————-

Status: Before uninstall, this module version was ACTIVE on this kernel.

vboxdrv.ko:
— Uninstallation
— Deleting from: /lib/modules/5.6.0-1039-oem/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

vboxnetadp.ko:
— Uninstallation
— Deleting from: /lib/modules/5.6.0-1039-oem/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

vboxnetflt.ko:
— Uninstallation
— Deleting from: /lib/modules/5.6.0-1039-oem/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

depmod…

DKMS: uninstall completed.

——— Uninstall Beginning ———
Module: virtualbox
Version: 6.1.10
Kernel: 5.6.0-1042-oem (x86_64)
————————————-

Status: Before uninstall, this module version was ACTIVE on this kernel.

vboxdrv.ko:
— Uninstallation
— Deleting from: /lib/modules/5.6.0-1042-oem/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

vboxnetadp.ko:
— Uninstallation
— Deleting from: /lib/modules/5.6.0-1042-oem/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

vboxnetflt.ko:
— Uninstallation
— Deleting from: /lib/modules/5.6.0-1042-oem/updates/dkms/
— Original module
— No original module was found for this module on this kernel.
— Use the dkms install command to reinstall any previous module version.

depmod…

DKMS: uninstall completed.

——————————
Deleting module version: 6.1.10
completely from the DKMS tree.
——————————
Done.
Loading new virtualbox-6.1.10 DKMS files…
Building for 5.8.0-34-generic 5.8.0-36-generic
Building initial module for 5.8.0-34-generic
ERROR: Cannot create report: [Errno 17] File exists: ‘/var/crash/virtualbox-dkms.0.crash’
Error! Bad return status for module build on kernel: 5.8.0-34-generic (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.10/build/make.log for more information.

sudo dpkg-reconfigure virtualbox

Job for vboxweb.service failed because the service did not take the steps required by its unit configuration.
See «systemctl status vboxweb.service» and «journalctl -xe» for details.
Job for virtualbox.service failed because the control process exited with error code.
See «systemctl status virtualbox.service» and «journalctl -xe» for details.
invoke-rc.d: initscript virtualbox, action «restart» failed.
● virtualbox.service — LSB: VirtualBox Linux kernel module
Loaded: loaded (/etc/init.d/virtualbox; generated)
Active: failed (Result: exit-code) since Fri 2021-01-08 15:31:23 EET; 4ms ago
Docs: man:systemd-sysv-generator(8)
Process: 66734 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE)

Jan 08 15:31:23 LL-USER2 systemd[1]: Starting LSB: VirtualBox Linux kernel module…
Jan 08 15:31:23 LL-USER2 virtualbox[66734]: * Loading VirtualBox kernel modules…
Jan 08 15:31:23 LL-USER2 virtualbox[66734]: * No suitable module for running kernel found
Jan 08 15:31:23 LL-USER2 virtualbox[66734]: …fail!
Jan 08 15:31:23 LL-USER2 systemd[1]: virtualbox.service: Control process exited, code=exited, status=1/FAILURE
Jan 08 15:31:23 LL-USER2 systemd[1]: virtualbox.service: Failed with result ‘exit-code’.
Jan 08 15:31:23 LL-USER2 systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.

Содержание man SYSTEMD-SYSV-GENERATOR (8)

SYSTEMD-SYSV-GENERATOR (8)
systemd-sysv-generator S
NAME
systemd-sysv-generator — Unit generator for SysV init scripts
SYNOPSIS
/lib/systemd/system-generators/systemd-sysv-generator
DESCRIPTION
systemd-sysv-generator is a generator that creates wrapper .service
units for SysV init[1] scripts in /etc/init.d/* at boot and when
configuration of the system manager is reloaded. This will allow
systemd(1) to support them similarly to native units.
LSB headers[2] in SysV init scripts are interpreted, and the ordering
specified in the header is turned into dependencies between the
generated unit and other units. The LSB facilities «$remote_fs»,
«$network», «$named», «$portmap», «$time» are supported and will be
turned into dependencies on specific native systemd targets. See
systemd.special(7) for more details.
SysV runlevels have corresponding systemd targets (runlevelX.target).
The wrapper unit that is generated will be wanted by those targets
which correspond to runlevels for which the script is enabled.
systemd does not support SysV scripts as part of early boot, so all
wrapper units are ordered after basic.target.
systemd-sysv-generator implements systemd.generator(7).
SEE ALSO
systemd(1), systemd.service(5), systemd.target(5)
NOTES
1.
SysV init
https://savannah.nongnu.org/projects/sysvinit
2.
LSB headers
http://refspecs.linuxbase.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
systemd 245 SYSTEMD-SYSV-GENERATOR(8)

sudo apt install —reinstall linux-headers-$(uname -r) virtualbox-dkms dkms

Reading package lists… Done
Building dependency tree
Reading state information… Done
The following packages were automatically installed and are no longer required:
libfprint-2-tod1 libllvm10 libllvm10:i386 linux-headers-5.4.0-59 linux-headers-5.4.0-59-generic
linux-headers-5.6.0-1020-oem linux-headers-5.6.0-1036-oem linux-headers-5.6.0-1039-oem
linux-image-5.4.0-59-generic linux-image-5.6.0-1020-oem linux-image-5.6.0-1036-oem
linux-image-5.6.0-1039-oem linux-modules-5.4.0-59-generic linux-modules-5.6.0-1020-oem
linux-modules-5.6.0-1036-oem linux-modules-5.6.0-1039-oem linux-modules-extra-5.4.0-59-generic
linux-modules-nvidia-450-5.4.0-59-generic linux-oem-5.6-headers-5.6.0-1020
linux-oem-5.6-headers-5.6.0-1036 linux-oem-5.6-headers-5.6.0-1039
Use ‘sudo apt autoremove’ to remove them.
0 upgraded, 0 newly installed, 3 reinstalled, 0 to remove and 1 not upgraded.
Need to get 1,990 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 dkms all 2.8.1-5ubuntu1 [66.6 kB]
Get:2 http://fi.archive.ubuntu.com/ubuntu focal-updates/main amd64 linux-headers-5.8.0-34-generic amd64 5.8.0-34.37~20.04.2 [1,236 kB]
Get:3 http://fi.archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 virtualbox-dkms amd64 6.1.10-dfsg-1~ubuntu1.20.04.1 [687 kB]
Fetched 1,990 kB in 0s (7,308 kB/s)
(Reading database … 412468 files and directories currently installed.)
Preparing to unpack …/dkms_2.8.1-5ubuntu1_all.deb …
Unpacking dkms (2.8.1-5ubuntu1) over (2.8.1-5ubuntu1) …
Preparing to unpack …/linux-headers-5.8.0-34-generic_5.8.0-34.37~20.04.2_amd64.deb …
Unpacking linux-headers-5.8.0-34-generic (5.8.0-34.37~20.04.2) over (5.8.0-34.37~20.04.2) …
Preparing to unpack …/virtualbox-dkms_6.1.10-dfsg-1~ubuntu1.20.04.1_amd64.deb …

——————————
Deleting module version: 6.1.10
completely from the DKMS tree.
——————————
Done.
Unpacking virtualbox-dkms (6.1.10-dfsg-1~ubuntu1.20.04.1) over (6.1.10-dfsg-1~ubuntu1.20.04.1) …
Setting up linux-headers-5.8.0-34-generic (5.8.0-34.37~20.04.2) …
/etc/kernel/header_postinst.d/dkms:
* dkms: running auto installation service for kernel 5.8.0-34-generic
…done.
Setting up dkms (2.8.1-5ubuntu1) …
Setting up virtualbox-dkms (6.1.10-dfsg-1~ubuntu1.20.04.1) …
Loading new virtualbox-6.1.10 DKMS files…
Building for 5.8.0-34-generic 5.8.0-36-generic
Building initial module for 5.8.0-34-generic
ERROR: Cannot create report: [Errno 17] File exists: ‘/var/crash/virtualbox-dkms.0.crash’
Error! Bad return status for module build on kernel: 5.8.0-34-generic (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.10/build/make.log for more information.
dpkg: error processing package virtualbox-dkms (—configure):
installed virtualbox-dkms package post-installation script subprocess returned error exit status 10
Processing triggers for man-db (2.9.1-1) …
Errors were encountered while processing:
virtualbox-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)

This system is currently not set up to build kernel modules.

This system is currently not set up to build kernel modules.
Please install the gcc make perl packages from your distribution.
modprobe vboxguest failed
The log file /var/log/vboxadd-setup.log may contain further information.

Установите

gcc

Rocky
,

CentOS

и RedHat это делается следующим образом

yum install gcc

The VirtualBox kernel modules do not match this version of VirtualBox

RTR3InitEx failed with rc=-1912 (rc=-1912)

The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing

‘/sbin/vboxconfig’

may correct this. Make sure that you are not mixing builds of VirtualBox from different sources.

where: supR3HardenedMainInitRuntime what: 4 VERR_VM_DRIVER_VERSION_MISMATCH (-1912) — The installed support driver doesn’t match the version of the user.

Возможно, существует более цивилизованный способ решения этой проблемы, но мне приходится удалять текущий VirtualBox

sudo apt remove —purge virtualbox
sudo apt install virtualbox

Иногда рекомендуют установить также virtualbox-dkms

sudo apt install virtualbox-dkms

Однажды мне помогло скачивание новой версии и устанавка из .deb

sudo dpkg -i virtualbox-6.1_6.1.28-147628~Ubuntu~eoan_amd64.deb

Nonexistent host networking interface

VBoxManage: error: Nonexistent host networking interface, name » (VERR_INTERNAL_ERROR)

Выполните, заменив ubuntu20 на имя вашей машины

VBoxManage showvminfo ubuntu20

У какого-то интерфейса вы обнаружите пустое место там где должно быть название сети. В данном примере
это NIC 1

NIC 1: MAC: 08002706DACE, Attachment: Host-only Interface » Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none

Убедитесь, что у вас есть нужная сеть и добавьте интерфейс туда

VBoxManage modifyvm ubuntu20 —nic1 hostonly —hostonlyadapter1 vboxnet0

Подробнее читайте в статье

«Подключение сетевого адаптераф»

Cannot unregister the machine

VBoxManage: error: Cannot unregister the machine ‘ubuntu’ while it is locked

Значит, что ваша машина в данный момент запущена.

Скорее всего в режиме headless, иначе бы вы её увидели и выключили бы.

Нужно найти запущенный процесс и закончить его. Например, с помощью

grep

ps -A | grep VBoxHeadless

10226 ? 00:01:01 VBoxHeadless

kill -9 10226

Или с помощью

awk

kill $(ps -A | grep VBoxHeadless | awk {‘print $1’})

Missing Dependencies Python Core / win32api

VBoxManage: error: Cannot unregister the machine ‘ubuntu’ while it is locked

alt

Установка VirtualBox в Windows 10

Установка VirtualBox в Windows 10

Установка VirtualBox в Windows 10

[Resolved] Nonexistent host networking interface, name ‘en4: Thunderbolt Ethernet’

I am trying to install a Primavera appliance demo in VirtalBox.

Host: Windows Server 2016 OS Release: 10.0.17763
Guest: Oracle Linux 6 U7
Machine: Hyper V is blade server ProLiant BL460c Gen8
Network Adapter: Microsoft Hyper-V Network Adapter
VirtualBox Version: 6.0.13 r133800

After installation of VirtualBox, i have imported appliance successfully.
When i click on start, i get the following error:

Failed to open a session for the virtual machine oracle-primavera-v188-ol67-appliance.

Nonexistent host networking interface, name ‘en4: Thunderbolt Ethernet’ (VERR_INTERNAL_ERROR).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I have gone through various forums but not able to get it working.

Appreciate any help to resolve the issue.

: screenshot of appliance in VBox; VBox_appliance.PNG (97.1 KiB) Viewed 38603 times

Attachments

VBox.log: VBox log file error; (3.39 KiB) Downloaded 217 times

Last edited by socratis on 19. Oct 2019, 10:43, edited 3 times in total.

Reason: Marked as [Resolved].

scottgus1: Site Moderator; Posts: 18925; Joined: 30. Dec 2009, 20:14; Primary OS: MS Windows 10; VBox Version: PUEL; Guest OSses: Windows, Linux

Re: Nonexistent host networking interface, name ‘en4: Thunderbolt Ethernet’ (VERR_INTERNAL_ERROR).

Post

by scottgus1 » 15. Oct 2019, 14:28

See on your screenshot, the guest Network settings? It says,

Adapter 1: Intel PRO/1000 MT Desktop (Bridged Adapter, en4: Thunderbolt Ethernet)

This means the adapter is trying to Bridge to the Thunderbolt Ethernet adapter, and you apparently don’t have one.

In the guest Network settings, under the «Name:» dropdown, pick an Ethernet adapter you do have, the one that you’re plugged into.

(Note that if all you have in the dropdown is a Wifi adapter, Bridged may not always work with a Wifi adapter, because of to-the-letter implementation of the Wifi protocols by either the wifi adapter driver or the access point firmware. Technically Wifi cannot Bridge, but some combinations of wifi adapter drivers and access point firmware implement these protocols in a lax fashion so Bridged can squeeze through. This is a limitation of Wi-fi, not caused by Virtualbox. If it works where you are, good. If you can’t get a good network trying to Bridge with a wifi adapter, you’ll have to go to wired Ethernet on the host PC.)

Junaidhk: Posts: 3; Joined: 15. Oct 2019, 09:14

Re: Nonexistent host networking interface, name ‘en4: Thunderbolt Ethernet’ (VERR_INTERNAL_ERROR).

Post

by Junaidhk » 15. Oct 2019, 15:10

In the Guest Network, under Name: there is only 1 option => Microsoft Hyper-V Network Adapter.

If i select «Host-only Adapter» i have options available as «VirtualBox Host-Only Ethernet Adapter». But even after selecting it, the «OK» option to accept it is greyed out and cannot be selected.

It doesnt allow me to change any Adapter configuration.

Attachments

: Host-Only Adapter screenshot; NetHostAdap1.PNG (29.73 KiB) Viewed 38589 times

: Bridge Adapter screenshot; NetAdap1.PNG (29.9 KiB) Viewed 38589 times

scottgus1: Site Moderator; Posts: 18925; Joined: 30. Dec 2009, 20:14; Primary OS: MS Windows 10; VBox Version: PUEL; Guest OSses: Windows, Linux

Re: Nonexistent host networking interface, name ‘en4: Thunderbolt Ethernet’ (VERR_INTERNAL_ERROR).

Post

by scottgus1 » 15. Oct 2019, 16:18

Junaidhk wrote:Machine: Hyper V is blade server ProLiant BL460c Gen8
Network Adapter: Microsoft Hyper-V Network Adapter

Is the OS you installed Virtualbox in an Hyper-V virtual machine? If so, this is nested virtualization, which is supposed to work only under very special circumstances. See the Virtualbox manual, section 9.35

If it will work, you might have to Bridge to the Hyper-V network adapter, as that appears to be all you’ve got. If it works, good. If it doesn’t, there is probably not anything we can do. You might try putting the appliance in the Hyper-V environment.

One other thing, there’s a warning in your screenshots «Invalid Settings Detected». See what that says.

socratis: Site Moderator; Posts: 27689; Joined: 22. Oct 2010, 11:03; Primary OS: Mac OS X other; VBox Version: PUEL; Guest OSses: Win(*>98), Linux*, OSX>10.5; Location: Greece

Re: Nonexistent host networking interface, name ‘en4: Thunderbolt Ethernet’ (VERR_INTERNAL_ERROR).

Post

by socratis » 16. Oct 2019, 09:58

scottgus1 wrote:Is the OS you installed Virtualbox in an Hyper-V virtual machine?

Yes, it is:

00:00:16.863666 DMI Product Name: Virtual Machine

@’Junaidhk’, as ‘scottgus1’ right-on-the-money commented:

scottgus1 wrote:If so, this is nested virtualization, which is supposed to work only under very special circumstances.

And those special circumstances are currently VirtualBox-on-VirtualBox. If it’s VirtualBox-on-Anything, then you got to start from the «Anything» part…

scottgus1 wrote:there’s a warning in your screenshots «Invalid Settings Detected». See what that says.

If you zoom in, that’s a Warning sign (triangle) over a Processor one. I guess some «Enable PAE/NX» enabled feature, which might not work due to the fact that it’s a virtualized-host…

Marking as [NotSupported].

Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the «QUOTE» button, please use the «POST REPLY«, at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.

socratis: Site Moderator; Posts: 27689; Joined: 22. Oct 2010, 11:03; Primary OS: Mac OS X other; VBox Version: PUEL; Guest OSses: Win(*>98), Linux*, OSX>10.5; Location: Greece

Re: [NotSupported] Nonexistent host networking interface, name ‘en4: Thunderbolt Ethernet’

Post

by socratis » 19. Oct 2019, 10:43

Junaidhk wrote:import the .ova file directly as a VM and they have managed to do that and have made the VM up and running

That configuration is definitely supported, changing the marking from [NotSupported] to [Resolved].

Источник

Virtualbox version

5.2.18

Vagrant version

Vagrant 2.1.5

Host operating system

Windows 10 x64

Guest operating system

ubuntu/xenial64

Vagrantfile

Vagrant.configure("2") do |config|
  config.vm.box = "ubuntu/xenial64"
  config.vm.hostname = "base"
  config.vm.network "public_network" , ip: "192.168.1.169"
end

Debug output

Stderr: VBoxManage.exe: error: Nonexistent host networking interface, name 'Broadcom 802.11n h├čl╦çzati adapter' (VE                                                           RR_INTERNAL_ERROR)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
>
ERROR vagrant: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "1794e8a1-6c18-41c5-91ed-da6fc23e1d21", "--type", "headless"]

Stderr: VBoxManage.exe: error: Nonexistent host networking interface, name 'Broadcom 802.11n h├čl╦çzati adapter' (VE                                                           RR_INTERNAL_ERROR)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

ERROR vagrant: C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/plugins/providers/virtualbox/driver/versi                                                           on_5_0.rb:714:in `block in start'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/util/retryable.rb:17:in `retryable'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/plugins/providers/virtualbox/driver/version_5_0.rb:704:i                                                           n `start'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/plugins/providers/virtualbox/action/boot.rb:16:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/plugins/providers/virtualbox/action/customize.rb:40:in `                                                           call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/plugins/providers/virtualbox/action/sane_defaults.rb:38:                                                           in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/builtin/set_hostname.rb:16:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/plugins/providers/virtualbox/action/forward_ports.rb:31:                                                           in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/plugins/providers/virtualbox/action/network_fix_ipv6.rb:                                                           41:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/plugins/providers/virtualbox/action/network.rb:123:in `c                                                           all'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/plugins/providers/virtualbox/action/clear_network_interf                                                           aces.rb:26:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/plugins/providers/virtualbox/action/prepare_nfs_settings                                                           .rb:19:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/builtin/synced_folders.rb:87:in `call                                                           '
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:i                                                           n `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/plugins/synced_folders/nfs/action_cleanup.rb:19:in `call                                                           '
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/plugins/providers/virtualbox/action/prepare_nfs_valid_id                                                           s.rb:12:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/builtin/handle_forwarded_port_collisi                                                           ons.rb:49:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/plugins/providers/virtualbox/action/prepare_forwarded_po                                                           rt_collision_params.rb:30:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/builtin/env_set.rb:19:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/builtin/provision.rb:80:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/plugins/providers/virtualbox/action/clear_forwarded_port                                                           s.rb:15:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/plugins/providers/virtualbox/action/set_name.rb:19:in `c                                                           all'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/plugins/providers/virtualbox/action/clean_machine_folder                                                           .rb:17:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/plugins/providers/virtualbox/action/check_accessible.rb:                                                           18:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:95:in `block in finalize_ac                                                           tion'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/builder.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/runner.rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/util/busy.rb:19:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/runner.rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/builtin/call.rb:53:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:95:in `block in finalize_ac                                                           tion'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/builder.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/runner.rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/util/busy.rb:19:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/runner.rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/builtin/call.rb:53:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:95:in `block in finalize_ac                                                           tion'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/builder.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/runner.rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/util/busy.rb:19:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/runner.rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/builtin/call.rb:53:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/builtin/box_check_outdated.rb:82:in `                                                           call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/builtin/config_validate.rb:25:in `cal                                                           l'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/plugins/providers/virtualbox/action/check_virtualbox.rb:                                                           26:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:95:in `block in finalize_ac                                                           tion'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:95:in `block in finalize_ac                                                           tion'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/builder.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/runner.rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/util/busy.rb:19:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/runner.rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/builtin/call.rb:53:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/builtin/config_validate.rb:25:in `cal                                                           l'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:95:in `block in finalize_ac                                                           tion'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:95:in `block in finalize_ac                                                           tion'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/builder.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/runner.rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/util/busy.rb:19:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/runner.rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/builtin/call.rb:53:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/plugins/providers/virtualbox/action/check_virtualbox.rb:                                                           26:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/warden.rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/builder.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/runner.rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/util/busy.rb:19:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/action/runner.rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/machine.rb:239:in `action_raw'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/machine.rb:208:in `block in action'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/environment.rb:614:in `lock'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/machine.rb:194:in `call'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/machine.rb:194:in `action'
C:/HashiCorp/Vagrant/embedded/gems/2.1.5/gems/vagrant-2.1.5/lib/vagrant/batch_action.rb:82:in `block (2 levels) in r                                                           un'
 INFO interface: error: There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "1794e8a1-6c18-41c5-91ed-da6fc23e1d21", "--type", "headless"]

Stderr: VBoxManage.exe: error: Nonexistent host networking interface, name 'Broadcom 802.11n h├čl╦çzati adapter' (VE                                                           RR_INTERNAL_ERROR)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "1794e8a1-6c18-41c5-91ed-da6fc23e1d21", "--type", "headless"]

Stderr: VBoxManage.exe: error: Nonexistent host networking interface, name 'Broadcom 802.11n h├čl╦çzati adapter' (VE                                                           RR_INTERNAL_ERROR)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
 INFO interface: Machine: error-exit ["Vagrant::Errors::VBoxManageError", "There was an error while executing `VBoxM                                                           anage`, a CLI used by Vagrantnfor controlling VirtualBox. The command and stderr is shown below.nnCommand: ["sta                                                           rtvm", "1794e8a1-6c18-41c5-91ed-da6fc23e1d21", "--type", "headless"]nnStderr: VBoxManage.exe: error: Nonexi                                                           stent host networking interface, name 'Broadcom 802.11n hu251Cu010Dlu2566u00E7zati adapter' (VERR_INTERNAL_ERROR                                                           )rnVBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsolern"]

References

#8967
#8207

I tried to edit the .vbox file with the correct unicode values but it doesnt work.

Источник

I am trying to vagrant up after windows 10 anniversary update, and I get an error:

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'scotch/box' is up to date...
==> default: Resuming suspended VM...
==> default: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "5c441fcf-c08f-4adb-8318-532107a81da3", "--type",     "headless"]

Stderr: VBoxManage.exe: error: Nonexistent host networking interface, name 'VirtualBox Host-Only Ethernet Adapter #2' (VERR_INTERNAL_ERROR)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

Before the update everything worked fine. I tried reinstall the newest version of VirtualBox and Vagrant also, but it doesn’t help.

Any help is appreciated.

asked Aug 4, 2016 at 7:17

xxxbencexxxbence

2,2301 gold badge22 silver badges14 bronze badges

Like @RusalBes sad the #2 adatper was not found. Therefore I went the Network Adapter setting in VirtualBox on that machine when the adapter name was not the «#2» instead of the normal «VirtualBox Host-Only Ethernet Adapter». Than I’ve just clicked OK and than everything works fine. I hope this will help others.

answered Aug 4, 2016 at 8:31

xxxbencexxxbence

2,2301 gold badge22 silver badges14 bronze badges

I had the same issue. I tried upgrading VirtualBox and Vagrant. Then I downgraded to VirtualBox 5.0, but it still didn’t work. Fortunately, I discovered this post, which basically showed that enabling the «VirtualBoxNDIS6 Bridged Network Driver» option in the «VirtualBox Host-Only Network» adapter properties in Network Settings resolved the issue. After doing that, everything began working again as expected.

Here’s the image from that post:

answered Aug 18, 2016 at 0:58

I just had the same trouble, reinstalling virtualbox 5.0 worked really fine.

answered Aug 4, 2016 at 7:45

LamaDelRayLamaDelRay

1992 silver badges11 bronze badges

I solved my problem installing the following versions of VirtualBox and Vagrant.

VirtualBox 5.0.26 (I had 5.0.18)
Vagrant 1.8.5 (I kept the same version)

As you can see I just uninstall VirtualBox and installed the 5.0.26 because Vagrant doesn’t work with Virtualbox 5.1.x

Regards!

answered Aug 9, 2016 at 14:45

SoldierCorpSoldierCorp

7,55016 gold badges60 silver badges99 bronze badges

I had this problem. Accepted solution did not work because the ‘Host Only Adapter’ did not have any options in the ‘Name:’ dropdown.

I solved this by selecting ‘Attach to’: ‘Bridged Adapter’ in vbox network setup, then the ‘Name:’ dropdown offered ‘Ethernet Adapter #2’ ….

answered May 15, 2018 at 10:27

Источник

	VirtualBox
	Установка
	Виртуальная CentOS 7 на Ubuntu
	Терминал VirtualBox
	Windows 7 на VirtualBox Debian
	NatNetwork
	VBoxManage Manual
	Разбор ошибок
	DevOps
	CentOS
	Ubuntu

Возможные проблемы

your current centos software installation requires of available space

Kernel driver not installed (rc=-1908)

This system is currently not set up to build kernel modules.

The VirtualBox kernel modules do not match this version of VirtualBox

Nonexistent host networking interface

Cannot unregister the machine

Missing Dependencies Python Core / win32api

[Resolved] Nonexistent host networking interface, name ‘en4: Thunderbolt Ethernet’

Re: Nonexistent host networking interface, name ‘en4: Thunderbolt Ethernet’ (VERR_INTERNAL_ERROR).

Re: Nonexistent host networking interface, name ‘en4: Thunderbolt Ethernet’ (VERR_INTERNAL_ERROR).

Re: Nonexistent host networking interface, name ‘en4: Thunderbolt Ethernet’ (VERR_INTERNAL_ERROR).

Re: Nonexistent host networking interface, name ‘en4: Thunderbolt Ethernet’ (VERR_INTERNAL_ERROR).

Re: [NotSupported] Nonexistent host networking interface, name ‘en4: Thunderbolt Ethernet’

Virtualbox version

Vagrant version

Host operating system

Guest operating system

Vagrantfile

Debug output

References

Возможно, вам также будет интересно: