hashicorp / vagrant

Vagrant is a tool for building and distributing development environments.
https://www.vagrantup.com
Other
26.16k stars 4.43k forks source link

[Bug] "private network" option is can't working on Manjaro (Arch base) Box. with massage `ip link set 'enp0s8' down && netctl restart 'enp0s8' && netctl enable 'enp0s8'` #13037

Open Extr3m4R4710 opened 1 year ago

Extr3m4R4710 commented 1 year ago

Debug output

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'NzxSec/NzxVox' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Loading metadata for box 'NzxSec/NzxVox'
    default: URL: https://vagrantcloud.com/NzxSec/NzxVox
==> default: Adding box 'NzxSec/NzxVox' (v0.2.0) for provider: virtualbox
    default: Downloading: https://vagrantcloud.com/NzxSec/boxes/NzxVox/versions/0.2.0/providers/virtualbox.box
==> default: Box download is resuming from prior download progress
==> default: Successfully added box 'NzxSec/NzxVox' (v0.2.0) for 'virtualbox'!
==> default: Importing base box 'NzxSec/NzxVox'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'NzxSec/NzxVox' version '0.2.0' is up to date...
==> default: Setting the name of the VM: NzxVox_default_1672315045290_54260
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> 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: private key
    default: 
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default: 
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   6.0.0
VBoxService inside the vm claims: 6.1.38
Going on, assuming VBoxService is correct...
[default] GuestAdditions versions on your host (7.0.4) and guest (6.1.38) do not match.
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   6.0.0
VBoxService inside the vm claims: 6.1.38
Going on, assuming VBoxService is correct...
:: Synchronizing package databases...
 core downloading...
 extra downloading...
 community downloading...
 multilib downloading...
 blackarch downloading...
:: Some packages should be upgraded first...
resolving dependencies...
looking for conflicting packages...

Packages (1) archlinux-keyring-20221220-1

Total Download Size:   1.13 MiB
Total Installed Size:  1.60 MiB
Net Upgrade Size:      0.02 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
 archlinux-keyring-20221220-1-any downloading...
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
upgrading archlinux-keyring...
==> Appending keys from archlinux.gpg...
==> Disabling revoked keys in keyring...
  -> Disabled 4 keys.
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:  26  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:  26  signed:  98  trust: 0-, 0q, 0n, 26m, 0f, 0u
gpg: depth: 2  valid:  78  signed:  26  trust: 78-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2023-04-21
==> Updating trust database...
gpg: next trustdb check due at 2023-04-21
:: Running post-transaction hooks...
(1/3) Reloading system manager configuration...
(2/3) Arming ConditionNeedsUpdate...
(3/3) Reinstate Black Arch keyring
==> Appending keys from blackarch.gpg...
==> Updating trust database...
gpg: next trustdb check due at 2023-04-21
warning: gcc-12.2.0-1 is up to date -- skipping
warning: make-4.3-5 is up to date -- skipping
warning: bzip2-1.0.8-5 is up to date -- skipping

resolving dependencies...
looking for conflicting packages...

Packages (1) dkms-3.0.9-1

Total Download Size:   0.04 MiB
Total Installed Size:  0.11 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
 dkms-3.0.9-1-any downloading...
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
installing dkms...
Optional dependencies for dkms
    linux-headers: build modules against the Arch kernel
    linux-lts-headers: build modules against the LTS kernel
    linux-zen-headers: build modules against the ZEN kernel
    linux-hardened-headers: build modules against the HARDENED kernel
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
Downloading VirtualBox Guest Additions ISO from https://download.virtualbox.org/virtualbox/7.0.4/VBoxGuestAdditions_7.0.4.iso
Copy iso file /home/raffix/.vagrant.d/tmp/VBoxGuestAdditions_7.0.4.iso into the box /tmp/VBoxGuestAdditions.iso
Mounting Virtualbox Guest Additions ISO to: /mnt
mount: /mnt: WARNING: source write-protected, mounted read-only.
Installing Virtualbox Guest Additions 7.0.4 - guest version is 6.1.38
Verifying archive integrity...  100%   MD5 checksums are OK. All good.
Uncompressing VirtualBox 7.0.4 Guest Additions for Linux  100%  
VirtualBox Guest Additions installer
Removing installed version 6.1.38 of VirtualBox Guest Additions...
./install.sh: line 153: VBoxControl: command not found
This system appears to have a version of the VirtualBox Guest Additions
already installed.  If it is part of the operating system and kept up-to-date,
there is most likely no need to replace it.  If it is not up-to-date, you
should get a notification when you start the system.  If you wish to replace
it with this version, please do not continue with this installation now, but
instead remove the current version first, following the instructions for the
operating system.

If your system simply has the remains of a version of the Additions you could
not remove you should probably continue now, and these will be removed during
installation.

Do you wish to continue? [yes or no]
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Setting up modules
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel 
modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Kernel headers not found for target kernel 
5.15.81-1-MANJARO. Please install them and execute
  /sbin/rcvboxadd setup
VirtualBox Guest Additions: Running kernel modules will not be replaced until 
the system is restarted
An error occurred during installation of VirtualBox Guest Additions 7.0.4. Some functionality may not work as intended.
In most cases it is OK that the "Window System drivers" installation failed.
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Setting up modules
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel 
modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Kernel headers not found for target kernel 
5.15.81-1-MANJARO. Please install them and execute
  /sbin/rcvboxadd setup
VirtualBox Guest Additions: Running kernel modules will not be replaced until 
the system is restarted
vboxadd-service.sh: Starting VirtualBox Guest Addition service.
Unmounting Virtualbox Guest Additions ISO from: /mnt
Cleaning up downloaded VirtualBox Guest Additions ISO...
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   6.0.0
VBoxService inside the vm claims: 7.0.4
Going on, assuming VBoxService is correct...
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   6.0.0
VBoxService inside the vm claims: 7.0.4
Going on, assuming VBoxService is correct...
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims:   6.0.0
VBoxService inside the vm claims: 7.0.4
Going on, assuming VBoxService is correct...
Restarting VM to apply changes...
==> default: Attempting graceful shutdown of VM...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

# Configure enp0s8
mv '/tmp/vagrant-network-enp0s8-1672315174-0' '/etc/netctl/enp0s8' &&
ip link set 'enp0s8' down &&
netctl restart 'enp0s8' &&
netctl enable 'enp0s8'

Stdout from the command:

Stderr from the command:

mv: cannot move '/tmp/vagrant-network-enp0s8-1672315174-0' to '/etc/netctl/enp0s8': No such file or directory

Expected behavior

Host-only adapter is properly set and operating

Actual behavior

Failing to configure and enable network interfaces

==> default: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

# Configure enp0s8
mv '/tmp/vagrant-network-enp0s8-1672315174-0' '/etc/netctl/enp0s8' &&
ip link set 'enp0s8' down &&
netctl restart 'enp0s8' &&
netctl enable 'enp0s8'

Stdout from the command:

Stderr from the command:

mv: cannot move '/tmp/vagrant-network-enp0s8-1672315174-0' to '/etc/netctl/enp0s8': No such file or directory

Reproduction information

Vagrant version

Vagrant 2.3.4

Host operating system

Kali Linux

Guest operating system

custom Manjaro (Arch base)

Steps to reproduce

  1. run following Vagrantfile with vagrant up
  2. [!!] error

Vagrantfile

Vagrant.configure("2") do |config|
  config.vm.box = "NzxSec/NzxVox"
  config.vm.network "private_network", ip: "192.168.56.2" # OR type: "dhcp"
end

If you want more info, I will reply additionally

yz271544 commented 2 months ago

+1 virtualbox: 7.0.18 vagrant: 2.4.1 kernel: linux66