Vagrant and Virtualbox error "Network is not available" on fedora 42

Ask Fedora
,
1

Hi All,
I installed vagrant (2.3.4 from repos) and virtualbox (7.1.8 from repo) on fedora 42 to be used to study ansible and I’m using following Vagrant file as I got from the book to start 3 Vbox vms:

# -*- mode: ruby -*-
# vi: set ft=ruby :

VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  # General Vagrant VM configuration.
  config.vm.box = "generic/oracle8"
  config.ssh.insert_key = false
  config.vm.synced_folder ".", "/vagrant", disabled: true
  config.vm.provider :virtualbox do |v|
    v.memory = 512
    v.linked_clone = true
  end

  # Application server 1.
  config.vm.define "app1" do |app|
    app.vm.hostname = "orc-app1.test"
    app.vm.network :private_network, ip: "192.168.56.4"
  end

  # Application server 2.
  config.vm.define "app2" do |app|
    app.vm.hostname = "orc-app2.test"
    app.vm.network :private_network, ip: "192.168.56.5"
  end

  # Database server.
  config.vm.define "db" do |db|
    db.vm.hostname = "orc-db.test"
    db.vm.network :private_network, ip: "192.168.56.6"
  end
end

When i run “vagrant up” command, ireceive the following error:

"Network 192.168.56.4 is not available. Specify available network
name, or an ip address if you want to create a new network."

for all 3 vms.

I take a look to this question too but seems it doesn’t use virtualbox.

Please let me know If you have any suggestion.

PS On my old NB fedora 41 it works with same vagrant file.
The new NB with fedora42 had the problem also when was 41 and for this I updated it but with no luck.

Thanks for any help

SR

2

VirtualBox has a long history of compatibility related issues.
You should strongly consider switching to libvirt.

3

Thanks @vgaetera, but my problem is the book use many time virtualbox and config command are different for libvirt and I’ll be forced to “translate” all vagrant file.

Anyway I’ll think about it.

4

The latest VirtualBox seems to require a newer Vagrant, try the upstream repo:

1 Like
5

@vgaetera Thanks again.
That did the trick for me: added the repo and upgraded vagrant.
VMs are running now.

1 Like