Red Hat Bugzilla – Bug 1284567
Spice fails to connect to multiple VMs
Last modified: 2015-11-30 03:57:33 EST
Description of problem:
When multiple VMs are running/open virt-manager seems to be unable to connect to the spice server for a given VM. I am able, however, to connect using virt-viewer from the command line without issue.
Version-Release number of selected component (if applicable):
OS: Fedora 23
Fairly consistently but not 100% isolated yet
Steps to Reproduce: (not 100%
1. Start with an empty set of VMs
2. Install/Setup test VM (in my case I'm using RHEL 6.7 VMs)
3. Observe the console connects just fine and as expected
4. Create additional VMs or clone VM from step 2 few times
5. Open all the VMs and observe the connection state of the console window
VM console tab either sits at a blank screen forever (regardless to giving it focus and input) or sits with a 'Connecting to graphical console for guest' message forever.
The console tab connects to the Spice server and presents the VM's console to be interacted with
I'm using SSH (with ssh keys) to connect to a remove KVM server (no local KVM), and am able to connect without issue using virt-viewer by passing the SSH connect string being used by virt-manager and the UUID of the VM.
I've not been able to isolate the exact steps to reproduce with 100% accuracy, but it seems to be that the longer you use virt-manager the more common this connection issue presents itself as if it's an issue of stale connections. (But I hesitate to say that as it might be a red herring)
Can you check ~/.cache/virt-manager/virt-manager.log for any backtraces? Or run 'virt-manager --debug' and try to reproduce, then post the output
I'm not able to find any stack traces in virt-manager.log so I launched virt-manager with the --debug flag and have attached the resulting log.
With some more fiddling, I'm able to reproduce this using only 1 VM (there's 6 total running and 1 paused VMs, but I don't interact with them to trigger this bug) By repeatedly opening and closing the same VM's details window on the 3rd opening it'll fail to connect.
Annotated log file is attached.
Created attachment 1098443 [details]
Debug log from virt-manager while reproducing bug