Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<?xml version="1.0" encoding="UTF-8"?>
|
2019-05-24 08:34:55 +08:00
|
|
|
<!-- Generated with glade 3.22.1 -->
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<interface>
|
2019-04-03 05:48:16 +08:00
|
|
|
<requires lib="gtk+" version="3.22"/>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<object class="GtkWindow" id="snapshot-top-window">
|
2013-10-06 02:57:58 +08:00
|
|
|
<property name="width_request">600</property>
|
|
|
|
|
<property name="height_request">400</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<property name="can_focus">False</property>
|
2019-05-24 08:34:55 +08:00
|
|
|
<child type="titlebar">
|
|
|
|
|
<placeholder/>
|
|
|
|
|
</child>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<child>
|
|
|
|
|
<object class="GtkBox" id="snapshot-top-box">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
2013-10-01 02:28:43 +08:00
|
|
|
<property name="hexpand">True</property>
|
|
|
|
|
<property name="vexpand">True</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<property name="border_width">12</property>
|
|
|
|
|
<property name="orientation">vertical</property>
|
|
|
|
|
<property name="spacing">6</property>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkPaned" id="spaned1">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">True</property>
|
|
|
|
|
<property name="position">200</property>
|
|
|
|
|
<property name="position_set">True</property>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkScrolledWindow" id="scrolledwindow7">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">True</property>
|
2014-02-14 23:20:37 +08:00
|
|
|
<property name="hscrollbar_policy">never</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<property name="shadow_type">in</property>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkTreeView" id="snapshot-list">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">True</property>
|
|
|
|
|
<property name="headers_visible">False</property>
|
2013-10-06 02:57:58 +08:00
|
|
|
<signal name="button-press-event" handler="on_snapshot_list_button_press_event" swapped="no"/>
|
2016-07-29 17:44:46 +08:00
|
|
|
<signal name="row-activated" handler="on_snapshot_list_row_activated" swapped="no"/>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<child internal-child="selection">
|
2013-09-23 04:29:58 +08:00
|
|
|
<object class="GtkTreeSelection" id="treeview-selection">
|
|
|
|
|
<signal name="changed" handler="on_snapshot_list_changed" swapped="no"/>
|
|
|
|
|
</object>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</child>
|
2018-01-19 04:45:59 +08:00
|
|
|
<child internal-child="accessible">
|
|
|
|
|
<object class="AtkObject" id="snapshot-list-atkobject">
|
|
|
|
|
<property name="AtkObject::accessible-name">snapshot-list</property>
|
|
|
|
|
</object>
|
|
|
|
|
</child>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</object>
|
|
|
|
|
</child>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="resize">False</property>
|
2014-02-14 23:20:37 +08:00
|
|
|
<property name="shrink">False</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
<child>
|
2014-09-07 03:01:12 +08:00
|
|
|
<object class="GtkAlignment" id="alignment1">
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<property name="visible">True</property>
|
2014-09-07 03:01:12 +08:00
|
|
|
<property name="can_focus">False</property>
|
|
|
|
|
<property name="left_padding">12</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<child>
|
2014-09-07 03:01:12 +08:00
|
|
|
<object class="GtkNotebook" id="snapshot-notebook">
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<property name="visible">True</property>
|
2014-09-07 03:01:12 +08:00
|
|
|
<property name="can_focus">True</property>
|
|
|
|
|
<property name="show_border">False</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<child>
|
2014-09-07 03:01:12 +08:00
|
|
|
<object class="GtkBox" id="sbox3">
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
2014-09-07 03:01:12 +08:00
|
|
|
<property name="orientation">vertical</property>
|
|
|
|
|
<property name="spacing">12</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<child>
|
|
|
|
|
<object class="GtkGrid" id="sgrid1">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
|
|
|
|
<property name="row_spacing">6</property>
|
|
|
|
|
<property name="column_spacing">6</property>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkLabel" id="slabel94">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
2017-05-31 21:08:33 +08:00
|
|
|
<property name="halign">start</property>
|
2017-05-31 21:08:36 +08:00
|
|
|
<property name="valign">start</property>
|
2016-07-29 17:44:46 +08:00
|
|
|
<property name="label" translatable="yes">Description:</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="left_attach">0</property>
|
2014-02-02 00:25:35 +08:00
|
|
|
<property name="top_attach">5</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkScrolledWindow" id="scrolledwindow8">
|
|
|
|
|
<property name="height_request">80</property>
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">True</property>
|
|
|
|
|
<property name="hexpand">True</property>
|
|
|
|
|
<property name="shadow_type">in</property>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkTextView" id="snapshot-description">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">True</property>
|
2014-02-14 23:21:21 +08:00
|
|
|
<property name="left_margin">2</property>
|
|
|
|
|
<property name="right_margin">2</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</object>
|
|
|
|
|
</child>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="left_attach">1</property>
|
2014-02-02 00:25:35 +08:00
|
|
|
<property name="top_attach">5</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkLabel" id="label92">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
2017-05-31 21:08:33 +08:00
|
|
|
<property name="halign">start</property>
|
2013-11-10 07:00:00 +08:00
|
|
|
<property name="label" translatable="yes">VM State:</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="left_attach">0</property>
|
2014-02-02 00:25:35 +08:00
|
|
|
<property name="top_attach">3</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
<child>
|
2013-10-01 02:28:43 +08:00
|
|
|
<object class="GtkBox" id="hbox3">
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
|
|
|
|
<property name="spacing">3</property>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkImage" id="snapshot-status-icon">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
|
|
|
|
<property name="stock">gtk-cancel</property>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="expand">False</property>
|
|
|
|
|
<property name="fill">True</property>
|
|
|
|
|
<property name="position">0</property>
|
|
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkLabel" id="snapshot-status-text">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
2017-05-31 21:08:33 +08:00
|
|
|
<property name="halign">start</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<property name="label">Shut down</property>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="expand">False</property>
|
|
|
|
|
<property name="fill">True</property>
|
|
|
|
|
<property name="position">1</property>
|
|
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="left_attach">1</property>
|
2014-02-02 00:25:35 +08:00
|
|
|
<property name="top_attach">3</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkLabel" id="label93">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
2017-05-31 21:08:33 +08:00
|
|
|
<property name="halign">start</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<property name="label" translatable="yes">Timestamp:</property>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="left_attach">0</property>
|
2014-02-02 00:25:35 +08:00
|
|
|
<property name="top_attach">2</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkLabel" id="snapshot-timestamp">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
2017-05-31 21:08:33 +08:00
|
|
|
<property name="halign">start</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<property name="label">label</property>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="left_attach">1</property>
|
2014-02-02 00:25:35 +08:00
|
|
|
<property name="top_attach">2</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkLabel" id="snapshot-title">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
2017-05-31 21:08:33 +08:00
|
|
|
<property name="halign">start</property>
|
2013-10-01 04:04:11 +08:00
|
|
|
<property name="label"><b>snapshot 'foo'</b></property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<property name="use_markup">True</property>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="left_attach">0</property>
|
|
|
|
|
<property name="top_attach">0</property>
|
|
|
|
|
<property name="width">2</property>
|
|
|
|
|
</packing>
|
|
|
|
|
</child>
|
2013-10-01 05:53:55 +08:00
|
|
|
<child>
|
|
|
|
|
<object class="GtkLabel" id="label5">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
2017-05-31 21:08:33 +08:00
|
|
|
<property name="halign">start</property>
|
2013-10-01 05:53:55 +08:00
|
|
|
<property name="label" translatable="yes">Snapshot Mode:</property>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="left_attach">0</property>
|
2014-02-02 00:25:35 +08:00
|
|
|
<property name="top_attach">4</property>
|
2013-10-01 05:53:55 +08:00
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkLabel" id="snapshot-mode">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
2017-05-31 21:08:33 +08:00
|
|
|
<property name="halign">start</property>
|
2013-10-01 05:53:55 +08:00
|
|
|
<property name="label" translatable="yes">label</property>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="left_attach">1</property>
|
2014-02-02 00:25:35 +08:00
|
|
|
<property name="top_attach">4</property>
|
2013-10-01 05:53:55 +08:00
|
|
|
</packing>
|
|
|
|
|
</child>
|
2013-10-01 09:41:10 +08:00
|
|
|
<child>
|
|
|
|
|
<object class="GtkLabel" id="label7">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
2017-05-31 21:08:33 +08:00
|
|
|
<property name="halign">start</property>
|
2017-05-31 21:08:36 +08:00
|
|
|
<property name="valign">start</property>
|
2016-07-29 17:44:46 +08:00
|
|
|
<property name="label" translatable="yes">Screenshot:</property>
|
2013-10-01 09:41:10 +08:00
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="left_attach">0</property>
|
2014-02-02 00:25:35 +08:00
|
|
|
<property name="top_attach">6</property>
|
2013-10-01 09:41:10 +08:00
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkBox" id="box5">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkImage" id="snapshot-screenshot">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
|
|
|
|
<property name="stock">gtk-missing-image</property>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="expand">False</property>
|
|
|
|
|
<property name="fill">True</property>
|
|
|
|
|
<property name="position">0</property>
|
|
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkLabel" id="snapshot-screenshot-label">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
|
|
|
|
<property name="label" translatable="yes">No screenshot available</property>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="expand">False</property>
|
|
|
|
|
<property name="fill">True</property>
|
|
|
|
|
<property name="position">1</property>
|
|
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="left_attach">1</property>
|
2014-02-02 00:25:35 +08:00
|
|
|
<property name="top_attach">6</property>
|
2013-10-01 09:41:10 +08:00
|
|
|
</packing>
|
|
|
|
|
</child>
|
2014-02-02 00:25:35 +08:00
|
|
|
<child>
|
|
|
|
|
<object class="GtkBox" id="snapshot-is-current">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
|
|
|
|
<property name="spacing">3</property>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkImage" id="image2">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
|
|
|
|
<property name="stock">gtk-info</property>
|
|
|
|
|
<property name="icon_size">2</property>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="expand">False</property>
|
|
|
|
|
<property name="fill">True</property>
|
|
|
|
|
<property name="position">0</property>
|
|
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkLabel" id="label652">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
2017-05-31 21:08:33 +08:00
|
|
|
<property name="halign">start</property>
|
2014-02-02 00:25:35 +08:00
|
|
|
<property name="label" translatable="yes"><small><i>This was the most recently applied snapshot.</i></small></property>
|
|
|
|
|
<property name="use_markup">True</property>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="expand">False</property>
|
|
|
|
|
<property name="fill">True</property>
|
|
|
|
|
<property name="position">1</property>
|
|
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="left_attach">0</property>
|
|
|
|
|
<property name="top_attach">1</property>
|
|
|
|
|
<property name="width">2</property>
|
|
|
|
|
</packing>
|
|
|
|
|
</child>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</object>
|
2014-09-07 03:01:12 +08:00
|
|
|
<packing>
|
|
|
|
|
<property name="expand">False</property>
|
|
|
|
|
<property name="fill">True</property>
|
|
|
|
|
<property name="position">0</property>
|
|
|
|
|
</packing>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</child>
|
|
|
|
|
</object>
|
2014-09-07 03:01:12 +08:00
|
|
|
</child>
|
|
|
|
|
<child type="tab">
|
|
|
|
|
<object class="GtkLabel" id="label89">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
|
|
|
|
<property name="label">details</property>
|
|
|
|
|
</object>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<packing>
|
2014-09-07 03:01:12 +08:00
|
|
|
<property name="tab_fill">False</property>
|
|
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkLabel" id="snapshot-error-label">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
|
|
|
|
<property name="label">error label</property>
|
2018-01-19 04:45:59 +08:00
|
|
|
<child internal-child="accessible">
|
|
|
|
|
<object class="AtkObject" id="snapshot-error-label-atkobject">
|
|
|
|
|
<property name="AtkObject::accessible-name">snapshot-error-label</property>
|
|
|
|
|
</object>
|
|
|
|
|
</child>
|
2014-09-07 03:01:12 +08:00
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="position">1</property>
|
|
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
<child type="tab">
|
|
|
|
|
<object class="GtkLabel" id="label90">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
|
|
|
|
<property name="label">empty</property>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="position">1</property>
|
|
|
|
|
<property name="tab_fill">False</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
</object>
|
|
|
|
|
</child>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="resize">True</property>
|
|
|
|
|
<property name="shrink">True</property>
|
|
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="expand">True</property>
|
|
|
|
|
<property name="fill">True</property>
|
|
|
|
|
<property name="position">0</property>
|
|
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkBox" id="box2">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
|
|
|
|
<property name="spacing">6</property>
|
|
|
|
|
<child>
|
2013-10-01 02:28:43 +08:00
|
|
|
<object class="GtkBox" id="hbox10">
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
2014-07-31 19:26:56 +08:00
|
|
|
<child>
|
2014-09-21 23:44:01 +08:00
|
|
|
<object class="GtkButton" id="snapshot-add">
|
2014-07-31 19:26:56 +08:00
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">True</property>
|
|
|
|
|
<property name="receives_default">True</property>
|
2014-09-21 23:44:01 +08:00
|
|
|
<property name="has_tooltip">True</property>
|
|
|
|
|
<property name="tooltip_markup" translatable="yes">Create new snapshot</property>
|
|
|
|
|
<property name="tooltip_text" translatable="yes">Create new snapshot</property>
|
|
|
|
|
<signal name="clicked" handler="on_snapshot_add_clicked" swapped="no"/>
|
2014-07-31 19:26:56 +08:00
|
|
|
<child>
|
2014-09-21 23:44:01 +08:00
|
|
|
<object class="GtkImage" id="image1">
|
2014-07-31 19:26:56 +08:00
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
2014-09-21 23:44:01 +08:00
|
|
|
<property name="stock">gtk-add</property>
|
2014-07-31 19:26:56 +08:00
|
|
|
</object>
|
|
|
|
|
</child>
|
2018-01-19 04:45:59 +08:00
|
|
|
<child internal-child="accessible">
|
|
|
|
|
<object class="AtkObject" id="snapshot-add-atkobject">
|
|
|
|
|
<property name="AtkObject::accessible-name">snapshot-add</property>
|
|
|
|
|
</object>
|
|
|
|
|
</child>
|
2014-07-31 19:26:56 +08:00
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="expand">False</property>
|
2014-09-21 23:44:01 +08:00
|
|
|
<property name="fill">False</property>
|
2014-07-31 19:26:56 +08:00
|
|
|
<property name="position">0</property>
|
|
|
|
|
</packing>
|
|
|
|
|
</child>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<child>
|
2014-09-21 23:44:01 +08:00
|
|
|
<object class="GtkButton" id="snapshot-start">
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">True</property>
|
|
|
|
|
<property name="receives_default">True</property>
|
2014-09-21 23:44:01 +08:00
|
|
|
<property name="tooltip_markup" translatable="yes">Run selected snapshot</property>
|
|
|
|
|
<signal name="clicked" handler="on_snapshot_start_clicked" swapped="no"/>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<child>
|
2014-09-21 23:44:01 +08:00
|
|
|
<object class="GtkImage" id="someicon">
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
2014-09-21 23:44:01 +08:00
|
|
|
<property name="stock">gtk-media-play</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</object>
|
|
|
|
|
</child>
|
2018-01-19 04:45:59 +08:00
|
|
|
<child internal-child="accessible">
|
|
|
|
|
<object class="AtkObject" id="snapshot-start-atkobject">
|
|
|
|
|
<property name="AtkObject::accessible-name">snapshot-start</property>
|
|
|
|
|
</object>
|
|
|
|
|
</child>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="expand">False</property>
|
|
|
|
|
<property name="fill">False</property>
|
2014-07-31 19:26:56 +08:00
|
|
|
<property name="position">1</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
<child>
|
2014-09-21 23:44:01 +08:00
|
|
|
<object class="GtkButton" id="snapshot-refresh">
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">True</property>
|
|
|
|
|
<property name="receives_default">True</property>
|
2017-01-18 20:33:42 +08:00
|
|
|
<property name="tooltip_markup" translatable="yes">Refresh snapshot list</property>
|
2014-09-21 23:44:01 +08:00
|
|
|
<signal name="clicked" handler="on_snapshot_refresh_clicked" swapped="no"/>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<child>
|
2014-09-21 23:44:01 +08:00
|
|
|
<object class="GtkImage" id="image5">
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
2014-09-21 23:44:01 +08:00
|
|
|
<property name="stock">gtk-refresh</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</object>
|
|
|
|
|
</child>
|
2018-01-19 04:45:59 +08:00
|
|
|
<child internal-child="accessible">
|
|
|
|
|
<object class="AtkObject" id="snapshot-refresh-atkobject">
|
|
|
|
|
<property name="AtkObject::accessible-name">snapshot-refresh</property>
|
|
|
|
|
</object>
|
|
|
|
|
</child>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="expand">False</property>
|
2014-09-21 23:44:01 +08:00
|
|
|
<property name="fill">True</property>
|
2014-07-31 19:26:56 +08:00
|
|
|
<property name="position">2</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkButton" id="snapshot-delete">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">True</property>
|
|
|
|
|
<property name="receives_default">True</property>
|
|
|
|
|
<property name="has_tooltip">True</property>
|
|
|
|
|
<property name="tooltip_markup" translatable="yes">Delete selected snapshot</property>
|
|
|
|
|
<property name="tooltip_text" translatable="yes">Delete selected snapshot</property>
|
|
|
|
|
<signal name="clicked" handler="on_snapshot_delete_clicked" swapped="no"/>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkImage" id="image11">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
|
|
|
|
<property name="stock">gtk-delete</property>
|
|
|
|
|
</object>
|
|
|
|
|
</child>
|
2018-01-19 04:45:59 +08:00
|
|
|
<child internal-child="accessible">
|
|
|
|
|
<object class="AtkObject" id="snapshot-delete-atkobject">
|
|
|
|
|
<property name="AtkObject::accessible-name">snapshot-delete</property>
|
|
|
|
|
</object>
|
|
|
|
|
</child>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="expand">False</property>
|
|
|
|
|
<property name="fill">False</property>
|
2014-07-31 19:26:56 +08:00
|
|
|
<property name="position">3</property>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="expand">True</property>
|
|
|
|
|
<property name="fill">True</property>
|
|
|
|
|
<property name="position">0</property>
|
|
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkButtonBox" id="buttonbox1">
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">False</property>
|
|
|
|
|
<property name="spacing">6</property>
|
|
|
|
|
<property name="layout_style">end</property>
|
|
|
|
|
<child>
|
|
|
|
|
<object class="GtkButton" id="snapshot-apply">
|
|
|
|
|
<property name="label">gtk-apply</property>
|
|
|
|
|
<property name="visible">True</property>
|
|
|
|
|
<property name="can_focus">True</property>
|
|
|
|
|
<property name="receives_default">True</property>
|
|
|
|
|
<property name="has_tooltip">True</property>
|
|
|
|
|
<property name="tooltip_markup" translatable="yes">Save updated snapshot metadata</property>
|
|
|
|
|
<property name="tooltip_text" translatable="yes">Save updated snapshot metadata</property>
|
|
|
|
|
<property name="use_stock">True</property>
|
|
|
|
|
<signal name="clicked" handler="on_snapshot_apply_clicked" swapped="no"/>
|
2018-01-19 04:45:59 +08:00
|
|
|
<child internal-child="accessible">
|
|
|
|
|
<object class="AtkObject" id="snapshot-apply-atkobject">
|
|
|
|
|
<property name="AtkObject::accessible-name">snapshot-apply</property>
|
|
|
|
|
</object>
|
|
|
|
|
</child>
|
Initial snapshot support
This adds initial UI for managing snapshots: list, run/revert, delete,
add, and redefining (for changing <description>) supported, but currently
only for internal snapshots. The UI is mostly in its final form except for
some bells and whistles.
The real remaining question is what do we want to advertise and support.
Internal (qcow2) snapshots are by far the simplest to manage, very
mature, and already have the semantics we want.
However most recent libvirt and qemu work has been to facilitate
external snapshots, which are more extensible and can be performed
live, and with qemu-ga coordination for extra safety. However
they make things much harder for virt-manager at the moment.
Until we have a plan, this work should be considered experimental
and not be relied upon.
2013-08-02 22:18:47 +08:00
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="expand">False</property>
|
|
|
|
|
<property name="fill">True</property>
|
|
|
|
|
<property name="position">0</property>
|
|
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="expand">False</property>
|
|
|
|
|
<property name="fill">True</property>
|
|
|
|
|
<property name="position">1</property>
|
|
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
</object>
|
|
|
|
|
<packing>
|
|
|
|
|
<property name="expand">False</property>
|
|
|
|
|
<property name="fill">True</property>
|
|
|
|
|
<property name="position">1</property>
|
|
|
|
|
</packing>
|
|
|
|
|
</child>
|
|
|
|
|
</object>
|
|
|
|
|
</child>
|
|
|
|
|
</object>
|
|
|
|
|
</interface>
|
