On Tue, 2019-01-29 at 10:39 +0000, Patrick O'Callaghan wrote: > 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. OK, first of all the Fedora guest doesn't have libvirt.service enabled, maybe because it was installed with no DE. Secondly, I did the following: 1) Verified that the Windows guest was still working. 2) Started the Fedora guest. 3) Both guests worked for a few minutes, then both failed. 4) Shut down the Fedora guest. Windows guest still failing. 5) Rebooted the Windows guest (from the virt-manager menu). Still failing. 6) Shut down the Windows guest and restarted it. It's now working. I think this is a strong indication that the problem is with libvirt itself. 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
