You are not logged in.
I've been struggling for about a month now to connect libvirtd/qemu (via virt-manager) virtual machines to the internet. I'm doing internet connectivity checks using a fedora 42 Everything (netinstall) ISO so that I can know when I've gotten it right.
I have dnscrypt-proxy installed and running directly on port 53, and my /etc/resolv.conf reads `nameserver 127.0.0.1`. I've tried setting network_backend to iptables in /etc/libvirt/network.conf, but this also does not fix the problem.
As a result, I find that guests cannot connect to the internet (via the default NAT device) even though libvirtd appears to be running with no visible problems in `systemctl status libvirtd`.
I'm using firewalld as my firewall, if that helps. I've tried reinstalling libvirtd, but that doesn't fix the issue.
Please let me know if any additional information might be helpful, I understand that this is a complex issue.
System information:
Operating System: Arch Linux
KDE Plasma Version: 6.4.1
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1
Kernel Version: 6.15.3-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 22 × Intel® Core™ Ultra 7 155H
Memory: 48 GiB of RAM (46.7 GiB usable)
Graphics Processor: Intel® Arc
Manufacturer: Notebook
Product Name: V54x_6x_TU
System Version: V540TU
Update: I tried again after stopping dnscrypt-proxy and starting systemd-resolved, and nothing changed, so I don't think this is an issue with dnscrypt-proxy. My guess is that there is some obscure flag in my settings, some misconfiguration, some missing package, or some other small problem that is causing my configuration to fail to provide network access to my VMs, but I have been unable to locate it. Any help would be greatly appreciated.
Update 2: Solved! I had a spare SSD lying around, so I installed arch on that to see if I could reproduce the issue on the new installation by cleanly installing it. Virtual machines had internet connectivity out of the box on the new install. So, I then carefully compared key folders in my /etc to gather clues as to where I had made an error. Eventually, I discovered that on my main (broken) rig, I had at some point ran `sudo systemctl enable nftables`, which I thought at the time would help libvirtd have internet connectivity, but seems to have ended up conflicting with it. **Disabling nftables via `sudo systemctl disable nftables` and then rebooting seemed to fix it, and VMs can now connect to the internet.** There was zero need to set network_backend to iptables in /etc/libvirt/network.conf as so many solutions on here advise. I'll leave this post here in case anyone else has the same issue.
Last edited by OIRNOIR (Today 06:12:11)
Offline