You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
gives the following error message on Ubuntu 22.04:
Libvirt Provider:
* network configuration 1 for machine jem2 is a public_network referencing host device 'virbr0' which does not exist, consider adding ':dev => ....' referencing one of eno3, eno1np0, eno4, eno2np1, enp94s0f0np0, enp94s0f1np1, eno1np0.910, eno1np0.108, eno1np0.104
The same configuration works fine on a Ubuntu 20.04 machine running the same version of the libvirt plugin.
root@jemserver:~/Vagrantfiles/jem1_2_alma9# brctl show virbr0
bridge name bridge id STP enabled interfaces
virbr0 8000.86d4134aac58 no eno1np0
vnet4
root@jemserver:~/Vagrantfiles/jem1_2_alma9#
and also libvirt sees it:
root@jemserver:~/Vagrantfiles/jem1_2_alma9# virsh -c qemu:///system iface-list --all
Name State MAC Address
----------------------------------------------
docker0 inactive 02:42:b5:39:bd:32
eno2np1 inactive bc:97:e1:a6:bc:95
eno3 inactive bc:97:e1:a6:bc:92
eno4 inactive bc:97:e1:a6:bc:93
enp94s0f0np0 inactive bc:97:e1:cd:e4:90
enp94s0f1np1 inactive bc:97:e1:cd:e4:91
lo inactive 00:00:00:00:00:00
virbr0 active 86:d4:13:4a:ac:58
virbr0.104 active 66:c7:1f:ee:84:fb
virbr0.108 active 9e:13:93:0b:0d:f2
virbr0.910 active 36:ef:6a:e7:4b:a2
Maybe related to #1786 as we see this problem on Ubuntu 22.04 as well.
To Reproduce
Use the following Vagrantfile on an Ubuntu 22.04 host:
Vagrant.configure("2") do |config|
#
# JEM1
#
config.vm.define :jem1 do |j1|
config.vm.provider :libvirt do |libvirt|
libvirt.storage_pool_name = 'default'
libvirt.cpus = 4
libvirt.memory = 8192
libvirt.management_network_mode = "none"
libvirt.default_prefix = ""
libvirt.machine_virtual_size = 200 # in GB
libvirt.qemu_use_session = false
end
j1.vm.host_name = "jem1"
j1.vm.box = "roboxes/alma9"
j1.vm.box_check_update = false
j1.vm.network "public_network",
:dev => "virbr0",
:mode => "bridge",
:type => "bridge",
:ip => "10.1.1.1",
:netmask => "255.255.0.0"
j1.vm.provision "ansible" do |ansible|
ansible.playbook = "ansible.yml"
end
end
Expected behavior
VM should be created. The same Vagrantfile is working on an Ubuntu 20.04 host pointing to a similar bridged device.
Screenshots
Versions (please complete the following information)::
Libvirt version: 0.12.2
Vagrant version [output of vagrant version]: 2.4.0
Vagrant flavour [Upstream or Distro]: Upstream
Vagrant plugins versions (including vagrant-libvirt) [output of vagrant plugin list]: vagrant-libvirt (0.12.2, global) is the only line
Describe the bug
Vagrantfile containing
gives the following error message on Ubuntu 22.04:
The same configuration works fine on a Ubuntu 20.04 machine running the same version of the libvirt plugin.
virbr0
is existing:and also libvirt sees it:
Maybe related to #1786 as we see this problem on Ubuntu 22.04 as well.
To Reproduce
Use the following Vagrantfile on an Ubuntu 22.04 host:
Expected behavior
VM should be created. The same Vagrantfile is working on an Ubuntu 20.04 host pointing to a similar bridged device.
Screenshots
Versions (please complete the following information)::
vagrant version
]: 2.4.0vagrant plugin list
]:vagrant-libvirt (0.12.2, global)
is the only lineDebug Log
Attach Output of
VAGRANT_LOG=debug vagrant ... --provider=libvirt >vagrant.log 2>&1
See here
A Vagrantfile to reproduce the issue:
See above
The text was updated successfully, but these errors were encountered: