Bugzilla – Bug 1216866
libvirt default network doesn't start automatically
Last modified: 2023-11-21 14:47:48 UTC
On my lab running TW 20231101, my default libvirt network was not autostarted at boot: $ virsh net-list --all Name State Autostart Persistent -------------------------------------------- default inactive yes yes I found out the culprit that was iptables-backend-nft-1.8.10-2.1.x86_64, due to the following error: Nov 03 10:06:05 rodan virtnetworkd[1393]: internal error: Failed to apply firewall rules /sbin/iptables -w --table nat --insert POSTROUTING --jump LIBVIRT_PRT: iptables v1.8.10 (nf_tables): CHAIN_ADD failed (No such file or directory): chain POSTROUTING After removing that package, my default libvirt network is now autostarted at boot: $ virsh net-list --all Name State Autostart Persistent -------------------------------------------- default active yes yes
I have the same issue. TW version is NAME="openSUSE Tumbleweed" # VERSION="20231110"
Hello Emiliano and xiaoguang, thank you for the report. Did this issue happen when iptables-backend-nft package was installed? Or did it break during the update to iptables 1.8.10?
(In reply to Danilo Spinella from comment #2) > Hello Emiliano and xiaoguang, thank you for the report. Did this issue > happen when iptables-backend-nft package was installed? Or did it break > during the update to iptables 1.8.10? This issue happened when iptables-backend-nft package was installed.
(In reply to Emiliano Langella from comment #3) > (In reply to Danilo Spinella from comment #2) > > Hello Emiliano and xiaoguang, thank you for the report. Did this issue > > happen when iptables-backend-nft package was installed? Or did it break > > during the update to iptables 1.8.10? > > This issue happened when iptables-backend-nft package was installed. Do you have any other iptables specific configuration? Or something that might be interfering with nftables backend?
(In reply to Danilo Spinella from comment #4) > Do you have any other iptables specific configuration? Or something that > might be interfering with nftables backend? I never configured iptables, firewall is disabled.
(In reply to Emiliano Langella from comment #5) > (In reply to Danilo Spinella from comment #4) > > Do you have any other iptables specific configuration? Or something that > > might be interfering with nftables backend? > > I never configured iptables, firewall is disabled. Then it might be a libvirt bug. Can you please open a bug upstream? https://gitlab.com/libvirt/libvirt/-/issues
(In reply to Danilo Spinella from comment #6) > (In reply to Emiliano Langella from comment #5) > > (In reply to Danilo Spinella from comment #4) > > > Do you have any other iptables specific configuration? Or something that > > > might be interfering with nftables backend? > > > > I never configured iptables, firewall is disabled. > > Then it might be a libvirt bug. Can you please open a bug upstream? > > https://gitlab.com/libvirt/libvirt/-/issues https://gitlab.com/libvirt/libvirt/-/issues/564