On 1/26/19 7:55 PM, Patrick O'Callaghan wrote:
The plot thickens. First of all, my snippet from wireshark was of course wrong as I was monitoring virbr0 instead of vnet0. Silly me.
Secondly, after a reboot to make sure everything was in default state, I fired up the Fedora guest alone, and lo and behold it worked. Then I fired up the Windows guest. It didn't work. Took it down and now the Fedora guest stopped working. Stopped and restarted both of them and they both work. Then suddenly they don't. Then they do again, or one does and the other doesn't.
While all this is going on, I try ping6 to both of them. It always works, even when ping doesn't.
My theory is that something is messing with DHCP. I'm running dnsmasq but I've been doing that for months. However avahi is also running, so perhaps there's some kind of conflict. And libvirtd apparently also runs its own dnsmasq internally, according to https://wiki.libvirt.org/page/Libvirtd_and_dnsmasq
Well, I only have Fedora guests and I just switched an existing one to use the NAT and running multiple guests works OK.
I don't run my own instance of dnsmasq. Just these of libvirt
[egreshko@meimei ~]$ ps -eaf | grep dnsmasq dnsmasq 1357 1 0 20:09 ? 00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper root 1358 1357 0 20:09 ? 00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
[egreshko@meimei ~]$ ps -eaf | grep avahi avahi 760 1 0 20:08 ? 00:00:00 avahi-daemon: running [meimei.local] avahi 918 760 0 20:08 ? 00:00:00 avahi-daemon: chroot helper
I currently don't have a Windows guest.