Hello, all. After the very useful recommendation from Cole, I added the file /etc/sysconfig/virtnetworkd with the line VIRTNETWORKD_ARGS= This really helped - the short breaks out of the problem stopped. But yesterday I left my laptop at about 13:00 and returned today at 10:00 (times are approximate) - and again, my VM is not showing its window. Obviously, this is not such a big deal - restarting libvirtd once a day is not a problem. So, just for the information...:-) On Fri, 7 Jul 2023 at 11:41, Leon Pollak <leon.pollak@xxxxxxxxx> wrote: > > Thank you very much , Cole. It really helped! > > On Wed, 5 Jul 2023 at 21:10, Cole Robinson <crobinso@xxxxxxxxxx> wrote: > > > > On 7/4/23 10:48 AM, Leon Pollak wrote: > > > Hello. > > > After upgrading to FC38 I have the following problem: > > > After some time of inactivity (working in other windows in my FC38 KDE > > > machine), returning to the virt-manager (4.1.0) and guest window does > > > not happen. I see the window capture displaying "Virtual Machine > > > Manager" or the name of my VM, but nothing happens. > > > I still can switch back to the host machine. > > > If I run "systemctl restart libvirtd", close all windows and run > > > virt-manager again, after providing the root password everything > > > returns to its normal state - the guest continues to run (from the > > > same place), manager is working normally. > > > Till the next "time-out" which is rather "long" - about 10-15 minutes. > > > > > > Does someone know what to do in such a case? > > > > > > > It's probably this systemd regression, it's hitting lots of libvirt > > users right now: https://bugzilla.redhat.com/show_bug.cgi?id=2213660 > > > > - Cole > >
