[virt-tools-list] [virt-manager][PATCH] Do not show manager window at startup if user requested to show any other window from command line.

[Cole Robinson]

On 05/29/2013 05:53 PM, Leonardo Augusto Guimarães Garcia wrote:
> Hey,
> 
> It has been quite some time since I last touched this topic here, but I would
> like to try to continue the discussion about providing something between
> virt-viewer and virt-manager for end-users whose basic necessity is to have
> access to the remote console but sometimes need to have some kind of control
> over the virtual machine, even though he/she doesn't want to interact with any
> other complexities related to the virtual machine management provided by
> virt-manager.
> 
> My first approach was to make this changes in virt-viewer, which was NACK by
> community. Suggestions were: create a third application in virt-viewer source
> code besides virt-viewer and remove-viewer to accomplish what I was trying to
> do or improve virt-manager to have the features I was looking for. I
> definitely prefer the later, and that's what I am trying to acomplish with the
> latest patch.
> 
> Although virt-manager has an option to start the console viewer (or any other
> details window) upon start, the manager window is always started as well. What
> I want is to avoid the manager window to be shown by default, so that a user
> not interested in dealing with all the details of the manager window can use
> the console view with a little bit more of control over the VM than is
> provided in virt-viewer.
> 

I agree that for something like this we should make virt-manager more
convenient to use, rather than go down the long path of creating a new app to
meet those needs. If you have any more suggestions I'm interested in hearing them.

These CLI virt-manager options don't historically have much use, so I'd be
fine with changing their semantics a bit to be more like virt-viewer. So you
could do 'virt-manager --connect [URI] [NAME|UUID|ID]' and it will do the
right thing, but also disable connection autoconnect for other non-specified
connections, not store the passed --connect value in gsettings, make it work
with launching multiple instances, etc.

- Cole