I've checked the posting at serverfault.com. It seems that yours is a bit of a noob question, and you got some harsh love in return... :-)
I'm not sure how to read your question at serverfault.com. There's a sequence of "ip ... " commands. The last one is the addition of a default route, pointing to 192.168.72.1. I suppose that's your router, physically reachable via eno1 in the HV/host machine. If I understand correctly, these commands are executed on the host? Would make sense. I understand that the physical eno0 gets bridged together with the tap interfaces going to the VM guests, and your host/HV instance of Linux accesses the network via the "artificial" br0 interface. I.e., the host/HV Linux instance and the VM/guest linux instances "sit side by side" on the same L2 network. Good. My counter-question is: exactly how did you set up the networking inside your VM guests? Those guest OS environments are Ubuntu as well? Note that Ubuntu (and modern Debian) can take network configuration in about two or three different styles, managed by different services. I recall the classic /etc/network/interfaces, or alternative config via the networkmanager's own config files, and I have a faint recollection of there being yet another way. Yes you can just run "ip ... whatever" by hand from the command line, and it takes immediate effect - but note that you manipulate the runtime config, and your mods to the runtime config of IP networking will probably get clobbered / flushed the next time the networkmanager or the ifup/ifdown scripts have a go, based on their respective config and some "event" that triggers them. And, one *specific* question: do you have the default route set up in the VM guest OS instances? A missing default route in the guests would explain your symptoms. Can you ping the default GW from inside the VM guests? In case you were wondering, note that you do *not* need specific routes to the VM guests, in the HV/host instance, nor at the firewall - as the host/HV and the VM/guests and your default HW all sit on the same L2 segment = they share a locally connected IP subnet = ARP handles the nitty gritty of local reachability. Frank From: Vishnupriya Karthy <vishnupriya.kar...@multicorewareinc.com> To: "qemu-discuss@nongnu.org" <qemu-discuss@nongnu.org> Subject: Hello experts, please help me sort this out Date sent: Wed, 5 Mar 2025 07:16:48 +0000 > > QEMU INTER-VM COMMUNICATION > https://serverfault.com/q/1174304/1239769?sem=2
