Red Hat Bugzilla – Bug 1315663
qemu:///session disconnects after 30 seconds
Last modified: 2016-04-01 13:52:04 EDT
Created attachment 1134104 [details]
Description of problem:
After 30 seconds of connecting to a User Session, if no VM is started, the connection is dropped.
This has worked previously.
Version-Release number of selected component (if applicable):
Archlinux updated a few minutes ago.
[xxx@xxxx]$ sudo pacman -Q libvirt virt-manager
Steps to Reproduce:
1. Connect to User Session (qemu:///session)
2. Wait 30 seconds, without starting any VM
Connection is dropped and a new connect action is needed.
Connection stays up. Necessary if additional VM configuration is needed.
Error polling connection 'qemu:///session': internal error: client socket is closed
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 385, in _handle_tick_queue
File "/usr/share/virt-manager/virtManager/connection.py", line 1319, in tick_from_engine
raise e # pylint: disable=raising-bad-type
libvirtError: internal error: client socket is closed
Error mentioned on Arch foruns:
Doesn't seems to be related in my case because I'm not using the 'qemu///system', so libvirt service is not needed to be enabled on systemd.
Screenshots showing the error.
Created attachment 1134105 [details]
Created attachment 1134106 [details]
there's this fedora bug too:
seems a libvirt regression
Martin posted the patch upstream:
Patch was applied
Issue still ongoing.
This patch is still not available on https://libvirt.org/sources/libvirt-1.3.2.tar.gz.
Is it possible to apply the patch on any of this files?
Versions on my system, at the moment:
The patch isn't in a released libvirt version yet, it will be in libvirt 1.3.3. If you want the patch in arch, you'll need to contact the arch maintainers and ask them to backport this patch:
Author: Martin Kletzander <email@example.com>
Date: Tue Mar 1 15:42:32 2016 +0100
daemon: Properly check for clients