search

rocky-linux / kickstarts

24 stars 11 forks source link

vagrant box v7.0.0 for rocky 8 seems to be broken #4

Open lucc opened 1 year ago

lucc commented 1 year ago

I have the following Vagrantfile:

Vagrant.configure("2") do |config|
  config.vm.box = "rockylinux/8"
  config.vm.synced_folder ".", "/vagrant", disabled: true
  config.vm.define "v5" do |v5|
    v5.vm.box_version = "5.0.0"
  end
  config.vm.define "v7" do |v7|
    v7.vm.box_version = "7.0.0"
  end
end

I have no fancy plugins installed:

$ vagrant plugin list
vagrant-libvirt (0.8.2, system)

And then run vagrant up:

$ vagrant up
Bringing machine 'v5' up with 'virtualbox' provider...
Bringing machine 'v7' up with 'virtualbox' provider...
==> v5: Importing base box 'rockylinux/8'...
==> v5: Matching MAC address for NAT networking...
==> v5: Checking if box 'rockylinux/8' version '5.0.0' is up to date...
==> v5: Setting the name of the VM: test-rocky-8-v7_v5_1670952861960_92069
==> v5: Clearing any previously set network interfaces...
==> v5: Preparing network interfaces based on configuration...
    v5: Adapter 1: nat
==> v5: Forwarding ports...
    v5: 22 (guest) => 2222 (host) (adapter 1)
==> v5: Booting VM...
==> v5: Waiting for machine to boot. This may take a few minutes...
    v5: SSH address: 127.0.0.1:2222
    v5: SSH username: vagrant
    v5: SSH auth method: private key
    v5:
    v5: Vagrant insecure key detected. Vagrant will automatically replace
    v5: this with a newly generated keypair for better security.
    v5:
    v5: Inserting generated public key within guest...
    v5: Removing insecure key from the guest if it's present...
    v5: Key inserted! Disconnecting and reconnecting using new SSH key...
==> v5: Machine booted and ready!
==> v5: Checking for guest additions in VM...
    v5: No guest additions were detected on the base box for this VM! Guest
    v5: additions are required for forwarded ports, shared folders, host only
    v5: networking, and more. If SSH fails on this machine, please install
    v5: the guest additions and repackage the box to continue.
    v5:
    v5: This is not an error message; everything may continue to work properly,
    v5: in which case you may ignore this message.
==> v7: Importing base box 'rockylinux/8'...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["import", "-n", "/home/luc/.vagrant.d/boxes/rockylinux-VAGRANTSLASH-8/7.0.0/virtualbox/box.ovf"]

Stderr: 0%...
Progress state: VBOX_E_OBJECT_NOT_FOUND
VBoxManage: error: Appliance read failed
VBoxManage: error: Failed to open OVF file '/home/luc/.vagrant.d/boxes/rockylinux-VAGRANTSLASH-8/7.0.0/virtualbox/box.ovf' (VERR_FILE_NOT_FOUND)
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component ApplianceWrap, interface IAppliance
VBoxManage: error: Context: "RTEXITCODE handleImportAppliance(HandlerArg*)" at line 471 of file VBoxManageAppliance.cpp

It seems that the v5 box is indeed up but the v7 box not:

$ vagrant ssh v5 --command "echo v5"
v5
$ vagrant ssh v7 --command "echo v7"
VM must be created before running this command. Run `vagrant up` first.
NeilHanlon commented 1 year ago

Heya,

Thank you for the report. I built a new version of the image to address this problem. An older image was mistakenly pulled in which we didn't catch.. This will go into the gating checks going forward.

The 'Latest' vagrant images on https://dl.rockylinux.org/pub/rocky/8/images should have the fix.

Tangentially, we are working on a fix for BIOS booting on the 8.7 image, which you may run into. Presently you must force it to boot over UEFI.

e.g., using virtualbox:

  config.vm.provider "virtualbox" do |domain|
    domain.customize ["modifyvm", :id, "--firmware", "efi"]
  end