On Mon, Jan 07, 2013 at 05:52:54PM -0200, lagarcia@xxxxxxxxxxxxxxxxxx wrote: > From: Leonardo Garcia <lagarcia@xxxxxxxxxx> > > This menu would hold entries related to the connected guest life-cycle management: > - Restart > - Shutdown > - Forced Shutdown > - Redefine Hardware Settings > - etc. > > The inclusion of these new actions in virt-viewer would allow an end-user to be > able to have some control over the running VM without the need of opening > virt-manager or other management tools. This is specially useful in > environments in which the end-user is not using a management tool to start the > VMs, but, instead, have a direct link setup to connect to a local or remote VM > in his/her desktop. I don't really think this is somewhere that I want virt-viewer to go. I really view virt-viewer as a minimal application for interacting with the guest. In particular the intent is that the user of virt-viewer should not need to have administrative privileges to libvirtd, which your suggested menu options would require. IMHO the use case you're describing really is one for virt-manager to have. There is no requirement that virt-manager display its main manager window - it has a command line flag to make it immediately display the GUI console of a single VM, which pretty much provides the functionality you describe. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| _______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
