Vagrant up not working, what did I forget

lhirlimann · February 8, 2022, 12:44pm

Fresh new install of fedora 35.

I have followed instructions at Vagrant with libvirt provider — Fedora Developer Portal and when I ‘vagrant up’ I get the following error :

[ludovic@tenger test]$ vagrant up
Bringing machine 'default' up with 'libvirt' provider...
==> default: Checking if box 'generic/freebsd13' version '3.6.8' is up to date...
==> default: Starting domain.
==> default: Waiting for domain to get an IP address...
==> default: Halting domain...
/usr/share/vagrant/gems/gems/vagrant-libvirt-0.4.1/lib/vagrant-libvirt/driver.rb:137:in `list_all_networks': Call to virConnectListAllNetworks failed: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock-ro': No such file or directory (Libvirt::RetrieveError)
	from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.4.1/lib/vagrant-libvirt/driver.rb:137:in `get_ipaddress_from_system'
	from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.4.1/lib/vagrant-libvirt/driver.rb:97:in `get_domain_ipaddress'
	from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.4.1/lib/vagrant-libvirt/action/wait_till_up.rb:43:in `block (2 levels) in call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/util/retryable.rb:17:in `retryable'
	from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.4.1/lib/vagrant-libvirt/action/wait_till_up.rb:38:in `block in call'
	from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.4.1/lib/vagrant-libvirt/util/timer.rb:9:in `time'
	from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.4.1/lib/vagrant-libvirt/action/wait_till_up.rb:37:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.4.1/lib/vagrant-libvirt/action/start_domain.rb:359:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/builtin/synced_folders.rb:87:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/builtin/delayed.rb:19:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/plugins/synced_folders/nfs/action_cleanup.rb:25:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.4.1/lib/vagrant-libvirt/action/prepare_nfs_valid_ids.rb:12:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.4.1/lib/vagrant-libvirt/action/set_boot_order.rb:78:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-libvirt-0.4.1/lib/vagrant-libvirt/action/create_networks.rb:31:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/builtin/provision.rb:80:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:127:in `block in finalize_action'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/builder.rb:149:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/runner.rb:89:in `block in run'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/util/busy.rb:19:in `busy'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/runner.rb:89:in `run'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/builtin/call.rb:53:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:127:in `block in finalize_action'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/builder.rb:149:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/runner.rb:89:in `block in run'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/util/busy.rb:19:in `busy'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/runner.rb:89:in `run'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/builtin/call.rb:53:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:127:in `block in finalize_action'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/builder.rb:149:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/runner.rb:89:in `block in run'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/util/busy.rb:19:in `busy'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/runner.rb:89:in `run'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/builtin/call.rb:53:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/builtin/box_check_outdated.rb:93:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/warden.rb:48:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/builder.rb:149:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/runner.rb:89:in `block in run'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/util/busy.rb:19:in `busy'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/action/runner.rb:89:in `run'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/machine.rb:246:in `action_raw'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/machine.rb:215:in `block in action'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/environment.rb:614:in `lock'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/machine.rb:201:in `call'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/machine.rb:201:in `action'
	from /usr/share/vagrant/gems/gems/vagrant-2.2.16/lib/vagrant/batch_action.rb:86:in `block (2 levels) in run'

In the journal I see these :

Feb 08 13:35:12 tenger virtqemud[3830]: libvirt version: 7.6.0, package: 5.fc35 (Fedora Project, 2021-12-16-17:57:31, )
Feb 08 13:35:12 tenger virtqemud[3830]: hostname: tenger
Feb 08 13:35:12 tenger virtqemud[3830]: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock-ro': No such file or directory
Feb 08 13:35:12 tenger virtqemud[3830]: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock-ro': No such file or directory
Feb 08 13:35:14 tenger avahi-daemon[1184]: Joining mDNS multicast group on interface tap0.IPv6 with address fe80::fc5a:87ff:fe80:d12c.
Feb 08 13:35:14 tenger avahi-daemon[1184]: New relevant interface tap0.IPv6 for mDNS.
Feb 08 13:35:14 tenger avahi-daemon[1184]: Registering new address record for fe80::fc5a:87ff:fe80:d12c on tap0.*.
Feb 08 13:35:14 tenger kernel: virbr0: port 1(tap0) entered learning state
Feb 08 13:35:16 tenger kernel: virbr0: port 1(tap0) entered forwarding state
Feb 08 13:35:16 tenger kernel: virbr0: topology change detected, propagating

There’s probably more, but these are the red ones.

What did I forget to do ?

Ludovic

oprizal · February 8, 2022, 2:11pm

Hi, first I never uses vagrant, but I just want to give my though. Maybe you need to configure the virtual network?

lhirlimann · February 8, 2022, 2:36pm

Thanks for the idea - I don’t remember dint any of this last time I installed vagrant. Looking at it right now.

afiadi · February 9, 2022, 6:36am

I follow this article to run vagrant with kvm in Fedora 35
https://fedoramagazine.org/vagrant-qemukvm-fedora-devops-sysadmin/

lhirlimann · February 9, 2022, 12:48pm

Tried to add what was missing from my config but didn’t work better I ended up filling a bug.

ilikelinux · February 9, 2022, 2:23pm

please let us know the link.

The problem just happens with 5.16 or did you test with the older Kernel 5.15 too?

lhirlimann · February 9, 2022, 3:22pm

https://bugzilla.redhat.com/show_bug.cgi?id=2052376

Nope I did not test with older kernels.

jakfrost · February 9, 2022, 6:51pm

Hi @lhirlimann ,
Just wondering, and sorry if this has been done/asked already, but did you sudo dnf group install virtualization?

lhirlimann · February 9, 2022, 7:37pm

I wasn’t sure , so I redid the command. Doesn’t change the issue.

I had vagrant properly working on a previous f35 machine, but it had been updated from previous. My issue seems to lie because it’s a fresh install.

afiadi · February 10, 2022, 3:33am

I forget to inform, I use kernel 5.16.5-200, I thinks you just reinstall your vagrant with guide on those fedoramagazine link and try again. I thinks this is not bug.

lhirlimann · February 10, 2022, 6:40am

Thanks that worked.

lhirlimann · February 14, 2022, 6:11pm

So I ran into the issue again today while re-installing my computer (yes, I’ve been redeploying that beast a lot these days).
So I found what the issue was and here is my installation

sudo dnf install @virtualization
then follow the guide from Fedoramagazine
sudo systemctl enable --now virtnetworkd

That last line was the missing peace for me to have things working properly.

Ludovic

guide :