Open fabstao opened 2 years ago
I was also facing this very issue and I am not sure what changed in recent updates.
I saw that this daemon was in an "inactive" state:
$ sudo systemctl status virtnetworkd
○ virtnetworkd.service - Virtualization network daemon
Loaded: loaded (/usr/lib/systemd/system/virtnetworkd.service; disabled; vendor preset: disabled)
Active: inactive (dead)
TriggeredBy: ● virtnetworkd.socket
○ virtnetworkd-ro.socket
○ virtnetworkd-admin.socket
Docs: man:libvirtd(8)
https://libvirt.org
So started and enabled it:
sudo systemctl enable --now virtnetworkd
Now it is working fine:
$ sudo systemctl status virtnetworkd
● virtnetworkd.service - Virtualization network daemon
Loaded: loaded (/usr/lib/systemd/system/virtnetworkd.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2022-01-31 12:09:16 IST; 9s ago
TriggeredBy: ● virtnetworkd-admin.socket
● virtnetworkd-ro.socket
● virtnetworkd.socket
Docs: man:libvirtd(8)
https://libvirt.org
Main PID: 56078 (virtnetworkd)
Tasks: 18 (limit: 18855)
Memory: 3.7M
CPU: 197ms
CGroup: /system.slice/virtnetworkd.service
└─56078 /usr/sbin/virtnetworkd --timeout 120
Jan 31 12:09:16 user systemd[1]: Starting Virtualization network daemon...
Jan 31 12:09:16 user systemd[1]: Started Virtualization network daemon.
Now vagrant up
works for me.
Thanks! Didn't work for me, now it is complaining about trying to use libvirt at all
[chris@fedora f36-vagrant]$ uname -a
Linux fedora 5.18.17-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Aug 11 14:36:06 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
[chris@fedora f36-vagrant]$
The same problem. Thanks @surajssd , that fix the problem.
sudo systemctl start virtnetworkd
or
sudo systemctl enable --now virtnetworkd
[chris@fedora f36-vagrant]$ uname -a Linux fedora 5.18.17-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Aug 11 14:36:06 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux [chris@fedora f36-vagrant]$
The same problem. Thanks @surajssd , that fix the problem.
sudo systemctl start virtnetworkd
or
sudo systemctl enable --now virtnetworkd
This also worked for me (Fedora36 Workstation)
Vagrant version
Host operating system
Guest operating system
Can't boot the guests OSes
Vagrantfile
Debug output
Debug: https://gist.github.com/fabstao/2b2fa5420180dcaf9996e83e0f250a0b
Expected behavior
What should have happened? Having two domains (VMs) running
Actual behavior
What actually happened?
Got error:
Steps to reproduce
vagrant up
as regular userReferences
No