search

personium / setup-vagrant

Vagrantfile and ansible for setting up of personium.io
Apache License 2.0
4 stars 9 forks source link

Failed to install using latest Vagrant and VirtualBox #48

Open dixonsiu opened 4 years ago

dixonsiu commented 4 years ago

Vagrant 2.2.9 & VirtualBox 6.1.10

D:\work\MyDataKorea\setup-vagrant>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'centos/7'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: setup-vagrant_default_1593351744029_58536
==> 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: 443 (guest) => 443 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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", "6d982037-0293-45b8-96e8-5f6d10063463", "--type", "headless"]

Stderr: VBoxManage.exe: error: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2' (VERR_INTNET_FLT_IF_NOT_FOUND).
VBoxManage.exe: error: Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
tochi-y commented 4 years ago

Vagrant 2.2.5 & VirtualBox 6.0.22 in my machine is OK. I don't know why this issue occurs.

dixonsiu commented 4 years ago

Maybe some differences between VirtualBox 6.0.22 and 6.1.10. I will try your version.

dixonsiu commented 4 years ago

From official website:

If you're looking for the latest VirtualBox 6.0 packages, see VirtualBox 6.0 builds. Please also use version 6.0 if you need to run VMs with software virtualization, as this has been discontinued in 6.1. Version 6.0 will remain supported until July 2020.