On Tue, 2019-01-29 at 06:11 +0800, Ed Greshko wrote: > 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. Interesting, though I wouldn't expect a difference between Gnome and KDE guests. Note that my guest is Fedora Server, with no DE installed. HOWEVER, (hold the front page!) Last night I rebooted everything and fired up *only* the Windows guest, and it is working perfectly. Recall that I've always had two guests running, so either a) the Fedora guest is screwing things up somehow, possibly in the way you suggest, or b) libvirt is confused by having two guests. If it's either of those things then something must have changed recently, because this is exactly the setup I've been using for months with no issues, and (I stress again) I have changed nothing in my configuration other than regular dnf updates. I'll do some more tests and report back. poc _______________________________________________ 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
