On 1/28/19 11:55 PM, Patrick O'Callaghan wrote: > On Mon, 2019-01-28 at 21:54 +0800, Ed Greshko wrote: > >> I'll do more in my AM. > Thanks again. > Well, yesterday I was able to replicate the symptoms of the problem you're having. I can't say if I actually duplicated it. However, this morning I can't determine the steps I took. The good news is that I know why I saw the same symptoms. My setup is the Host running F29 and KDE only. Two Guests, one running F29 KDE Only and the other running F29 GNOME only. Last night while checking, and maybe changing, things on the Host FW that pings weren't working. Looking around I found that the F29 GOME guest had created a virbr0 interface with 192.168.122.1/24 as the address. I didn't think to check routing info on all systems. :-( Anyway, I did find that a system with F29 installed has all the libvirt packages installed and libvirtd.service enabled. It would seem that the guests are supposed to detect they are guests and not create the bridge. FWIW, I started an F29 GNOME guest under VirtualBox and it does create the bridge. So, maybe, try disabling libvirt.service on any guests which may have it enabled and reboot *everything* to see if your problem persists. -- Right: I dislike the default color scheme Wrong: What idiot picked the default color scheme _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
