| Summary: | RFE: allow user to specify custom sendkey sequences with gsettings | ||
|---|---|---|---|
| Product: | [Community] Virtualization Tools | Reporter: | Zdenek Kabelac <zkabelac> |
| Component: | virt-manager | Assignee: | Cole Robinson <crobinso> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | berrange, crobinso, gscrivan, juzhou, virt-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-09-01 23:59:11 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Zdenek Kabelac
2013-10-02 13:56:20 UTC
Isn't this sysrq turned off by default in distro kernels? If it's something that you need to compile a custom kernel for, then it's sufficiently obscure that I don't want to add an option to the UI for it, when as you point out there's a virsh sendkey option for. I've thought in the past about adding some gsettings/gconf way of allowing users to register their own key sequences, we can use this to track that. (In reply to Cole Robinson from comment #1) > Isn't this sysrq turned off by default in distro kernels? If it's something > that you need to compile a custom kernel for, then it's sufficiently obscure IMHO it's compiled-in in every Fedora kernel - and it's just disabled for security reasons for normal users. For a developer you may easily enable it by setting through sysctl settings: 'kernel.sysrq = 1' This will unlock all options. > that I don't want to add an option to the UI for it, when as you point out > there's a virsh sendkey option for. Well when you have a lot of graphical clicking windows from various remote boxes - you do not really want to bother with all the virsh ugliness. (And I've never tried that, I just assume it could probably work somehow in there). > I've thought in the past about adding some gsettings/gconf way of allowing > users to register their own key sequences, we can use this to track that. I'm not a gnome expert here, in fact I'd to go away from all the horrible Gnome3 thing and permanent unusability in Rawhide (it's been quite common to have to broken there for months...) - so I'm just openbox/xfce user. >
> > I've thought in the past about adding some gsettings/gconf way of allowing
> > users to register their own key sequences, we can use this to track that.
>
> I'm not a gnome expert here, in fact I'd to go away from all the horrible
> Gnome3 thing and permanent unusability in Rawhide (it's been quite common
> to have to broken there for months...) - so I'm just openbox/xfce user.
gsettings + dconf is what we use to store persistent settings no matter what desktop environment you are on. so the solution I propose would be independent of gnome shell
The goal going forward is to keep virt-manager's console support fairly slim and basic and punt more advanced cases to more appropriate tools. This is described more in the design document: https://github.com/virt-manager/virt-manager/blob/master/DESIGN.md I was onboard with adding more keycombo support to virt-manager for a while but nowadays if it should live anywhere it should be in virt-viewer IMO |