# Vagrant + VirtualBOx can't mount on the latest CentOS7 vbox (centos/7 2004.01)

After updating to the latest version after a long time and vagrant up, I could not mount it, so make a note of what I checked.

environment

name version
Windows 10 2004(19041.685)
VirtualBox 6.1.16
Vagrant 2.2.14
vagrant-vbguest 0.28.0

This phenomenon also occurs on MacOS.

phenomenon

When I do vagrant up, I can't mount it like this

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'centos/7'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'centos/7' version '2004.01' is up to date...
==> default: Setting the name of the VM: centos7_default_1608725302718_27652
==> 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: 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: 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!
[default] No Virtualbox Guest Additions installation found.
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: ftp.riken.jp
 * extras: ftp.riken.jp
 * updates: ftp.riken.jp
Resolving Dependencies
--> Running transaction check
---> Package centos-release.x86_64 0:7-8.2003.0.el7.centos will be updated
---> Package centos-release.x86_64 0:7-9.2009.1.el7.centos will be an update
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package             Arch        Version                     Repository    Size
================================================================================
Updating:
 centos-release      x86_64      7-9.2009.1.el7.centos       updates       27 k

Transaction Summary
================================================================================
Upgrade  1 Package

Total download size: 27 k
Downloading packages:
No Presto metadata available for updates

... Omitted ...

No package kernel-devel-3.10.0-1127.el7.x86_64 available.
Error: Nothing to do
Unmounting Virtualbox Guest Additions ISO from: /mnt
umount: /mnt: not mounted
==> default: Checking for guest additions in VM...
    default: No guest additions were detected on the base box for this VM! Guest
    default: additions are required for forwarded ports, shared folders, host only
    default: networking, and more. If SSH fails on this machine, please install
    default: the guest additions and repackage the box to continue.
    default:
    default: This is not an error message; everything may continue to work properly,
    default: in which case you may ignore this message.
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

umount /mnt

Stdout from the command:



Stderr from the command:

umount: /mnt: not mounted

Cause

The contents of the vbox consist of CentOS 7.8, but since CentOS 7.9 has been released, the kernel-devel package that matches the installed kernel version cannot be retrieved from the repository. Oops.

Since you are using vbguest, updating VirtualBox Guest Additions fails because you cannot get the corresponding version of kernel-devel.

Workaround

Even if you fail with vagrant up, you can start up to the point where you can connect to SSH, so update kernel once and complete it with the following procedure.

  1. Failed with vagrant up
  2. vagrant ssh
  3. sudo yum -y update kernel
  4. exit
  5. vagrant reload --provision

It's just a first aid, so you have to either create your own updated vbox or wait for the official vbox to update.

reference

Recommended Posts

# Vagrant + VirtualBOx can't mount on the latest CentOS7 vbox (centos/7 2004.01)
Install the latest hardware drivers from ELRepo on CentOS
I installed CentOS 8 on Windows 10 using VirtualBox and Vagrant
Install Apache on CentOS on VirtualBox
Build the latest Samba 4 on Ubuntu 20.04
Use the iostat command on CentOS 8
Install OpenJDK (Java) on the latest Ubuntu
Install the webmail client Rainloop on CentOS 8
How to share on the host side (windows) and guest side (CentOS 7) with VirtualBox
Install the latest version of Jenkins on Ubuntu 16