[From nobody Fri Dec 12 10:43:14 2014
From: Chris Murphy <lists@colorremedies.com>
Precedence: list
MIME-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
To: For testing and quality assurance of Fedora releases
	<test@lists.fedoraproject.org>
Date: Tue, 15 Oct 2013 00:25:15 -0600
Reply-To: For testing and quality assurance of Fedora releases
	<test@lists.fedoraproject.org>
Message-ID: <15D7112A-98F7-4B56-AF98-26F05B052425@colorremedies.com>
Content-Type: text/plain; charset=us-ascii
Subject: avahi/mDNS in qemu/kvm
Message: 5
Content-Transfer-Encoding: 7bit

Are multiple avahi/mDNS instances supposed to reliably work on one NIC with virtual machines?  I'm experiencing hostname resolution failure with avahi about 1 minute after avahi-daemon.service starts. Nothing is recorded in the journal in between working and not working. I've disabled firewalld in the VM and on the host and get the same results.

The baremetal host I can ssh to/from without there ever being a problem: ssh chris@f20s.local

The qemu/kvm guest, I can ssh to/from intermittently: ssh chris@f20sv.local

If I constantly log out and login, it always works, for 3-4 minutes. If I stop doing that for even 20 or seconds, the next attempt I get:
ssh: Could not resolve hostname f20sv.local: nodename nor servname provided, or not known

When that happens, I can still login the old fashioned way, ssh chris@192.168.1.xxx and this succeeds.

I can then 'systemctl restart avahi-daemon" and for a short while I can once again ssh/scp to my heart's content. Then it stops working. It is almost like a service like a firewall is taking a bit of time to cut it off, but then does so. But firewalld is not running on host or guest.

I'm not sure how to troubleshoot this further in the event it's not expected behavior.


Chris Murphy
]