Description of problem: I use a separate spice client from virt-manager's integrated viewer, and sometimes use virt-manager to change some features of my domain while it's running. This causes virt-manager to refresh its spice client connection, which takes it away from my spice client. Even opening the domain will trigger the spice connection. I would like to be able to disable this, per-domain if possible, but globally is alright. Version-Release number of selected component (if applicable): 2.2.1 How reproducible: 100% Steps to Reproduce: 1. Run domain from virt-manager or virsh 2. Open external spice client of choice 3. Open domain config in virt-manager, or change domain from virt-manager while running Actual results: virt-manager initiates a spice connection, re-initiating it when any action is taken on the VM. Without a way to disable this, it boots out my preferred spice client Expected results: A toggle option to disable virt-manager's integrated spice viewer, so my external spice client retains its connection Additional info:
Updated title to clarify that I'm requesting a toggle setting, rather than disabling the spice viewer completely
*** Bug 1605705 has been marked as a duplicate of this bug. ***
Thanks for the suggestion, this is a good idea to side step these console collision problems. I will implement it for the next release
Upstream now: commit ac8591192f6cefe586813e7b1568451e47359e3d Author: Cole Robinson <crobinso> Date: Wed Sep 9 19:04:44 2020 -0400 console: Add option to disable autoconnect Edit->Preferences has a global 'Console autoconnect' option, enabled by default (the existing behavior). VM window has per-VM View->Autoconnect checkbox. When disabled, the viewer is replaced by a 'Connect to console' button. User needs to explicitly click it before we interact with spice/vnc at all. The viewer will stay connected while the window is open, but close + reopen and you'll need to click again.