shaba/virt-manager
1
0
Fork 0
mirror of https://github.com/virt-manager/virt-manager.git synced 2025-01-05 09:17:57 +03:00
Code Issues Projects Releases Wiki Activity
0e5fb7d7c2
virt-manager/data/org.virt-manager.virt-manager.gschema.xml

358 lines
14 KiB
XML
Raw Normal View History

Port from gconf to gsettings This unfortunately has a decent amount of fallout: add a wrapper class in config.py that reduces much of the churn. Another big piece is that gsettings can't accept arbitrary paths like gconf would, everything needs to be described in the schema. Also do a bunch more RPM spec modernizing
2013-04-18 01:39:25 +04:00
<schemalist>
<!-- Relocatable per VM schema -->
<schema id="org.virt-manager.virt-manager.vm">
<key name="vm-window-size" type="(ii)">
<default>(-1, -1)</default>
<summary>VM window dimensions</summary>
<description>VM window dimensions</description>
</key>
<key name="scaling" type="i">
<default>-1</default>
<summary>When to scale the VM graphical console</summary>
<description>When to scale the VM graphical console. -1 = global default, 0 = never, 1 = only when in full screen mode, 2 = Always</description>
</key>
<key name="console-password" type="(si)">
<default>("", -1)</default>
<summary>Username and secrets ID for graphical password</summary>
<description>Username and secrets ID for graphical password</description>
</key>
console: Support spice 'resize-guest' (bz 754559) This will auto change the guest resolution to match the window size. Off by default, can be enabled like scaling preferences.
2014-01-31 18:13:53 +04:00
<key name="resize-guest" type="i">
<default>-1</default>
<summary>Automatically resize guest when window size changes</summary>
<description>Automatically change guest resolution along with virt-manager window. Only works with spice with a vdagent set up. -1 = global default, 0 = off, 1 = on.</description>
</key>
Port from gconf to gsettings This unfortunately has a decent amount of fallout: add a wrapper class in config.py that reduces much of the churn. Another big piece is that gsettings can't accept arbitrary paths like gconf would, everything needs to be described in the schema. Also do a bunch more RPM spec modernizing
2013-04-18 01:39:25 +04:00
</schema>
connection: Allow setting a custom 'pretty name' (bz 784701) We've had multiple requests over the years for something similar. People might have to connect to multiple IP addresses, or really large hostnames, that become difficult to distinguish in the UI. Add a field in the host details page that allows setting a custom name, and store it in gsettings.
2015-04-11 20:39:25 +03:00
<!-- Relocatable per conn schema -->
<schema id="org.virt-manager.virt-manager.connection">
<key name="pretty-name" type="s">
<default>''</default>
<summary>Custom connection description</summary>
<description>Custom connection description, used in the manager window. If empty, the app generates a default on demand.</description>
</key>
host: Remember window dimensions Like we do for details and manager windows, save window size in gsettings and remember it across app runs
2019-04-13 21:52:17 +03:00
<key name="window-size" type="(ii)">
<default>(-1, -1)</default>
<summary>Conn details window dimensions</summary>
<description>Connection details window dimensions</description>
</key>
connection: Allow setting a custom 'pretty name' (bz 784701) We've had multiple requests over the years for something similar. People might have to connect to multiple IP addresses, or really large hostnames, that become difficult to distinguish in the UI. Add a field in the host details page that allows setting a custom name, and store it in gsettings.
2015-04-11 20:39:25 +03:00
</schema>
Port from gconf to gsettings This unfortunately has a decent amount of fallout: add a wrapper class in config.py that reduces much of the churn. Another big piece is that gsettings can't accept arbitrary paths like gconf would, everything needs to be described in the schema. Also do a bunch more RPM spec modernizing
2013-04-18 01:39:25 +04:00
<schema id="org.virt-manager.virt-manager"
path="/org/virt-manager/virt-manager/">
<key name="system-tray" type="b">
<default>false</default>
<summary>Show system tray icon</summary>
<description>Show system tray icon while app is running</description>
</key>
preferences: Disable XML editing by default This adds a field in gsettings and preferences UI to enable XML editing. It's off by default. The XML tab page is still visible, but the textview is not editable, and there's a warning at the top: XML editing is disabled in 'Preferences'. Only enable it if you know what you are doing. When the setting is enabled, the warning goes away and the textview is editable. This puts a roadblock up for people that don't know what they are doing, but still advertises the feature and keeps the UI surface difference fairly small between on/off states.
2019-06-06 00:40:54 +03:00
<key name="xmleditor-enabled" type="b">
<default>false</default>
<summary>Enable XML editting UI</summary>
<description>Enable XML editting UI</description>
</key>
prefs: Add a setting to enable/disable libguestfs inspection Rather than key it on the library being available. Makes it much easier to test both modes of behavior. Fix up a few inspection bugs while I'm in the area, and convert it to be more singleton like.
2018-03-13 20:00:59 +03:00
<key name="enable-libguestfs-vm-inspection" type="b">
<default>true</default>
<summary>Enable libguestfs VM inspection</summary>
<description>Enable libguestfs VM inspection for things like OS icons, installed applications, etc. This only works if python libguestfs bindings are installed.</description>
</key>
Port from gconf to gsettings This unfortunately has a decent amount of fallout: add a wrapper class in config.py that reduces much of the churn. Another big piece is that gsettings can't accept arbitrary paths like gconf would, everything needs to be described in the schema. Also do a bunch more RPM spec modernizing
2013-04-18 01:39:25 +04:00
<key name="manager-window-height" type="i">
<default>0</default>
<summary>Default manager window height</summary>
<description>Default manager window height</description>
</key>
<key name="manager-window-width" type="i">
<default>0</default>
<summary>Default manager window width</summary>
<description>Default manager window width</description>
</key>
<child name="connections" schema="org.virt-manager.virt-manager.connections"/>
<child name="vmlist-fields" schema="org.virt-manager.virt-manager.vmlist-fields"/>
<child name="stats" schema="org.virt-manager.virt-manager.stats"/>
<child name="urls" schema="org.virt-manager.virt-manager.urls"/>
<child name="console" schema="org.virt-manager.virt-manager.console"/>
<child name="details" schema="org.virt-manager.virt-manager.details"/>
<child name="new-vm" schema="org.virt-manager.virt-manager.new-vm"/>
<child name="paths" schema="org.virt-manager.virt-manager.paths"/>
<child name="confirm" schema="org.virt-manager.virt-manager.confirm"/>
</schema>
<schema id="org.virt-manager.virt-manager.connections"
path="/org/virt-manager/virt-manager/connections/">
<key name="uris" type="as">
<default>[]</default>
<summary>Libvirt URIs listed in the manager window</summary>
<description>Libvirt URIs listed in the manager window</description>
</key>
<key name="autoconnect" type="as">
<default>[]</default>
<summary>Libvirt URIs to connect to on app startup</summary>
<description>Libvirt URIs to connect to on app startup</description>
</key>
</schema>
<schema id="org.virt-manager.virt-manager.vmlist-fields" path="/org/virt-manager/virt-manager/vmlist-fields/">
<key name="disk-usage" type="b">
<default>false</default>
<summary>Show disk I/O in summary</summary>
<description>Show the disk I/O field in the domain list summary view</description>
</key>
<key name="network-traffic" type="b">
<default>false</default>
<summary>Show network I/O in summary</summary>
<description>Show the network I/O field in the domain list summary view</description>
</key>
<key name="cpu-usage" type="b">
<default>true</default>
<summary>Show guest cpu usage in summary</summary>
<description>Show the guest cpu usage field in the domain list summary view</description>
</key>
<key name="host-cpu-usage" type="b">
<default>false</default>
<summary>Show host cpu usage in summary</summary>
<description>Show the host cpu usage field in the domain list summary view</description>
</key>
Add memory stats widget also to manager tree view. (crobinso: Fix an initialization issue)
2013-12-18 17:42:42 +04:00
<key name="memory-usage" type="b">
<default>false</default>
<summary>Show memory usage in summary</summary>
<description>Show memory usage field in the domain list summary view</description>
</key>
Port from gconf to gsettings This unfortunately has a decent amount of fallout: add a wrapper class in config.py that reduces much of the churn. Another big piece is that gsettings can't accept arbitrary paths like gconf would, everything needs to be described in the schema. Also do a bunch more RPM spec modernizing
2013-04-18 01:39:25 +04:00
</schema>
<schema id="org.virt-manager.virt-manager.stats" path="/org/virt-manager/virt-manager/stats/">
<key name="update-interval" type="i">
prefs: Change the tick interval to 3 seconds Most libvirt usage now shouldn't need a high tick interval, since we are using async events. So raise it.
2014-02-12 00:30:16 +04:00
<default>3</default>
Port from gconf to gsettings This unfortunately has a decent amount of fallout: add a wrapper class in config.py that reduces much of the churn. Another big piece is that gsettings can't accept arbitrary paths like gconf would, everything needs to be described in the schema. Also do a bunch more RPM spec modernizing
2013-04-18 01:39:25 +04:00
<summary>The statistics update interval</summary>
<description>The statistics update interval in seconds</description>
</key>
preferences: Allow disabling VM CPU poll With this, the only libvirt API call we hit on each tick is the connection nodeinfo.
2014-02-12 00:29:30 +04:00
<key name="enable-cpu-poll" type="b">
<default>true</default>
<summary>Poll VM CPU stats</summary>
<description>Whether or not the app will poll VM CPU statistics</description>
</key>
Port from gconf to gsettings This unfortunately has a decent amount of fallout: add a wrapper class in config.py that reduces much of the churn. Another big piece is that gsettings can't accept arbitrary paths like gconf would, everything needs to be described in the schema. Also do a bunch more RPM spec modernizing
2013-04-18 01:39:25 +04:00
<key name="enable-disk-poll" type="b">
<default>false</default>
<summary>Poll disk i/o stats</summary>
<description>Whether or not the app will poll VM disk i/o statistics</description>
</key>
<key name="enable-net-poll" type="b">
<default>false</default>
<summary>Poll net i/o stats</summary>
<description>Whether or not the app will poll VM network i/o statistics</description>
</key>
prefs: Allow disabling all memorystats polling Similar to how we allow disabling disk/net polling, not sure yet what effect it might have on remote connections, so best to add this option just to be safe. Unlike disk/net stats, we enable this checking by default.
2014-01-13 02:39:21 +04:00
<key name="enable-memory-poll" type="b">
prefs: Disable memory polling by default This path hits the qemu monitor, and leads to the virt-manager UI being locked up when performing asynchronous tasks like creating a snapshot. So make it opt in for people that want it.
2014-02-11 00:14:10 +04:00
<default>false</default>
prefs: Allow disabling all memorystats polling Similar to how we allow disabling disk/net polling, not sure yet what effect it might have on remote connections, so best to add this option just to be safe. Unlike disk/net stats, we enable this checking by default.
2014-01-13 02:39:21 +04:00
<summary>Poll memory stats</summary>
<description>Whether or not the app will poll VM memory statistics</description>
</key>
Port from gconf to gsettings This unfortunately has a decent amount of fallout: add a wrapper class in config.py that reduces much of the churn. Another big piece is that gsettings can't accept arbitrary paths like gconf would, everything needs to be described in the schema. Also do a bunch more RPM spec modernizing
2013-04-18 01:39:25 +04:00
</schema>
<schema id="org.virt-manager.virt-manager.urls"
gsettings: Remove url-list-length Kinda pointless, just default to 10
2013-04-23 20:42:22 +04:00
path="/org/virt-manager/virt-manager/urls/">
Port from gconf to gsettings This unfortunately has a decent amount of fallout: add a wrapper class in config.py that reduces much of the churn. Another big piece is that gsettings can't accept arbitrary paths like gconf would, everything needs to be described in the schema. Also do a bunch more RPM spec modernizing
2013-04-18 01:39:25 +04:00
gschema: Populate/Store previous container URLs
2017-07-05 19:51:21 +03:00
<key name="containers" type="as">
<default>[]</default>
<summary>Saved list of source URLs</summary>
<description>Saved list of source URLs used to bootstrap OS containers</description>
</key>
Port from gconf to gsettings This unfortunately has a decent amount of fallout: add a wrapper class in config.py that reduces much of the churn. Another big piece is that gsettings can't accept arbitrary paths like gconf would, everything needs to be described in the schema. Also do a bunch more RPM spec modernizing
2013-04-18 01:39:25 +04:00
<key name="urls" type="as">
<default>[]</default>
<summary>Saved list of install URLs</summary>
<description>Saved list of install URLs</description>
</key>
<key name="isos" type="as">
<default>[]</default>
<summary>Saved list of install ISOs</summary>
<description>Saved list of install ISOs</description>
</key>
<key name="kickstarts" type="as">
<default>[]</default>
<summary>Saved list of install kickstarts</summary>
<description>Saved list of install kickstarts</description>
</key>
</schema>
<schema id="org.virt-manager.virt-manager.console"
path="/org/virt-manager/virt-manager/console/">
<key name="enable-accels" type="b">
<default>false</default>
<summary>Enable menu accelerators in console window</summary>
<description>Whether to enable menu accelerators while connected to the guest graphical console.</description>
</key>
<key name="scaling" type="i">
<default>1</default>
<summary>When to scale the VM graphical console</summary>
<description>When to scale the VM graphical console. 0 = never, 1 = only when in full screen mode, 2 = Always</description>
</key>
console: Support spice 'resize-guest' (bz 754559) This will auto change the guest resolution to match the window size. Off by default, can be enabled like scaling preferences.
2014-01-31 18:13:53 +04:00
<key name="resize-guest" type="i">
<default>-1</default>
<summary>Automatically resize guest when window size changes</summary>
<description>Automatically change guest resolution along with virt-manager window. Only works with spice with a vdagent set up. -1 = global default, 0 = off, 1 = on.</description>
</key>
Port from gconf to gsettings This unfortunately has a decent amount of fallout: add a wrapper class in config.py that reduces much of the churn. Another big piece is that gsettings can't accept arbitrary paths like gconf would, everything needs to be described in the schema. Also do a bunch more RPM spec modernizing
2013-04-18 01:39:25 +04:00
<key name="grab-keys" type="s">
<default>''</default>
<summary>Grab keyboard sequence for the graphical console</summary>
<description>Grab keyboard sequence for the graphical console</description>
</key>
add new "spice-disable-usbredir" option to disable autoredir feature The value is stored in gsettings. By default, we use spice autoredir feature for usb redirection.
2013-07-01 22:32:21 +04:00
Add a gsetting key to disable keyboard grabbing Add a gsetting key to disable keyboard grabbing that works the same way as spicy when unchecking "Options" > "Grab keyboard when active and focused".
2014-03-10 21:07:15 +04:00
<!--This key is not intended to be exposed in the UI yet-->
<key name="grab-keyboard" type="b">
<default>true</default>
<summary>Enable grab keyboard when active and focused</summary>
<description>Enable grab keyboard when active and focused</description>
</key>
add new "spice-disable-usbredir" option to disable autoredir feature The value is stored in gsettings. By default, we use spice autoredir feature for usb redirection.
2013-07-01 22:32:21 +04:00
<key name="auto-redirect" type="b">
<default>true</default>
<summary>Enable SPICE Auto USB redirection in console window</summary>
<description>Whether to enable SPICE Auto USB redirection while connected to the guest console.</description>
</key>
Port from gconf to gsettings This unfortunately has a decent amount of fallout: add a wrapper class in config.py that reduces much of the churn. Another big piece is that gsettings can't accept arbitrary paths like gconf would, everything needs to be described in the schema. Also do a bunch more RPM spec modernizing
2013-04-18 01:39:25 +04:00
</schema>
prefs: Remove distinction between local and remote sound Remote sound works fine these days. If people want to turn the preference off, they probably want to do it in all cases, and can 'customize before install' to alter the rest.
2013-04-23 22:02:46 +04:00
<schema id="org.virt-manager.virt-manager.details"
path="/org/virt-manager/virt-manager/details/">
Port from gconf to gsettings This unfortunately has a decent amount of fallout: add a wrapper class in config.py that reduces much of the churn. Another big piece is that gsettings can't accept arbitrary paths like gconf would, everything needs to be described in the schema. Also do a bunch more RPM spec modernizing
2013-04-18 01:39:25 +04:00
<key name="show-toolbar" type="b">
<default>true</default>
<summary>Whether to show VM button toolbar in Details display</summary>
<description>Whether to show toolbar containing Virtual Machine action buttons (such as Run, Pause, Shutdown) in the details display</description>
</key>
</schema>
prefs: Remove distinction between local and remote sound Remote sound works fine these days. If people want to turn the preference off, they probably want to do it in all cases, and can 'customize before install' to alter the rest.
2013-04-23 22:02:46 +04:00
<schema id="org.virt-manager.virt-manager.new-vm"
path="/org/virt-manager/virt-manager/new-vm/">
<key name="add-sound" type="b">
Port from gconf to gsettings This unfortunately has a decent amount of fallout: add a wrapper class in config.py that reduces much of the churn. Another big piece is that gsettings can't accept arbitrary paths like gconf would, everything needs to be described in the schema. Also do a bunch more RPM spec modernizing
2013-04-18 01:39:25 +04:00
<default>true</default>
prefs: Remove distinction between local and remote sound Remote sound works fine these days. If people want to turn the preference off, they probably want to do it in all cases, and can 'customize before install' to alter the rest.
2013-04-23 22:02:46 +04:00
<summary>Install sound device for new Vms</summary>
<description>Whether to install a sound device for new VMs</description>
Port from gconf to gsettings This unfortunately has a decent amount of fallout: add a wrapper class in config.py that reduces much of the churn. Another big piece is that gsettings can't accept arbitrary paths like gconf would, everything needs to be described in the schema. Also do a bunch more RPM spec modernizing
2013-04-18 01:39:25 +04:00
</key>
<key name="graphics-type" type="s">
<default>'system'</default>
<summary>Install selected graphics type for new VM</summary>
<description>Install selected graphics type for new VM. vnc or spice, system for software configured default</description>
</key>
prefs: Add 'Add SPICE USB redirection' option, enable it For qemu guests that are using spice, add 4 redirdevs so USB redirection happens for free. This can be disabled in the preferences dialog.
2014-02-05 00:12:23 +04:00
<key name="add-spice-usbredir" type="s">
<default>'system'</default>
<summary>Add spice usbredir HW for new VMs</summary>
<description>Add spice usbredir HW for new VMs. yes, no, or system for software configured default</description>
</key>
Port from gconf to gsettings This unfortunately has a decent amount of fallout: add a wrapper class in config.py that reduces much of the churn. Another big piece is that gsettings can't accept arbitrary paths like gconf would, everything needs to be described in the schema. Also do a bunch more RPM spec modernizing
2013-04-18 01:39:25 +04:00
<key name="storage-format" type="s">
<default>'default'</default>
<summary>Use selected format for new VM storage</summary>
<description>Use selected format when creating new disk images in new VM wizard</description>
</key>
prefs: Allow changing the default VM CPU mode/model config Add a preference for changing the default CPU mode/model. The options are: - default (whatever virt-manager chooses as the default) - hypervisor default (no <cpu> block, what we've always done) - nearest host cpu model (just the 'model' from caps->host->cpu) - copy host cpu (the entire <cpu> block from caps->host) The setting only applies to KVM guests, not tested with anything else. The default is left as is for now (hypervisor default). copy host CPU will one day use mode='host-model', when it does what we want. At that point we will probably make it the default
2014-01-18 00:32:40 +04:00
<key name="cpu-default" type="s">
<default>'default'</default>
<summary>CPU setting to use for new VMs</summary>
wip
2014-02-05 22:51:53 +04:00
<description>CPU setting to use for new VMs. Limited to VMs matching the host architecture. Possible values: default (virt-manager default), hv-default (qemu's default), host-model-only (just the model, not the additional features), host-model (libvirt's host-model setting).</description>
prefs: Allow changing the default VM CPU mode/model config Add a preference for changing the default CPU mode/model. The options are: - default (whatever virt-manager chooses as the default) - hypervisor default (no <cpu> block, what we've always done) - nearest host cpu model (just the 'model' from caps->host->cpu) - copy host cpu (the entire <cpu> block from caps->host) The setting only applies to KVM guests, not tested with anything else. The default is left as is for now (hypervisor default). copy host CPU will one day use mode='host-model', when it does what we want. At that point we will probably make it the default
2014-01-18 00:32:40 +04:00
</key>
Port from gconf to gsettings This unfortunately has a decent amount of fallout: add a wrapper class in config.py that reduces much of the churn. Another big piece is that gsettings can't accept arbitrary paths like gconf would, everything needs to be described in the schema. Also do a bunch more RPM spec modernizing
2013-04-18 01:39:25 +04:00
</schema>
gsettings: Simplify remembering last used paths
2013-04-23 22:16:54 +04:00
<schema id="org.virt-manager.virt-manager.paths"
path="/org/virt-manager/virt-manager/paths/">
<key name="image-default" type="s">
Port from gconf to gsettings This unfortunately has a decent amount of fallout: add a wrapper class in config.py that reduces much of the churn. Another big piece is that gsettings can't accept arbitrary paths like gconf would, everything needs to be described in the schema. Also do a bunch more RPM spec modernizing
2013-04-18 01:39:25 +04:00
<default>''</default>
<summary>Default image path</summary>
<description>Default path for choosing VM images</description>
</key>
gsettings: Simplify remembering last used paths
2013-04-23 22:16:54 +04:00
<key name="media-default" type="s">
Port from gconf to gsettings This unfortunately has a decent amount of fallout: add a wrapper class in config.py that reduces much of the churn. Another big piece is that gsettings can't accept arbitrary paths like gconf would, everything needs to be described in the schema. Also do a bunch more RPM spec modernizing
2013-04-18 01:39:25 +04:00
<default>''</default>
<summary>Default media path</summary>
<description>Default path for choosing media</description>
</key>
gsettings: Simplify remembering last used paths
2013-04-23 22:16:54 +04:00
<key name="screenshot-default" type="s">
Port from gconf to gsettings This unfortunately has a decent amount of fallout: add a wrapper class in config.py that reduces much of the churn. Another big piece is that gsettings can't accept arbitrary paths like gconf would, everything needs to be described in the schema. Also do a bunch more RPM spec modernizing
2013-04-18 01:39:25 +04:00
<default>''</default>
<summary>Default screenshot path</summary>
<description>Default path for saving screenshots from VMs</description>
</key>
Fix crash when creating guest from ISO media (bz 958641) Accessing another unknown gsettings key. Should be the last one though...
2013-05-10 04:07:29 +04:00
gsettings: Fix default for perms-fix-ignore (bz 962569)
2013-05-15 23:35:55 +04:00
<key name="perms-fix-ignore" type="as">
<default>[]</default>
Fix crash when creating guest from ISO media (bz 958641) Accessing another unknown gsettings key. Should be the last one though...
2013-05-10 04:07:29 +04:00
<summary>Ask about fixing permissions</summary>
<description>Whether to ask about fixing path permissions</description>
</key>
Port from gconf to gsettings This unfortunately has a decent amount of fallout: add a wrapper class in config.py that reduces much of the churn. Another big piece is that gsettings can't accept arbitrary paths like gconf would, everything needs to be described in the schema. Also do a bunch more RPM spec modernizing
2013-04-18 01:39:25 +04:00
</schema>
<schema id="org.virt-manager.virt-manager.confirm" path="/org/virt-manager/virt-manager/confirm/">
<key name="forcepoweroff" type="b">
<default>true</default>
<summary>Confirm force poweroff request</summary>
<description>Whether we require confirmation to forcepoweroff a VM</description>
</key>
<key name="poweroff" type="b">
<default>false</default>
<summary>Confirm poweroff request</summary>
<description>Whether we require confirmation to poweroff/reboot a VM</description>
</key>
<key name="pause" type="b">
<default>false</default>
<summary>Confirm pause request</summary>
<description>Whether we require confirmation to pause a VM</description>
</key>
<key name="removedev" type="b">
<default>true</default>
<summary>Confirm device removal request</summary>
<description>Whether we require confirmation to remove a virtual device</description>
</key>
<key name="interface-power" type="b">
<default>true</default>
<summary>Confirm device interface start and stop</summary>
<description>Whether we require confirmation to start or stop a libvirt virtual interface</description>
</key>
<key name="unapplied-dev" type="b">
<default>true</default>
<summary>Confirm about unapplied device changes</summary>
<description>Whether we ask the user to apply or discard unapplied device changes</description>
</key>
<key name="delete-storage" type="b">
<default>true</default>
<summary>Confirm deleting storage</summary>
<description>Whether we require a confirmation on deleting storage</description>
</key>
</schema>
</schemalist>
Reference in New Issue Copy Permalink