On 6/24/2025 6:37 PM, Richard W.M. Jones via Libguestfs wrote: >Reported-by: Srikanth Aithal >Fixed-by: Stefano Brivio >See: https://lists.libguestfs.org/archives/list/guestfs@lists.libguestfs.org/t... >--- > appliance/init | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > >diff --git a/appliance/init b/appliance/init >index 5d35a47dd..47eb97dfc 100755 >--- a/appliance/init >+++ b/appliance/init >@@ -127,7 +127,7 @@ ip addr add 127.0.0.1/8 brd + dev lo scope host > ip link set dev lo up > if test "$guestfs_network" = 1; then >- iface=$(ls -I all -I default -I lo /proc/sys/net/ipv4/conf) >+ iface=$(ls -I all -I default -I lo -I sit0 /proc/sys/net/ipv4/conf) > # Two workarounds for Ubuntu: > touch /etc/fstab > rm -f /etc/dhcp/dhclient-enter-hooks.d/resolved I tested this patch in my environment, and it resolves the issue observed. The IPv4 interface of the appliance is now properly configured with an IP address, even though sit0 resides within the same appliance: $ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00     inet 127.0.0.1/8 brd 127.255.255.255 scope host lo        valid_lft forever preferred_lft forever     inet6 ::1/128 scope host        valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000     link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff     inet 169.254.2.15/16 brd 169.254.255.255 scope global dynamic eth0        valid_lft 86400sec preferred_lft 86400sec     inet6 fe80::5054:ff:fe12:3456/64 scope link tentative        valid_lft forever preferred_lft forever 3: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000     link/sit 0.0.0.0 brd 0.0.0.0 Thank you, Tested-by: Srikanth Aithal <sraithal(a)amd.com&gt;