Vagrant - Не е дадено IP за гост на основния NFS помощник на Vagrant

Наскоро нашите Vagrant DEV VM вече няма да се зареждат от virtualbox (windows 10).

Това свързано ли е с текущата грешка в ядрото, която причинява проблеми с много от дистрибуциите?

ГРЕШКА: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/1820526
ГРЕШКА: https://bugs.launchpad.net/vagrant/+bug/1821083

Ето кода за стартиране:


vagrant up

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Setting the name of the VM: LOCAL-DEV_20190322_113839
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: You are trying to forward to privileged ports (ports <= 1024). Most
==> default: operating systems restrict this to only privileged process (typically
==> default: processes running as an administrative user). This is a warning in case
==> default: the port forwarding doesn't work. If any problems occur, please try a
==> default: port higher than 1024.
==> default: Forwarding ports...
    default: 22 (guest) => 22 (host) (adapter 1)
    default: 80 (guest) => 80 (host) (adapter 1)
    default: 443 (guest) => 443 (host) (adapter 1)
    default: 3306 (guest) => 3306 (host) (adapter 1)
    default: 6379 (guest) => 6379 (host) (adapter 1)
    default: 4369 (guest) => 4369 (host) (adapter 1)
    default: 9090 (guest) => 9090 (host) (adapter 1)
    default: 9100 (guest) => 9100 (host) (adapter 1)
    default: 9104 (guest) => 9104 (host) (adapter 1)
    default: 9150 (guest) => 9150 (host) (adapter 1)
    default: 5672 (guest) => 5672 (host) (adapter 1)
    default: 8883 (guest) => 8883 (host) (adapter 1)
    default: 15672 (guest) => 15672 (host) (adapter 1)
    default: 15674 (guest) => 15674 (host) (adapter 1)
    default: 15675 (guest) => 15675 (host) (adapter 1)
    default: 25672 (guest) => 25672 (host) (adapter 1)
    default: 35197 (guest) => 35197 (host) (adapter 1)
    default: 1883 (guest) => 1883 (host) (adapter 1)
    default: 5673 (guest) => 5673 (host) (adapter 1)
    default: 8161 (guest) => 8161 (host) (adapter 1)
    default: 61613 (guest) => 61613 (host) (adapter 1)
    default: 61614 (guest) => 61614 (host) (adapter 1)
    default: 61616 (guest) => 61616 (host) (adapter 1)
    default: 9900 (guest) => 9900 (host) (adapter 1)
    default: 9910 (guest) => 9910 (host) (adapter 1)
    default: 9200 (guest) => 9200 (host) (adapter 1)
    default: 9300 (guest) => 9300 (host) (adapter 1)
    default: 5601 (guest) => 5601 (host) (adapter 1)
    default: 27017 (guest) => 27017 (host) (adapter 1)
    default: 27018 (guest) => 27018 (host) (adapter 1)
    default: 27019 (guest) => 27019 (host) (adapter 1)
    default: 27080 (guest) => 27080 (host) (adapter 1)
    default: 28017 (guest) => 28017 (host) (adapter 1)
    default: 5432 (guest) => 5432 (host) (adapter 1)
    default: 5480 (guest) => 5480 (host) (adapter 1)
    default: 10000 (guest) => 10000 (host) (adapter 1)
    default: 20000 (guest) => 20000 (host) (adapter 1)
    default: 4444 (guest) => 4444 (host) (adapter 1)
    default: 3128 (guest) => 3128 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: password
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
==> default: Machine booted and ready!
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   5.2.16
VBoxService inside the vm claims: 5.2.26
Going on, assuming VBoxService is correct...
[default] GuestAdditions seems to be installed (5.2.26) correctly, but not running.
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   5.2.16
VBoxService inside the vm claims: 5.2.26
Going on, assuming VBoxService is correct...
Job for vboxadd-service.service failed because the control process exited with error code. See "systemctl status vboxadd-service.service" and "journalctl -xe" for details.
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   5.2.16
VBoxService inside the vm claims: 5.2.26
Going on, assuming VBoxService is correct...
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   5.2.16
VBoxService inside the vm claims: 5.2.26
Going on, assuming VBoxService is correct...
==> default: Checking for guest additions in VM...
==> default: Configuring and enabling network interfaces...
No guest IP was given to the Vagrant core NFS helper. This is an
internal error that should be reported as a bug.

cat /etc/lsb-release

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS"

uname -r

4.4.0-143-generic

Опитах се да възстановя заглавките на ядрото. Изглежда се инсталираха правилно.

sudo dpkg-reconfigure virtualbox-dkms

-------- Uninstall Beginning --------
Module:  virtualbox
Version: 5.1.38
Kernel:  4.4.0-143-generic (x86_64)
-------------------------------------

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

vboxdrv.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.4.0-143-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/4.4.0-143-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/4.4.0-143-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.


vboxpci.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.4.0-143-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.

------------------------------
Deleting module version: 5.1.38
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-5.1.38 DKMS files...
Building only for 4.4.0-143-generic
Building initial module for 4.4.0-143-generic
Done.

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

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

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

vboxpci.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.4.0-143-generic/updates/dkms/

depmod.....

DKMS: install completed.

Също така актуализирах virtualbox на Ubuntu

sudo apt install virtualbox-5.2

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  libsdl-ttf2.0-0
The following packages will be REMOVED:
  virtualbox virtualbox-guest-additions-iso virtualbox-qt
The following NEW packages will be installed:
  libsdl-ttf2.0-0 virtualbox-5.2
0 to upgrade, 2 to newly install, 3 to remove and 4 not to upgrade.
Need to get 0 B/73.9 MB of archives.
After this operation, 28.8 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Preconfiguring packages ...
(Reading database ... 375081 files and directories currently installed.)
Removing virtualbox-qt (5.1.38-dfsg-0ubuntu1.16.04.3) ...
Removing virtualbox (5.1.38-dfsg-0ubuntu1.16.04.3) ...
Removing virtualbox-guest-additions-iso (5.1.38-0ubuntu1.16.04.1) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for mime-support (3.59ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1.1) ...
Processing triggers for shared-mime-info (1.5-2ubuntu0.2) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Selecting previously unselected package libsdl-ttf2.0-0:amd64.
(Reading database ... 374771 files and directories currently installed.)
Preparing to unpack .../libsdl-ttf2.0-0_2.0.11-3_amd64.deb ...
Unpacking libsdl-ttf2.0-0:amd64 (2.0.11-3) ...
Selecting previously unselected package virtualbox-5.2.
Preparing to unpack .../virtualbox-5.2_5.2.26-128414~Ubuntu~xenial_amd64.deb ...
Unpacking virtualbox-5.2 (5.2.26-128414~Ubuntu~xenial) ...
Processing triggers for libc-bin (2.23-0ubuntu11) ...
Processing triggers for systemd (229-4ubuntu21.17) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1.1) ...
Processing triggers for shared-mime-info (1.5-2ubuntu0.2) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Processing triggers for mime-support (3.59ubuntu1) ...
Setting up libsdl-ttf2.0-0:amd64 (2.0.11-3) ...
Setting up virtualbox-5.2 (5.2.26-128414~Ubuntu~xenial) ...
addgroup: The group `vboxusers' already exists as a system group. Exiting.
Processing triggers for libc-bin (2.23-0ubuntu11) ...

Командата съществува и не извежда никакви грешки.

sudo /sbin/vboxconfig

vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.

Смаян съм, може би ще трябва да изчакам нова корекция на ядрото?


person Adan Rehtla    schedule 22.03.2019    source източник
comment
Дори опитът за монтиране на споделен диск във виртуалната машина води до грешки. _12_   -  person Adan Rehtla    schedule 22.03.2019
comment
Опит за надграждане до най-новата версия на vagrant v2.2.4 и virtualbox v6.0.4 r128413 (Qt5.6.2).   -  person Adan Rehtla    schedule 22.03.2019
comment
Без зарове... No guest IP was given to the Vagrant core NFS helper. This is an internal error that should be reported as a bug.   -  person Adan Rehtla    schedule 22.03.2019
comment
Има повече информация в: askubuntu .com/questions/1126591/ Изглежда, че това е известен проблем, който много хора са имали по един или друг начин.   -  person Ganton    schedule 25.03.2019


Отговори (2)


Няма бързо и лесно решение за това, най-добрият ви залог е да понижите версията на ядрото.

Вземете списък със заглавки и изображения на ядра

dpkg --list | grep linux-header
dpkg --list | grep linux-image

Премахнете неправилното ядро

sudo apt purge linux-image-4.4.0-143-generic linux-headers-4.4.0-143-generic linux-image-unsigned-4.4.0-143-generic linux-modules-4.4.0-143-generic linux-modules-extra-4.4.0-143-generic

apt-mark - задръжте неправилното ядро ​​за бъдещи актуализации

sudo apt-mark hold linux-image-4.4.0-143-generic linux-headers-4.4.0-143-generic linux-image-unsigned-4.4.0-143-generic linux-modules-4.4.0-143-generic linux-modules-extra-4.4.0-143-generic
sudo apt-mark showhold

Премахнете други ядра и dkms

sudo apt-get remove dkms build-essential linux-headers-*

Преинсталирайте по-старото ядро ​​и конфигурирайте dkms с помощта на virtualbox-guest-dkms

sudo apt-get install dkms build-essential linux-headers-4.4.0-142-generic virtualbox-guest-dkms

Рестартирайте, за да активирате старата версия на ядрото

sudo reboot

Пусни apt update

sudo apt update
sudo apt upgrade -y

И трябва да можете да стартирате вашите virtual-box / vagrant кутии отново.

person Adan Rehtla    schedule 25.03.2019

Наложих корекция преди няколко дни и днес тя мигрира в версия. https://launchpad.net/ubuntu/+source/virtualbox/4.3.40-dfsg-0ubuntu14.04.1 https://launchpad.net/ubuntu/+source/virtualbox-lts-xenial/4.3.40-dfsg-0ubuntu1.14.04.1~14.04.1 https://launchpad.net/ubuntu/+source/virtualbox-guest-additions-iso/4.3.40-0ubuntu1.14.04.1 моля, използвайте фиксирания пакет.

person Gianfranco Costamagna    schedule 25.03.2019
comment
Това е за Ubuntu 14.04 (Trusy). Има ли планове за корекция на Ubuntu 16.04 (Xenial)? - person Adan Rehtla; 26.03.2019
comment
Fox Xenial, virtualbox 5.1.38-dfsg-0ubuntu1.16.04.3 и virtualbox-hwe 5.1.38-dfsg-0ubuntu1.16.04.2 трябва да свършат работа - person Gianfranco Costamagna; 27.03.2019