2010-11-24 23:57:40 +03:00
<?xml version="1.0" encoding="UTF-8"?>
2018-03-13 23:37:46 +03:00
<!-- Generated with glade 3.20.3 -->
2012-02-02 02:26:46 +04:00
<interface>
2016-05-18 00:07:48 +03:00
<requires lib="gtk+" version="3.14"/>
2012-02-02 02:26:46 +04:00
<object class="GtkAccelGroup" id="accelgroup1"/>
<object class="GtkAdjustment" id="adjustment1">
<property name="lower">1</property>
<property name="upper">10240000</property>
<property name="value">50</property>
<property name="step_increment">1</property>
<property name="page_increment">25</property>
</object>
2012-11-09 12:43:45 +04:00
<object class="GtkAdjustment" id="adjustment10">
<property name="upper">1000000000</property>
<property name="step_increment">1024</property>
</object>
<object class="GtkAdjustment" id="adjustment11">
<property name="upper">1000000000</property>
<property name="step_increment">10</property>
</object>
<object class="GtkAdjustment" id="adjustment12">
<property name="upper">1000000000</property>
<property name="step_increment">1024</property>
</object>
<object class="GtkAdjustment" id="adjustment13">
<property name="upper">1000000000</property>
<property name="step_increment">10</property>
</object>
2014-02-21 14:13:11 +04:00
<object class="GtkAdjustment" id="adjustment14">
<property name="upper">65536</property>
<property name="step_increment">1</property>
<property name="page_increment">25</property>
</object>
<object class="GtkAdjustment" id="adjustment15">
<property name="upper">65536</property>
<property name="step_increment">1</property>
<property name="page_increment">25</property>
</object>
<object class="GtkAdjustment" id="adjustment16">
2015-08-10 20:14:37 +03:00
<property name="upper">10000000</property>
2014-02-21 14:13:11 +04:00
<property name="value">1000</property>
<property name="step_increment">1</property>
<property name="page_increment">25</property>
</object>
<object class="GtkAdjustment" id="adjustment17">
2015-08-10 20:14:37 +03:00
<property name="upper">10000000</property>
2014-02-21 14:13:11 +04:00
<property name="value">1000</property>
<property name="step_increment">1</property>
<property name="page_increment">25</property>
</object>
<object class="GtkAdjustment" id="adjustment18">
<property name="upper">65536</property>
<property name="value">10</property>
<property name="step_increment">1</property>
<property name="page_increment">25</property>
</object>
<object class="GtkAdjustment" id="adjustment19">
<property name="upper">65536</property>
<property name="value">10</property>
<property name="step_increment">1</property>
<property name="page_increment">25</property>
</object>
2012-02-02 02:26:46 +04:00
<object class="GtkAdjustment" id="adjustment2">
<property name="lower">1</property>
<property name="upper">10240000</property>
<property name="value">50</property>
<property name="step_increment">1</property>
<property name="page_increment">25</property>
</object>
<object class="GtkAdjustment" id="adjustment3">
<property name="lower">1</property>
<property name="upper">256</property>
<property name="value">1</property>
<property name="step_increment">1</property>
<property name="page_increment">10</property>
</object>
<object class="GtkAdjustment" id="adjustment4">
<property name="lower">1</property>
<property name="upper">256</property>
<property name="value">1</property>
<property name="step_increment">1</property>
<property name="page_increment">10</property>
</object>
<object class="GtkAdjustment" id="adjustment5">
<property name="lower">1</property>
<property name="upper">256</property>
<property name="value">1</property>
<property name="step_increment">1</property>
<property name="page_increment">10</property>
</object>
<object class="GtkAdjustment" id="adjustment6">
<property name="lower">1</property>
<property name="upper">1024</property>
<property name="value">1</property>
<property name="step_increment">1</property>
<property name="page_increment">2</property>
</object>
<object class="GtkAdjustment" id="adjustment7">
<property name="lower">1</property>
<property name="upper">1024</property>
<property name="value">2</property>
<property name="step_increment">1</property>
<property name="page_increment">2</property>
</object>
2013-02-17 17:40:37 +04:00
<object class="GtkAdjustment" id="adjustment8">
<property name="upper">1000000000</property>
<property name="step_increment">1024</property>
</object>
<object class="GtkAdjustment" id="adjustment9">
<property name="upper">1000000000</property>
<property name="step_increment">10</property>
</object>
2013-09-22 20:18:49 +04:00
<object class="GtkImage" id="image70">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="stock">gtk-apply</property>
</object>
<object class="GtkImage" id="image80">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="stock">gtk-add</property>
</object>
2012-02-02 02:26:46 +04:00
<object class="GtkWindow" id="vmm-details">
<property name="can_focus">False</property>
2008-10-31 17:18:55 +03:00
<property name="title" translatable="yes">Virtual Machine</property>
2009-02-09 22:55:18 +03:00
<property name="default_width">800</property>
<property name="default_height">600</property>
2012-02-02 02:26:46 +04:00
<accel-groups>
<group name="accelgroup1"/>
</accel-groups>
<signal name="configure-event" handler="on_vmm_details_configure_event" swapped="no"/>
<signal name="delete-event" handler="on_vmm_details_delete_event" swapped="no"/>
2008-10-31 17:18:55 +03:00
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="vbox2">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</property>
2008-10-31 17:18:55 +03:00
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkMenuBar" id="details-menubar">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2008-10-31 17:18:55 +03:00
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkMenuItem" id="file1">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2008-10-31 17:18:55 +03:00
<property name="label" translatable="yes">_File</property>
<property name="use_underline">True</property>
2012-02-02 02:26:46 +04:00
<child type="submenu">
<object class="GtkMenu" id="file1_menu">
<property name="can_focus">False</property>
2008-10-31 17:18:55 +03:00
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkMenuItem" id="view_manager">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2009-11-18 01:47:34 +03:00
<property name="label" translatable="yes">_View Manager</property>
2008-10-31 17:18:55 +03:00
<property name="use_underline">True</property>
2012-02-02 02:26:46 +04:00
<signal name="activate" handler="on_details_menu_view_manager_activate" swapped="no"/>
</object>
2008-10-31 17:18:55 +03:00
</child>
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkSeparatorMenuItem" id="separator15">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
</object>
2008-10-31 17:18:55 +03:00
</child>
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkImageMenuItem" id="close4">
2009-07-07 20:16:03 +04:00
<property name="label">gtk-close</property>
2009-09-23 18:45:44 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2008-10-31 17:18:55 +03:00
<property name="use_underline">True</property>
<property name="use_stock">True</property>
2012-02-02 02:26:46 +04:00
<property name="accel_group">accelgroup1</property>
<signal name="activate" handler="on_details_menu_close_activate" swapped="no"/>
</object>
2008-10-31 17:18:55 +03:00
</child>
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkImageMenuItem" id="quit3">
2009-07-07 20:16:03 +04:00
<property name="label">gtk-quit</property>
2009-09-23 18:45:44 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2008-10-31 17:18:55 +03:00
<property name="use_underline">True</property>
<property name="use_stock">True</property>
2012-02-02 02:26:46 +04:00
<property name="accel_group">accelgroup1</property>
<signal name="activate" handler="on_details_menu_quit_activate" swapped="no"/>
</object>
2008-10-31 17:18:55 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2008-10-31 17:18:55 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2008-10-31 17:18:55 +03:00
</child>
<child>
2013-09-22 23:44:58 +04:00
<object class="GtkMenuItem" id="details-vm-menu">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2008-10-31 17:18:55 +03:00
<property name="label" translatable="yes">Virtual _Machine</property>
<property name="use_underline">True</property>
2013-07-01 22:33:59 +04:00
<signal name="activate" handler="on_details_menu_virtual_manager_activate" swapped="no"/>
2012-02-02 02:26:46 +04:00
<child type="submenu">
<object class="GtkMenu" id="virtual_machine1_menu">
<property name="can_focus">False</property>
2013-06-18 00:29:51 +04:00
<child>
<object class="GtkSeparatorMenuItem" id="separator2">
<property name="visible">True</property>
<property name="can_focus">False</property>
</object>
</child>
2008-10-31 17:18:55 +03:00
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkMenuItem" id="details-menu-vm-screenshot">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2008-10-31 17:18:55 +03:00
<property name="label" translatable="yes">_Take Screenshot</property>
<property name="use_underline">True</property>
2012-02-02 02:26:46 +04:00
<signal name="activate" handler="on_details_menu_screenshot_activate" swapped="no"/>
</object>
2008-10-31 17:18:55 +03:00
</child>
2013-07-01 22:33:59 +04:00
<child>
<object class="GtkMenuItem" id="details-menu-usb-redirection">
<property name="visible">True</property>
<property name="can_focus">False</property>
2014-02-05 00:27:22 +04:00
<property name="tooltip_text" translatable="yes">Redirect host USB device to virtual machine with SPICE graphics.</property>
2013-07-01 22:33:59 +04:00
<property name="label" translatable="yes">_Redirect USB device</property>
<property name="use_underline">True</property>
<signal name="activate" handler="on_details_menu_usb_redirection" swapped="no"/>
</object>
</child>
2012-02-02 02:26:46 +04:00
</object>
2008-10-31 17:18:55 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2008-10-31 17:18:55 +03:00
</child>
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkMenuItem" id="view2">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2008-10-31 17:18:55 +03:00
<property name="label" translatable="yes">_View</property>
<property name="use_underline">True</property>
2012-02-02 02:26:46 +04:00
<child type="submenu">
<object class="GtkMenu" id="view2_menu">
<property name="can_focus">False</property>
2009-10-21 20:01:53 +04:00
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkRadioMenuItem" id="details-menu-view-console">
2009-10-21 20:01:53 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2009-11-18 01:47:34 +03:00
<property name="label" translatable="yes">_Console</property>
2009-10-21 20:01:53 +04:00
<property name="use_underline">True</property>
<property name="active">True</property>
<property name="draw_as_radio">True</property>
2012-02-02 02:26:46 +04:00
<signal name="toggled" handler="on_details_menu_view_console_toggled" swapped="no"/>
</object>
2009-10-21 20:01:53 +04:00
</child>
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkRadioMenuItem" id="details-menu-view-details">
2009-10-21 20:01:53 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2009-11-18 01:47:34 +03:00
<property name="label" translatable="yes">_Details</property>
2009-10-21 20:01:53 +04:00
<property name="use_underline">True</property>
<property name="draw_as_radio">True</property>
<property name="group">details-menu-view-console</property>
2012-02-02 02:26:46 +04:00
<signal name="toggled" handler="on_details_menu_view_details_toggled" swapped="no"/>
</object>
2009-10-21 20:01:53 +04:00
</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 18:18:47 +04:00
<child>
<object class="GtkRadioMenuItem" id="details-menu-view-snapshots">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">Sna_pshots</property>
<property name="use_underline">True</property>
<property name="draw_as_radio">True</property>
<property name="group">details-menu-view-console</property>
<signal name="toggled" handler="on_details_menu_view_snapshots_toggled" swapped="no"/>
</object>
</child>
2009-10-21 20:01:53 +04:00
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkSeparatorMenuItem" id="menuitem2">
2009-10-21 20:01:53 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
</object>
2009-10-21 20:01:53 +04:00
</child>
2008-10-31 17:18:55 +03:00
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkCheckMenuItem" id="details-menu-view-fullscreen">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2009-11-18 01:47:34 +03:00
<property name="label" translatable="yes">_Fullscreen</property>
2008-10-31 17:18:55 +03:00
<property name="use_underline">True</property>
2012-02-02 02:26:46 +04:00
<signal name="activate" handler="on_details_menu_view_fullscreen_activate" swapped="no"/>
</object>
2008-10-31 17:18:55 +03:00
</child>
2009-11-29 04:07:01 +03:00
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkMenuItem" id="detains-menu-view-size-to-vm">
2009-11-29 04:07:01 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2009-11-29 04:07:01 +03:00
<property name="label" translatable="yes">_Resize to VM</property>
<property name="use_underline">True</property>
2012-02-02 02:26:46 +04:00
<signal name="activate" handler="on_details_menu_view_size_to_vm_activate" swapped="no"/>
</object>
2009-11-29 04:07:01 +03:00
</child>
2008-10-31 17:18:55 +03:00
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkMenuItem" id="menuitem1">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2009-11-18 01:47:34 +03:00
<property name="label" translatable="yes">_Scale Display</property>
2008-10-31 17:18:55 +03:00
<property name="use_underline">True</property>
2012-02-02 02:26:46 +04:00
<child type="submenu">
<object class="GtkMenu" id="menu1">
2009-02-24 02:50:27 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2009-02-24 02:50:27 +03:00
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkRadioMenuItem" id="details-menu-view-scale-always">
2009-02-24 02:50:27 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2009-11-18 01:47:34 +03:00
<property name="label" translatable="yes">_Always</property>
2009-02-24 02:50:27 +03:00
<property name="use_underline">True</property>
<property name="active">True</property>
2012-02-02 02:26:46 +04:00
<signal name="toggled" handler="on_details_menu_view_scale_always_toggled" swapped="no"/>
</object>
2009-02-24 02:50:27 +03:00
</child>
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkRadioMenuItem" id="details-menu-view-scale-fullscreen">
2009-02-24 02:50:27 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2009-11-18 01:47:34 +03:00
<property name="label" translatable="yes">_Only when Fullscreen</property>
2009-02-24 02:50:27 +03:00
<property name="use_underline">True</property>
<property name="draw_as_radio">True</property>
<property name="group">details-menu-view-scale-always</property>
2012-02-02 02:26:46 +04:00
<signal name="toggled" handler="on_details_menu_view_scale_fullscreen_toggled" swapped="no"/>
</object>
2009-02-24 02:50:27 +03:00
</child>
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkRadioMenuItem" id="details-menu-view-scale-never">
2009-02-24 02:50:27 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2009-11-18 01:47:34 +03:00
<property name="label" translatable="yes">_Never</property>
2009-02-24 02:50:27 +03:00
<property name="use_underline">True</property>
<property name="draw_as_radio">True</property>
<property name="group">details-menu-view-scale-always</property>
2012-02-02 02:26:46 +04:00
<signal name="toggled" handler="on_details_menu_view_scale_never_toggled" swapped="no"/>
</object>
2009-02-24 02:50:27 +03:00
</child>
2014-01-31 18:13:53 +04:00
<child>
<object class="GtkSeparatorMenuItem" id="menuitem3">
<property name="visible">True</property>
<property name="can_focus">False</property>
</object>
</child>
<child>
<object class="GtkCheckMenuItem" id="details-menu-view-resizeguest">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">Auto _resize VM with window</property>
<property name="use_underline">True</property>
<signal name="toggled" handler="on_details_menu_view_resizeguest_toggled" swapped="no"/>
</object>
</child>
2012-02-02 02:26:46 +04:00
</object>
2009-02-24 02:50:27 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2008-10-31 17:18:55 +03:00
</child>
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkMenuItem" id="details-menu-view-serial-list">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2009-11-18 01:47:34 +03:00
<property name="label" translatable="yes">_Text Consoles</property>
2008-10-31 17:18:55 +03:00
<property name="use_underline">True</property>
2012-02-02 02:26:46 +04:00
</object>
2008-10-31 17:18:55 +03:00
</child>
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkSeparatorMenuItem" id="separator7">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
</object>
2008-10-31 17:18:55 +03:00
</child>
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkCheckMenuItem" id="details-menu-view-toolbar">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2009-11-18 01:47:34 +03:00
<property name="label" translatable="yes">T_oolbar</property>
2008-10-31 17:18:55 +03:00
<property name="use_underline">True</property>
<property name="active">True</property>
2012-02-02 02:26:46 +04:00
<signal name="activate" handler="on_details_menu_view_toolbar_activate" swapped="no"/>
</object>
2008-10-31 17:18:55 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2008-10-31 17:18:55 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2008-10-31 17:18:55 +03:00
</child>
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkMenuItem" id="details-menu-send-key">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2009-11-17 23:06:15 +03:00
<property name="label" translatable="yes">Send _Key</property>
2008-10-31 17:18:55 +03:00
<property name="use_underline">True</property>
2012-02-02 02:26:46 +04:00
</object>
2008-10-31 17:18:55 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2008-10-31 17:18:55 +03:00
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
2009-09-23 18:45:44 +04:00
<property name="position">0</property>
2008-10-31 17:18:55 +03:00
</packing>
</child>
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="toolbar-box">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2008-10-31 17:18:55 +03:00
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkToolbar" id="details-toolbar">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2009-07-28 17:40:43 +04:00
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkRadioToolButton" id="control-vm-console">
2009-07-28 17:40:43 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
<property name="tooltip_text" translatable="yes">Show the graphical console</property>
2009-07-28 17:40:43 +04:00
<property name="label" translatable="yes">Console</property>
<property name="icon_name">icon_console</property>
<property name="active">True</property>
2012-02-02 02:26:46 +04:00
<signal name="toggled" handler="on_control_vm_console_toggled" swapped="no"/>
</object>
2009-07-28 17:40:43 +04:00
<packing>
2009-09-23 18:45:44 +04:00
<property name="expand">False</property>
2009-07-28 17:40:43 +04:00
<property name="homogeneous">True</property>
</packing>
</child>
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkRadioToolButton" id="control-vm-details">
2009-07-28 17:40:43 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
<property name="tooltip_text" translatable="yes">Show virtual hardware details</property>
2009-07-28 17:40:43 +04:00
<property name="label" translatable="yes">Details</property>
<property name="stock_id">gtk-info</property>
<property name="group">control-vm-console</property>
2012-02-02 02:26:46 +04:00
<signal name="toggled" handler="on_control_vm_details_toggled" swapped="no"/>
</object>
2009-07-28 17:40:43 +04:00
<packing>
2009-09-23 18:45:44 +04:00
<property name="expand">False</property>
2009-07-28 17:40:43 +04:00
<property name="homogeneous">True</property>
</packing>
</child>
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkSeparatorToolItem" id="toolbutton3">
2009-07-28 17:40:43 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
</object>
2009-07-28 17:40:43 +04:00
<packing>
2009-09-23 18:45:44 +04:00
<property name="expand">False</property>
2009-07-28 17:40:43 +04:00
<property name="homogeneous">True</property>
</packing>
</child>
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkToolButton" id="control-run">
2009-07-28 17:40:43 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
<property name="tooltip_text" translatable="yes">Power on the virtual machine</property>
2009-07-28 17:40:43 +04:00
<property name="label" translatable="yes">Run</property>
<property name="use_underline">True</property>
<property name="stock_id">gtk-media-play</property>
2012-02-02 02:26:46 +04:00
<signal name="clicked" handler="on_control_run_clicked" swapped="no"/>
</object>
2009-07-28 17:40:43 +04:00
<packing>
2009-09-23 18:45:44 +04:00
<property name="expand">False</property>
2009-07-28 17:40:43 +04:00
<property name="homogeneous">True</property>
</packing>
</child>
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkToggleToolButton" id="control-pause">
2009-07-28 17:40:43 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
<property name="tooltip_text" translatable="yes">Pause the virtual machine</property>
2009-07-28 17:40:43 +04:00
<property name="label" translatable="yes">Pause</property>
<property name="use_underline">True</property>
<property name="stock_id">gtk-media-pause</property>
2012-02-02 02:26:46 +04:00
<signal name="toggled" handler="on_control_pause_toggled" swapped="no"/>
</object>
2009-07-28 17:40:43 +04:00
<packing>
2009-09-23 18:45:44 +04:00
<property name="expand">False</property>
2009-07-28 17:40:43 +04:00
<property name="homogeneous">True</property>
</packing>
</child>
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkMenuToolButton" id="control-shutdown">
2009-07-28 17:40:43 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-03-06 23:16:13 +03:00
<property name="tooltip_text" translatable="yes">Shut down the virtual machine</property>
<property name="label" translatable="yes">_Shut Down</property>
2009-07-28 17:40:43 +04:00
<property name="use_underline">True</property>
2012-02-02 02:26:46 +04:00
<signal name="clicked" handler="on_control_shutdown_clicked" swapped="no"/>
</object>
2009-09-23 18:45:44 +04:00
<packing>
<property name="expand">False</property>
2014-01-12 00:08:00 +04:00
<property name="homogeneous">False</property>
2009-09-23 18:45:44 +04:00
</packing>
2009-07-28 17:40:43 +04:00
</child>
2010-02-07 20:18:28 +03:00
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkSeparatorToolItem" id="toolbutton7">
2010-02-07 20:18:28 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
</object>
2010-02-07 20:18:28 +03:00
<packing>
<property name="expand">False</property>
<property name="homogeneous">True</property>
</packing>
</child>
2013-10-01 04:59:15 +04:00
<child>
<object class="GtkRadioToolButton" id="control-snapshots">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">Snapshots</property>
<property name="icon_name">vm_clone_wizard</property>
<property name="group">control-vm-console</property>
<signal name="toggled" handler="on_control_snapshots_toggled" swapped="no"/>
</object>
<packing>
<property name="expand">False</property>
<property name="homogeneous">True</property>
</packing>
</child>
2010-02-07 20:18:28 +03:00
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkToggleToolButton" id="control-fullscreen">
2010-02-07 20:18:28 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
<property name="tooltip_text" translatable="yes">Switch to fullscreen view</property>
2013-10-01 04:59:15 +04:00
<property name="halign">end</property>
2010-02-07 20:18:28 +03:00
<property name="stock_id">gtk-fullscreen</property>
2012-02-02 02:26:46 +04:00
<signal name="toggled" handler="on_control_fullscreen_toggled" swapped="no"/>
</object>
2010-02-07 20:18:28 +03:00
<packing>
2013-10-01 04:59:15 +04:00
<property name="expand">True</property>
2010-02-07 20:18:28 +03:00
<property name="homogeneous">True</property>
</packing>
</child>
2012-02-02 02:26:46 +04:00
</object>
2009-09-23 18:45:44 +04:00
<packing>
2012-02-02 02:26:46 +04:00
<property name="expand">True</property>
<property name="fill">True</property>
2009-09-23 18:45:44 +04:00
<property name="position">0</property>
</packing>
2008-10-31 17:18:55 +03:00
</child>
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkToolbar" id="customize-toolbar">
<property name="can_focus">False</property>
2010-08-25 00:31:55 +04:00
<property name="toolbar_style">both-horiz</property>
2009-07-28 17:40:43 +04:00
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkToolButton" id="details-finish-customize">
2009-07-28 17:40:43 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
<property name="tooltip_text" translatable="yes">Begin Installation</property>
2010-08-25 00:31:55 +04:00
<property name="is_important">True</property>
<property name="label" translatable="yes">_Begin Installation</property>
2010-02-07 20:18:28 +03:00
<property name="use_underline">True</property>
<property name="stock_id">gtk-apply</property>
2012-02-02 02:26:46 +04:00
<signal name="clicked" handler="on_details_customize_finish_clicked" swapped="no"/>
</object>
2009-07-28 17:40:43 +04:00
<packing>
2009-09-23 18:45:44 +04:00
<property name="expand">False</property>
2009-07-28 17:40:43 +04:00
<property name="homogeneous">True</property>
</packing>
</child>
2011-07-19 05:31:06 +04:00
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkToolButton" id="details-cancel-customize">
2011-07-19 05:31:06 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2011-07-19 05:31:06 +04:00
<property name="is_important">True</property>
2015-05-03 23:53:43 +03:00
<property name="label" translatable="yes">_Cancel Installation</property>
2011-07-19 05:31:06 +04:00
<property name="use_underline">True</property>
<property name="stock_id">gtk-cancel</property>
2012-02-02 02:26:46 +04:00
<signal name="clicked" handler="on_details_cancel_customize_clicked" swapped="no"/>
</object>
2011-07-19 05:31:06 +04:00
<packing>
<property name="expand">False</property>
<property name="homogeneous">True</property>
</packing>
</child>
2012-02-02 02:26:46 +04:00
</object>
2008-10-31 17:18:55 +03:00
<packing>
2012-02-02 02:26:46 +04:00
<property name="expand">True</property>
<property name="fill">True</property>
2009-07-28 17:40:43 +04:00
<property name="position">1</property>
2008-10-31 17:18:55 +03:00
</packing>
</child>
2012-02-02 02:26:46 +04:00
</object>
2008-10-31 17:18:55 +03:00
<packing>
<property name="expand">False</property>
2012-02-02 02:26:46 +04:00
<property name="fill">True</property>
2008-10-31 17:18:55 +03:00
<property name="position">1</property>
</packing>
</child>
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkNotebook" id="details-pages">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="show_border">False</property>
2012-02-02 02:26:46 +04:00
<signal name="switch-page" handler="on_details_pages_switch_page" after="yes" swapped="no"/>
2008-10-31 17:18:55 +03:00
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="hbox1">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2009-11-02 05:39:48 +03:00
<property name="border_width">12</property>
2009-07-09 22:35:36 +04:00
<property name="spacing">12</property>
2008-10-31 17:18:55 +03:00
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="vbox53">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</property>
2009-07-09 22:35:36 +04:00
<property name="spacing">6</property>
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkScrolledWindow" id="scrolledwindow5">
2009-07-09 22:35:36 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
2009-09-23 18:45:44 +04:00
<property name="hscrollbar_policy">never</property>
<property name="shadow_type">in</property>
2009-07-09 22:35:36 +04:00
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkTreeView" id="hw-list">
2009-07-09 22:35:36 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="headers_visible">False</property>
2012-02-02 02:26:46 +04:00
<signal name="button-press-event" handler="on_hw_list_button_press_event" swapped="no"/>
<child internal-child="selection">
2013-09-23 00:29:58 +04:00
<object class="GtkTreeSelection" id="treeview-selection1">
<signal name="changed" handler="on_hw_list_changed" swapped="no"/>
</object>
2012-02-02 02:26:46 +04:00
</child>
2015-09-14 21:11:04 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="hw-list-atkobject">
2015-09-24 00:01:41 +03:00
<property name="AtkObject::accessible-name">hw-list</property>
2015-09-14 21:11:04 +03:00
</object>
</child>
</object>
</child>
<child internal-child="accessible">
<object class="AtkObject" id="scrolledwindow5-atkobject">
2015-09-24 00:01:41 +03:00
<property name="AtkObject::accessible-name">hw-list-scroll</property>
2012-02-02 02:26:46 +04:00
</object>
2009-07-09 22:35:36 +04:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2009-09-23 18:45:44 +04:00
<packing>
2012-02-02 02:26:46 +04:00
<property name="expand">True</property>
<property name="fill">True</property>
2009-09-23 18:45:44 +04:00
<property name="position">0</property>
</packing>
2009-07-09 22:35:36 +04:00
</child>
2008-10-31 17:18:55 +03:00
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkButton" id="add-hardware-button">
2009-11-17 23:06:15 +03:00
<property name="label" translatable="yes">A_dd Hardware</property>
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2009-02-09 22:55:18 +03:00
<property name="can_focus">True</property>
2009-09-23 18:45:44 +04:00
<property name="receives_default">False</property>
2013-09-22 20:18:49 +04:00
<property name="image">image80</property>
2009-11-17 23:06:15 +03:00
<property name="use_underline">True</property>
2012-02-02 02:26:46 +04:00
<signal name="clicked" handler="on_add_hardware_button_clicked" swapped="no"/>
2015-09-09 16:49:45 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="add-hardware-button-atkobject">
2015-09-24 00:01:41 +03:00
<property name="AtkObject::accessible-name">add-hardware</property>
2015-09-09 16:49:45 +03:00
</object>
</child>
2012-02-02 02:26:46 +04:00
</object>
2009-07-09 22:35:36 +04:00
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">1</property>
</packing>
</child>
2012-02-02 02:26:46 +04:00
</object>
2009-07-09 22:35:36 +04:00
<packing>
<property name="expand">False</property>
2012-02-02 02:26:46 +04:00
<property name="fill">True</property>
2009-09-23 18:45:44 +04:00
<property name="position">0</property>
2009-07-09 22:35:36 +04:00
</packing>
</child>
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="vbox1">
2009-07-09 22:35:36 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</property>
2009-07-09 22:35:36 +04:00
<property name="spacing">6</property>
<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 18:18:47 +04:00
<object class="GtkNotebook" id="hw-panel">
2009-07-09 22:35:36 +04:00
<property name="visible">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 18:18:47 +04:00
<property name="can_focus">True</property>
2014-09-20 18:21:27 +04:00
<property name="tab_pos">left</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 18:18:47 +04:00
<property name="show_border">False</property>
2008-10-31 17:18:55 +03:00
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="vbox6">
2008-10-31 17:18:55 +03:00
<property name="visible">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 18:18:47 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</property>
2014-01-26 23:07:35 +04:00
<property name="spacing">12</property>
2008-10-31 17:18:55 +03:00
<child>
2014-01-26 23:07:35 +04:00
<object class="GtkFrame" id="frame2">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2014-01-26 23:07:35 +04:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
2010-12-12 00:40:24 +03:00
<child>
2014-01-26 23:07:35 +04:00
<object class="GtkAlignment" id="alignment9">
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2014-01-26 23:07:35 +04:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
2010-12-12 00:40:24 +03:00
<child>
2014-01-26 23:07:35 +04:00
<object class="GtkGrid" id="table5">
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2014-01-26 23:07:35 +04:00
<property name="border_width">3</property>
<property name="row_spacing">6</property>
<property name="column_spacing">6</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 18:18:47 +04:00
<child>
2014-01-26 23:07:35 +04:00
<object class="GtkLabel" id="label44">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-01-26 23:07:35 +04:00
<property name="label" translatable="yes">Status:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label68">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-01-26 23:07:35 +04:00
<property name="label" translatable="yes">UUID:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label43">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-01-26 23:07:35 +04:00
<property name="label" translatable="yes">_Name:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">overview-name</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="overview-uuid">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-01-26 23:07:35 +04:00
<property name="label">8ffc926e-b4da-b3b6-552f-e37b92f918d5</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkEntry" id="overview-name">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="hexpand">False</property>
<signal name="changed" handler="on_overview_name_changed" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="title-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-12-12 13:31:11 +03:00
<property name="label" translatable="yes">T_itle:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">overview-title</property>
2014-01-26 23:07:35 +04:00
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">3</property>
</packing>
</child>
<child>
<object class="GtkEntry" id="overview-title">
<property name="visible">True</property>
<property name="can_focus">True</property>
<signal name="changed" handler="on_overview_title_changed" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">3</property>
</packing>
</child>
<child>
<object class="GtkGrid" id="grid1">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="column_spacing">3</property>
2013-11-25 19:10:03 +04:00
<child>
2014-01-26 23:07:35 +04:00
<object class="GtkLabel" id="overview-status-text">
2013-11-25 19:10:03 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-01-26 23:07:35 +04:00
<property name="label" translatable="yes">Shut down</property>
2013-11-25 19:10:03 +04:00
</object>
<packing>
<property name="left_attach">1</property>
2014-01-12 23:25:09 +04:00
<property name="top_attach">0</property>
2013-11-25 19:10:03 +04:00
</packing>
</child>
<child>
2014-01-26 23:07:35 +04:00
<object class="GtkImage" id="overview-status-icon">
<property name="width_request">22</property>
2013-11-25 19:10:03 +04:00
<property name="visible">True</property>
2014-01-12 23:25:09 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-01-26 23:07:35 +04:00
<property name="stock">gtk-missing-image</property>
2013-11-25 19:10:03 +04:00
</object>
<packing>
2014-01-12 23:25:09 +04:00
<property name="left_attach">0</property>
2014-01-26 23:07:35 +04:00
<property name="top_attach">0</property>
2013-11-25 19:10:03 +04:00
</packing>
2011-07-18 22:53:57 +04:00
</child>
2014-01-26 23:07:35 +04:00
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label24">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2017-05-31 16:08:36 +03:00
<property name="valign">start</property>
2015-03-17 04:26:47 +03:00
<property name="label" translatable="yes">D_escription:</property>
2014-12-12 13:31:11 +03:00
<property name="use_underline">True</property>
<property name="mnemonic_widget">overview-description</property>
2014-01-26 23:07:35 +04:00
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">4</property>
</packing>
</child>
<child>
<object class="GtkScrolledWindow" id="scrolledwindow2">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="shadow_type">in</property>
<property name="min_content_height">80</property>
2013-09-24 15:02:27 +04:00
<child>
2014-01-26 23:07:35 +04:00
<object class="GtkTextView" id="overview-description">
2013-09-24 15:02:27 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
2014-01-26 23:07:35 +04:00
<property name="hexpand">True</property>
<property name="wrap_mode">word</property>
2014-02-14 19:21:21 +04:00
<property name="left_margin">2</property>
<property name="right_margin">2</property>
2013-09-24 15:02:27 +04:00
</object>
</child>
</object>
2014-01-26 23:07:35 +04:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">4</property>
</packing>
2011-07-18 22:53:57 +04:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2011-07-18 22:53:57 +04:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2011-07-18 22:53:57 +04:00
</child>
2014-01-26 23:07:35 +04:00
<child type="label">
<object class="GtkLabel" id="label50">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>Basic Details</b></property>
<property name="use_markup">True</property>
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkFrame" id="frame7">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
2009-05-12 21:09:08 +04:00
<child>
2014-01-26 23:07:35 +04:00
<object class="GtkAlignment" id="alignment6">
2009-05-12 21:09:08 +04:00
<property name="visible">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 18:18:47 +04:00
<property name="can_focus">False</property>
2014-01-26 23:07:35 +04:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
2009-05-12 21:09:08 +04:00
<child>
2014-01-26 23:07:35 +04:00
<object class="GtkGrid" id="table1">
2009-05-12 21:09:08 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2014-01-26 23:07:35 +04:00
<property name="border_width">3</property>
<property name="row_spacing">6</property>
<property name="column_spacing">6</property>
<child>
<object class="GtkLabel" id="label11">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-01-26 23:07:35 +04:00
<property name="label" translatable="yes">Hypervisor:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label12">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-01-26 23:07:35 +04:00
<property name="label" translatable="yes">Architecture:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="overview-hv">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-01-26 23:07:35 +04:00
<property name="label">foo</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="overview-arch">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-01-26 23:07:35 +04:00
<property name="label">foo</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="overview-emulator">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-02-17 19:28:02 +04:00
<property name="label">foooooooooooooo</property>
2014-01-26 23:07:35 +04:00
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label13">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-01-26 23:07:35 +04:00
<property name="label" translatable="yes">Emulator:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
2015-02-22 01:54:15 +03:00
<object class="GtkLabel" id="machine-type-title">
2014-01-26 23:07:35 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2014-09-18 01:25:03 +04:00
<property name="valign">start</property>
2014-01-26 23:07:35 +04:00
<property name="label" translatable="yes">Machine _Type: </property>
<property name="use_underline">True</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">3</property>
</packing>
</child>
2014-06-01 04:13:08 +04:00
<child>
<object class="GtkLabel" id="overview-chipset-title">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-09-18 01:25:03 +04:00
<property name="valign">start</property>
2014-06-01 04:13:08 +04:00
<property name="label" translatable="yes">Chipse_t:</property>
<property name="use_underline">True</property>
<property name="ellipsize">middle</property>
</object>
<packing>
<property name="left_attach">0</property>
2014-09-18 01:25:03 +04:00
<property name="top_attach">5</property>
2014-06-01 04:13:08 +04:00
</packing>
</child>
2014-09-18 01:25:03 +04:00
<child>
<object class="GtkLabel" id="overview-firmware-title">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-09-18 01:25:03 +04:00
<property name="valign">start</property>
<property name="label" translatable="yes">Firmware:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">4</property>
</packing>
</child>
<child>
<object class="GtkBox" id="box11">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">3</property>
<child>
<object class="GtkBox" id="box16">
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<object class="GtkComboBox" id="overview-firmware">
<property name="visible">True</property>
<property name="can_focus">False</property>
<signal name="changed" handler="on_overview_firmware_changed" swapped="no"/>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="overview-firmware-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="valign">start</property>
<property name="vexpand">False</property>
<property name="label">label</property>
</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">0</property>
</packing>
</child>
<child>
<object class="GtkImage" id="overview-firmware-warn">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="stock">gtk-dialog-warning</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
</object>
2014-06-01 04:13:08 +04:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">4</property>
2014-01-26 23:07:35 +04:00
</packing>
2009-03-01 01:28:00 +03:00
</child>
2015-02-22 01:54:15 +03:00
<child>
<object class="GtkBox" id="box17">
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<object class="GtkComboBox" id="machine-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<signal name="changed" handler="on_machine_type_changed" swapped="no"/>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="machine-type-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">label</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>
<property name="top_attach">3</property>
</packing>
</child>
2017-11-25 23:15:08 +03:00
<child>
<object class="GtkBox" id="overview-chipset-box">
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<object class="GtkComboBoxText" id="overview-chipset">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="hexpand">False</property>
<signal name="changed" handler="on_overview_chipset_changed" swapped="no"/>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="overview-chipset-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="valign">start</property>
<property name="vexpand">True</property>
<property name="label">label</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>
<property name="top_attach">5</property>
</packing>
</child>
2012-02-02 02:26:46 +04:00
</object>
2010-12-12 00:40:24 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2009-02-09 22:55:18 +03:00
</child>
2014-01-26 23:07:35 +04:00
<child type="label">
<object class="GtkLabel" id="frame">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>Hypervisor Details</b></property>
<property name="use_markup">True</property>
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
2014-02-21 14:13:11 +04:00
<child>
2015-09-14 01:01:39 +03:00
<object class="GtkExpander" id="idmap-expander">
2014-02-21 14:13:11 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<child>
<object class="GtkAlignment" id="alignment1">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<child>
2015-09-14 01:01:39 +03:00
<object class="GtkGrid" id="idmap-grid">
2014-02-21 14:13:11 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<property name="row_spacing">6</property>
<property name="column_spacing">6</property>
<child>
2015-09-14 01:01:39 +03:00
<object class="GtkCheckButton" id="idmap-checkbutton">
2014-02-21 14:13:11 +04:00
<property name="label" translatable="yes">Enable User Namespace</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-02-21 14:13:11 +04:00
<property name="draw_indicator">True</property>
2015-09-14 01:01:39 +03:00
<signal name="toggled" handler="on_idmap_check_toggled" swapped="no"/>
2014-02-21 14:13:11 +04:00
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkGrid" id="idmap-spin-grid">
<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="label19">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2014-02-21 14:13:11 +04:00
<property name="label" translatable="yes">User ID: </property>
<property name="max_width_chars">15</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label20">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2014-02-21 14:13:11 +04:00
<property name="label" translatable="yes"> Group ID: </property>
<property name="max_width_chars">15</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label21">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">Start</property>
<property name="max_width_chars">20</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label22">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">Target</property>
<property name="max_width_chars">20</property>
</object>
<packing>
<property name="left_attach">2</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label29">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">Count</property>
<property name="max_width_chars">20</property>
</object>
<packing>
<property name="left_attach">3</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label33">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="max_width_chars">15</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkSpinButton" id="uid-target">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="width_chars">6</property>
<property name="adjustment">adjustment16</property>
<signal name="changed" handler="on_idmap_uid_target_changed" swapped="no"/>
</object>
<packing>
<property name="left_attach">2</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkSpinButton" id="gid-target">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="adjustment">adjustment17</property>
<signal name="changed" handler="on_idmap_gid_target_changed" swapped="no"/>
</object>
<packing>
<property name="left_attach">2</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkSpinButton" id="uid-count">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="width_chars">6</property>
<property name="adjustment">adjustment18</property>
<signal name="changed" handler="on_idmap_uid_count_changed" swapped="no"/>
</object>
<packing>
<property name="left_attach">3</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkSpinButton" id="gid-count">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="adjustment">adjustment19</property>
<signal name="changed" handler="on_idmap_gid_count_changed" swapped="no"/>
</object>
<packing>
<property name="left_attach">3</property>
<property name="top_attach">2</property>
</packing>
</child>
2014-02-27 06:01:29 +04:00
<child>
<object class="GtkLabel" id="gid-start">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">0</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="uid-start">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">0</property>
<property name="width_chars">10</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
</packing>
</child>
2014-02-21 14:13:11 +04:00
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
</object>
</child>
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label8">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>User Namespace</b></property>
<property name="use_markup">True</property>
</object>
</child>
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">2</property>
</packing>
</child>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="vbox6-atkobject">
<property name="AtkObject::accessible-name">overview-tab</property>
</object>
</child>
2014-01-26 23:07:35 +04:00
</object>
</child>
<child type="tab">
<object class="GtkLabel" id="label10">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">over</property>
</object>
<packing>
<property name="tab_fill">False</property>
</packing>
</child>
<child>
2018-03-13 23:37:46 +03:00
<object class="GtkBox" id="box14">
2014-01-26 23:07:35 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
2018-03-13 23:37:46 +03:00
<property name="spacing">12</property>
2014-01-26 23:07:35 +04:00
<child>
2018-03-13 23:37:46 +03:00
<object class="GtkFrame" id="details-inspection-os">
2014-01-26 23:07:35 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2018-03-13 23:37:46 +03:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
2009-02-09 22:55:18 +03:00
<child>
2018-03-13 23:37:46 +03:00
<object class="GtkAlignment" id="alignment43">
2009-02-09 22:55:18 +03:00
<property name="visible">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 18:18:47 +04:00
<property name="can_focus">False</property>
2018-03-13 23:37:46 +03:00
<property name="left_padding">12</property>
2008-10-31 17:18:55 +03:00
<child>
2018-03-13 23:37:46 +03:00
<object class="GtkGrid" id="table17">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2018-03-13 23:37:46 +03:00
<property name="border_width">3</property>
<property name="row_spacing">6</property>
<property name="column_spacing">6</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 18:18:47 +04:00
<child>
2018-03-13 23:37:46 +03:00
<object class="GtkLabel" id="label72">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2018-03-13 23:37:46 +03:00
<property name="halign">end</property>
<property name="label" translatable="yes">Product name:</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 18:18:47 +04:00
</object>
2018-03-13 23:37:46 +03:00
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="inspection-hostname">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label">foo</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label71">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="label" translatable="yes">Hostname:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="label" translatable="yes">Operating system:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="inspection-product-name">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label">foo</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="inspection-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label" translatable="yes">foo</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
</packing>
2009-09-23 18:45:44 +04:00
</child>
2013-11-25 19:10:03 +04:00
</object>
</child>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
</child>
2018-03-13 23:37:46 +03:00
<child type="label">
<object class="GtkLabel" id="label70">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>Operating System</b></property>
<property name="use_markup">True</property>
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkExpander" id="details-inspection-apps">
<property name="visible">True</property>
<property name="can_focus">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 18:18:47 +04:00
<child>
2018-03-13 23:37:46 +03:00
<object class="GtkAlignment" id="alignment44">
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 18:18:47 +04:00
<property name="visible">True</property>
2018-03-13 23:37:46 +03:00
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">21</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 18:18:47 +04:00
<child>
2018-03-13 23:37:46 +03:00
<object class="GtkScrolledWindow" id="scrolledwindow6">
<property name="height_request">150</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 18:18:47 +04:00
<property name="visible">True</property>
2018-03-13 23:37:46 +03:00
<property name="can_focus">True</property>
<property name="shadow_type">etched-in</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 18:18:47 +04:00
<child>
2018-03-13 23:37:46 +03:00
<object class="GtkTreeView" id="inspection-apps">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
2018-03-13 23:37:46 +03:00
<child internal-child="selection">
<object class="GtkTreeSelection" id="treeview-selection"/>
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 18:18:47 +04:00
</child>
</object>
</child>
</object>
</child>
2013-11-25 19:10:03 +04:00
</object>
2018-03-13 23:37:46 +03:00
</child>
<child type="label">
<object class="GtkLabel" id="label73">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>Applications</b></property>
<property name="use_markup">True</property>
</object>
2013-11-25 19:10:03 +04:00
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
2018-03-13 23:37:46 +03:00
<property name="position">1</property>
2013-11-25 19:10:03 +04:00
</packing>
</child>
<child>
2018-03-13 23:37:46 +03:00
<object class="GtkBox">
2013-11-25 19:10:03 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2018-03-13 23:37:46 +03:00
<property name="spacing">12</property>
2013-11-25 19:10:03 +04:00
<child>
2018-03-13 23:37:46 +03:00
<object class="GtkGrid" id="details-overview-error-box">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2013-11-25 19:10:03 +04:00
<property name="halign">start</property>
2018-03-13 23:37:46 +03:00
<property name="valign">center</property>
<property name="orientation">vertical</property>
<property name="column_spacing">6</property>
<child>
<object class="GtkImage" id="image1">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="valign">start</property>
<property name="stock">gtk-dialog-warning</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="details-overview-error">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="valign">start</property>
<property name="label">Error message baraaaaaaaa aaaaaaaaaaaaaa aaaaaaaaaaaaaaaa</property>
<property name="justify">fill</property>
<property name="wrap">True</property>
<property name="max_width_chars">60</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
</child>
2013-11-25 19:10:03 +04:00
</object>
<packing>
2018-03-13 23:37:46 +03:00
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
2013-11-25 19:10:03 +04:00
</packing>
</child>
<child>
2018-03-13 23:37:46 +03:00
<object class="GtkButton" id="details-inspection-refresh">
<property name="label" translatable="yes">Refresh</property>
2013-11-25 19:10:03 +04:00
<property name="visible">True</property>
2018-03-13 23:37:46 +03:00
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<property name="halign">end</property>
2017-05-31 16:08:36 +03:00
<property name="valign">start</property>
2018-03-13 23:37:46 +03:00
<signal name="clicked" handler="on_details_inspection_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 18:18:47 +04:00
</object>
2013-11-25 19:10:03 +04:00
<packing>
2018-03-13 23:37:46 +03:00
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">1</property>
2013-11-25 19:10:03 +04:00
</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 18:18:47 +04:00
</child>
</object>
2017-02-23 13:22:27 +03:00
<packing>
<property name="expand">False</property>
2018-03-13 23:37:46 +03:00
<property name="fill">True</property>
2017-02-23 13:22:27 +03:00
<property name="position">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 18:18:47 +04:00
</object>
2014-01-26 23:07:35 +04:00
<packing>
<property name="position">1</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 18:18:47 +04:00
</child>
<child type="tab">
2014-01-26 23:07:35 +04:00
<object class="GtkLabel" id="label14">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2014-01-26 23:07:35 +04:00
<property name="label">inspect</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 18:18:47 +04:00
</object>
<packing>
2014-01-26 23:07:35 +04: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 18:18:47 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
2013-09-27 22:17:57 +04:00
<object class="GtkBox" id="box2">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2013-09-27 22:17:57 +04:00
<property name="orientation">vertical</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 18:18:47 +04:00
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="vbox5">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</property>
2013-09-27 22:17:57 +04:00
<property name="spacing">12</property>
2010-12-17 00:05:55 +03:00
<child>
2013-09-27 22:17:57 +04:00
<object class="GtkFrame" id="frame24">
2010-12-17 00:05:55 +03:00
<property name="visible">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 18:18:47 +04:00
<property name="can_focus">False</property>
2013-09-27 22:17:57 +04:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
2010-12-17 00:05:55 +03:00
<child>
2013-09-27 22:17:57 +04:00
<object class="GtkAlignment" id="alignment50">
2010-12-17 00:05:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2013-09-27 22:17:57 +04:00
<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 18:18:47 +04:00
<child>
2013-09-27 22:17:57 +04:00
<object class="GtkBox" id="box7">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2013-09-27 22:17:57 +04:00
<property name="orientation">vertical</property>
<property name="spacing">3</property>
<child>
<object class="GtkAlignment" id="overview-cpu-usage-align">
<property name="height_request">75</property>
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<placeholder/>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="overview-cpu-usage-text">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-09-27 22:17:57 +04:00
<property name="label">18%</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</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 18:18:47 +04:00
</object>
</child>
2013-09-27 22:17:57 +04:00
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label45">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>CPU usage</b></property>
<property name="use_markup">True</property>
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkFrame" id="frame3">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<child>
<object class="GtkAlignment" id="alignment4">
<property name="visible">True</property>
<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 18:18:47 +04:00
<child>
2013-09-27 22:17:57 +04:00
<object class="GtkBox" id="box6">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2013-09-27 22:17:57 +04:00
<property name="orientation">vertical</property>
<property name="spacing">3</property>
<child>
<object class="GtkAlignment" id="overview-memory-usage-align">
<property name="height_request">75</property>
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<placeholder/>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="overview-memory-usage-text">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2014-06-16 07:56:02 +04:00
<property name="label">30 MiB of 128 MiB</property>
2013-09-27 22:17:57 +04:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</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 18:18:47 +04:00
</object>
</child>
2013-09-27 22:17:57 +04:00
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label51">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>Memory usage</b></property>
<property name="use_markup">True</property>
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">1</property>
</packing>
</child>
<child>
<object class="GtkFrame" id="frame22">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<child>
<object class="GtkAlignment" id="alignment48">
<property name="visible">True</property>
<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 18:18:47 +04:00
<child>
2013-09-27 22:17:57 +04:00
<object class="GtkBox" id="box5">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2013-09-27 22:17:57 +04:00
<property name="orientation">vertical</property>
<property name="spacing">3</property>
<child>
<object class="GtkAlignment" id="overview-disk-usage-align">
<property name="height_request">75</property>
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<placeholder/>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="overview-disk-usage-text">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2014-06-16 07:56:02 +04:00
<property name="label" translatable="yes">0 KiBytes/s 0 KiBytes/s</property>
2013-09-27 22:17:57 +04:00
<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>
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 18:18:47 +04:00
</object>
</child>
2013-09-27 22:17:57 +04:00
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label91">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>Disk I/O</b></property>
<property name="use_markup">True</property>
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">2</property>
</packing>
</child>
<child>
<object class="GtkFrame" id="frame23">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<child>
<object class="GtkAlignment" id="alignment49">
<property name="visible">True</property>
<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 18:18:47 +04:00
<child>
2013-09-27 22:17:57 +04:00
<object class="GtkBox" id="box8">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2013-09-27 22:17:57 +04:00
<property name="orientation">vertical</property>
<property name="spacing">3</property>
<child>
<object class="GtkAlignment" id="overview-network-traffic-align">
<property name="height_request">75</property>
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<placeholder/>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="overview-network-traffic-text">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2014-06-16 07:56:02 +04:00
<property name="label">0 KiBytes/s 0 KiBytes/s</property>
2013-09-27 22:17:57 +04:00
<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>
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 18:18:47 +04:00
</object>
2010-12-17 00:05:55 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2010-12-17 00:05:55 +03:00
</child>
2013-09-27 22:17:57 +04:00
<child type="label">
<object class="GtkLabel" id="label92">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>Network I/O</b></property>
<property name="use_markup">True</property>
</object>
</child>
2012-02-02 02:26:46 +04:00
</object>
2013-09-27 22:17:57 +04:00
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">3</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 18:18:47 +04:00
</child>
</object>
<packing>
2013-09-27 22:17:57 +04:00
<property name="expand">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 18:18:47 +04:00
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="box2-atkobject">
<property name="AtkObject::accessible-name">performance-tab</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 18:18:47 +04:00
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">2</property>
2013-09-27 22:17:57 +04:00
<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 18:18:47 +04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label7">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">stat</property>
</object>
<packing>
2014-01-26 23:07:35 +04: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 18:18:47 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="vbox14">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2014-01-26 23:14:44 +04:00
<property name="valign">start</property>
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</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 18:18:47 +04:00
<property name="spacing">12</property>
<child>
<object class="GtkFrame" id="CPUs">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
2010-12-17 00:05:55 +03:00
<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 18:18:47 +04:00
<object class="GtkAlignment" id="alignment11">
2010-12-17 00:05:55 +03:00
<property name="visible">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 18:18:47 +04:00
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">12</property>
2010-12-17 00:05:55 +03:00
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="hbox5">
2010-12-17 00:05:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="spacing">6</property>
2010-12-17 00:05:55 +03:00
<child>
2017-05-31 16:08:40 +03:00
<object class="GtkGrid" id="table30">
2010-12-17 00:05:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="border_width">3</property>
<property name="row_spacing">6</property>
2017-05-31 16:08:40 +03:00
<property name="column_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 18:18:47 +04:00
<child>
<object class="GtkLabel" id="state-host-cpus">
2010-12-17 00:05:55 +03:00
<property name="visible">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 18:18:47 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2017-05-31 16:08:40 +03:00
<property name="valign">center</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 18:18:47 +04:00
<property name="label">8</property>
<property name="selectable">True</property>
2012-02-02 02:26:46 +04:00
</object>
2010-12-17 00:05:55 +03:00
<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 18:18:47 +04:00
<property name="left_attach">1</property>
2017-05-31 16:08:40 +03:00
<property name="top_attach">0</property>
2010-12-17 00:05:55 +03:00
</packing>
</child>
<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 18:18:47 +04:00
<object class="GtkLabel" id="label334">
2010-12-17 00:05:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2017-05-31 16:08:40 +03:00
<property name="valign">center</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 18:18:47 +04:00
<property name="label" translatable="yes">Logical host CPUs:</property>
</object>
<packing>
2017-05-31 16:08:40 +03:00
<property name="left_attach">0</property>
<property name="top_attach">0</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 18:18:47 +04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="label335">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2017-05-31 16:08:40 +03:00
<property name="valign">center</property>
2014-10-21 12:04:34 +04:00
<property name="label" translatable="yes">Ma_ximum allocation:</property>
<property name="use_underline">True</property>
2015-09-14 01:01:39 +03:00
<property name="mnemonic_widget">cpu-maxvcpus</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 18:18:47 +04:00
</object>
<packing>
2017-05-31 16:08:40 +03:00
<property name="left_attach">0</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 18:18:47 +04:00
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label333">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2017-05-31 16:08:40 +03:00
<property name="valign">center</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 18:18:47 +04:00
<property name="label" translatable="yes">Current a_llocation:</property>
<property name="use_underline">True</property>
2015-09-14 01:01:39 +03:00
<property name="mnemonic_widget">cpu-vcpus</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 18:18:47 +04:00
</object>
<packing>
2017-05-31 16:08:40 +03:00
<property name="left_attach">0</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 18:18:47 +04:00
<property name="top_attach">1</property>
</packing>
</child>
<child>
2015-09-14 01:01:39 +03:00
<object class="GtkSpinButton" id="cpu-maxvcpus">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
<property name="adjustment">adjustment6</property>
2015-09-14 01:01:39 +03:00
<signal name="changed" handler="on_cpu_maxvcpus_changed" 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 18:18:47 +04:00
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
2015-09-14 01:01:39 +03:00
<object class="GtkSpinButton" id="cpu-vcpus">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
2017-05-31 16:08:40 +03:00
<property name="valign">center</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 18:18:47 +04:00
<property name="invisible_char">●</property>
<property name="adjustment">adjustment7</property>
<property name="climb_rate">1</property>
<property name="numeric">True</property>
<property name="update_policy">if-valid</property>
2015-09-14 01:01:39 +03:00
<signal name="changed" handler="on_cpu_vcpus_changed" 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 18:18:47 +04:00
<child internal-child="accessible">
2015-09-14 01:01:39 +03:00
<object class="AtkObject" id="cpu-vcpus-atkobject">
2015-09-24 00:01:41 +03:00
<property name="AtkObject::accessible-name">Virtual CPU Select</property>
2012-02-02 02:26:46 +04:00
</object>
2010-12-17 00:05:55 +03:00
</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 18:18:47 +04:00
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
</packing>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="cpu-vcpus-warn-box">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">6</property>
<child>
<object class="GtkImage" id="image9">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03: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 18:18:47 +04:00
<property name="stock">gtk-dialog-warning</property>
2012-02-02 02:26:46 +04:00
</object>
2010-12-17 00:05:55 +03:00
<packing>
2013-01-13 01:13:53 +04:00
<property name="expand">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 18:18:47 +04:00
<property name="fill">False</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label28">
<property name="width_request">300</property>
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03: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 18:18:47 +04:00
<property name="label" translatable="yes"><small>Overcommitting vCPUs can hurt performance</small></property>
<property name="use_markup">True</property>
<property name="wrap">True</property>
<property name="max_width_chars">32</property>
</object>
<packing>
<property name="expand">True</property>
2012-02-02 02:26:46 +04:00
<property name="fill">True</property>
2010-12-17 00:05:55 +03:00
<property name="position">1</property>
</packing>
</child>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
2010-12-17 00:05:55 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2010-12-17 00:05:55 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2010-12-17 00:05:55 +03:00
</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 18:18:47 +04:00
<child type="label">
<object class="GtkLabel" id="label100">
2008-10-31 17:18:55 +03:00
<property name="visible">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 18:18:47 +04:00
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>CPUs</b></property>
<property name="use_markup">True</property>
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">0</property>
</packing>
</child>
<child>
2015-04-07 18:53:16 +03:00
<object class="GtkFrame" id="frame1">
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 18:18:47 +04:00
<property name="visible">True</property>
2015-04-07 18:53:16 +03:00
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</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 18:18:47 +04:00
<child>
2015-04-07 18:53:16 +03:00
<object class="GtkAlignment" id="alignment5">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2015-04-07 18:53:16 +03:00
<property name="top_padding">3</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 18:18:47 +04:00
<child>
2014-01-31 22:40:09 +04:00
<object class="GtkGrid" id="table15">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2014-01-31 22:40:09 +04:00
<property name="halign">start</property>
<property name="valign">start</property>
<property name="row_spacing">3</property>
<property name="column_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 18:18:47 +04:00
<child>
2014-01-31 22:40:09 +04:00
<object class="GtkLabel" id="label52">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-11-11 11:06:47 +03:00
<property name="label" translatable="yes">M_odel:</property>
<property name="use_underline">True</property>
2015-04-07 18:53:16 +03:00
<property name="mnemonic_widget">combobox-entry</property>
2014-01-31 22:40:09 +04:00
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkCheckButton" id="cpu-copy-host">
2014-11-11 11:06:47 +03:00
<property name="label" translatable="yes">Copy host CP_U configuration</property>
2014-01-31 22:40:09 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-12-12 13:31:11 +03:00
<property name="use_underline">True</property>
2014-01-31 22:40:09 +04:00
<property name="draw_indicator">True</property>
<signal name="clicked" handler="on_cpu_copy_host_clicked" swapped="no"/>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
<property name="width">2</property>
</packing>
</child>
<child>
<object class="GtkComboBox" id="cpu-model">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="has_entry">True</property>
<signal name="changed" handler="on_cpu_model_changed" swapped="no"/>
<child internal-child="entry">
2015-04-07 18:53:16 +03:00
<object class="GtkEntry" id="combobox-entry">
2014-01-31 22:40:09 +04:00
<property name="can_focus">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 18:18:47 +04:00
</object>
</child>
2018-01-21 02:21:54 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="cpu-model-atkobject">
<property name="AtkObject::accessible-name">cpu-model</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 18:18:47 +04:00
</object>
<packing>
2014-01-31 22:40:09 +04:00
<property name="left_attach">1</property>
<property name="top_attach">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 18:18:47 +04:00
</packing>
</child>
</object>
</child>
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label49">
<property name="visible">True</property>
<property name="can_focus">False</property>
2014-11-11 11:06:47 +03:00
<property name="label" translatable="yes"><b>Configu_ration</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 18:18:47 +04:00
<property name="use_markup">True</property>
2014-11-11 11:06:47 +03:00
<property name="use_underline">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 18:18:47 +04:00
</object>
</child>
</object>
<packing>
2015-04-07 18:53:16 +03:00
<property name="expand">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 18:18:47 +04:00
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
<child>
2014-02-01 18:14:55 +04:00
<object class="GtkExpander" id="cpu-topology-expander">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<child>
<object class="GtkAlignment" id="alignment39">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="left_padding">23</property>
<property name="right_padding">12</property>
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="vbox15">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</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 18:18:47 +04:00
<property name="spacing">4</property>
<child>
<object class="GtkCheckButton" id="cpu-topology-enable">
2014-11-11 11:06:47 +03:00
<property name="label" translatable="yes">Manuall_y set CPU topology</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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
2014-12-12 13:31:11 +03:00
<property name="use_underline">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 18:18:47 +04:00
<property name="active">True</property>
<property name="draw_indicator">True</property>
<signal name="toggled" handler="on_cpu_topology_enable_toggled" swapped="no"/>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
2014-10-27 19:04:56 +03:00
<object class="GtkAlignment" id="alignment3">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-10-27 19:04:56 +03:00
<property name="xscale">0</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 18:18:47 +04:00
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="hbox26">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2014-10-27 19:04:56 +03:00
<property name="spacing">6</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 18:18:47 +04:00
<child>
2017-05-31 16:08:40 +03:00
<object class="GtkGrid" id="cpu-topology-table">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2014-10-27 19:04:56 +03:00
<property name="row_spacing">4</property>
2017-05-31 16:08:40 +03:00
<property name="column_spacing">12</property>
2014-10-27 19:04:56 +03:00
<child>
<object class="GtkLabel" id="label59">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-11-11 11:06:47 +03:00
<property name="label" translatable="yes">Thread_s:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">cpu-threads</property>
2014-10-27 19:04:56 +03:00
</object>
<packing>
2017-05-31 16:08:40 +03:00
<property name="left_attach">0</property>
2014-10-27 19:04:56 +03:00
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label58">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-11-11 11:06:47 +03:00
<property name="label" translatable="yes">Cor_es:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">cpu-cores</property>
2014-10-27 19:04:56 +03:00
</object>
<packing>
2017-05-31 16:08:40 +03:00
<property name="left_attach">0</property>
2014-10-27 19:04:56 +03:00
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label57">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-11-11 11:06:47 +03:00
<property name="label" translatable="yes">Socke_ts:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">cpu-sockets</property>
2014-10-27 19:04:56 +03:00
</object>
<packing>
2017-05-31 16:08:40 +03:00
<property name="left_attach">0</property>
<property name="top_attach">0</property>
2014-10-27 19:04:56 +03:00
</packing>
</child>
<child>
<object class="GtkSpinButton" id="cpu-sockets">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="halign">start</property>
<property name="hexpand">False</property>
<property name="invisible_char">●</property>
<property name="adjustment">adjustment3</property>
<signal name="changed" handler="on_cpu_sockets_changed" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
2017-05-31 16:08:40 +03:00
<property name="top_attach">0</property>
2014-10-27 19:04:56 +03:00
</packing>
</child>
<child>
<object class="GtkSpinButton" id="cpu-cores">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="halign">start</property>
<property name="hexpand">False</property>
2017-05-31 16:08:40 +03:00
<property name="vexpand">True</property>
2014-10-27 19:04:56 +03:00
<property name="invisible_char">●</property>
<property name="adjustment">adjustment4</property>
<signal name="changed" handler="on_cpu_cores_changed" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkSpinButton" id="cpu-threads">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="halign">start</property>
2017-05-31 16:08:40 +03:00
<property name="hexpand">True</property>
<property name="vexpand">True</property>
2014-10-27 19:04:56 +03:00
<property name="invisible_char">●</property>
<property name="adjustment">adjustment5</property>
<signal name="changed" handler="on_cpu_threads_changed" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">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 18:18:47 +04:00
</object>
<packing>
2014-10-27 19:04:56 +03:00
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</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 18:18:47 +04:00
</packing>
</child>
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="cpu-topology-warn-box">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2014-10-27 19:04:56 +03:00
<property name="spacing">6</property>
<child>
<object class="GtkImage" id="image4">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2017-05-31 16:08:36 +03:00
<property name="valign">end</property>
2014-10-27 19:04:56 +03:00
<property name="stock">gtk-dialog-warning</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label65">
<property name="width_request">300</property>
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2017-05-31 16:08:36 +03:00
<property name="valign">end</property>
2014-10-27 19:04:56 +03:00
<property name="label" translatable="yes"><small>Selected CPU model does not support Hyper-Threading</small></property>
<property name="use_markup">True</property>
<property name="single_line_mode">True</property>
<property name="max_width_chars">32</property>
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
2012-02-02 02:26:46 +04:00
</object>
2010-02-25 04:37:41 +03:00
<packing>
2014-10-27 19:04:56 +03:00
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">1</property>
2010-12-12 00:40:24 +03:00
</packing>
2010-02-25 04:37:41 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2009-02-09 22:55:18 +03:00
</child>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
2009-02-09 22:55:18 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2008-10-31 17:18:55 +03:00
</child>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
</child>
<child type="label">
<object class="GtkLabel" id="label62">
<property name="visible">True</property>
<property name="can_focus">False</property>
2014-11-11 11:06:47 +03:00
<property name="label" translatable="yes"><b>To_pology</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 18:18:47 +04:00
<property name="use_markup">True</property>
2014-11-11 11:06:47 +03:00
<property name="use_underline">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 18:18:47 +04:00
</object>
2009-02-09 22:55:18 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2009-09-23 18:45:44 +04:00
<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 18:18:47 +04:00
<property name="expand">False</property>
<property name="fill">True</property>
2015-11-18 23:05:21 +03:00
<property name="position">2</property>
2010-12-12 00:40:24 +03:00
</packing>
</child>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="vbox14-atkobject">
<property name="AtkObject::accessible-name">cpu-tab</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 18:18:47 +04:00
</object>
<packing>
2014-01-26 23:07:35 +04: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 18:18:47 +04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label53">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">cpu</property>
</object>
<packing>
2014-01-26 23:07:35 +04: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 18:18:47 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="vbox7">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</property>
2010-12-12 00:40:24 +03:00
<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 18:18:47 +04:00
<object class="GtkFrame" id="frame5">
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
2010-12-12 00:40:24 +03:00
<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 18:18:47 +04:00
<object class="GtkAlignment" id="alignment23">
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
2010-12-12 00:40:24 +03:00
<child>
2017-05-31 16:08:40 +03:00
<object class="GtkGrid" id="table6">
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="border_width">3</property>
<property name="row_spacing">6</property>
2017-05-31 16:08:40 +03:00
<property name="column_spacing">6</property>
2010-12-12 00:40:24 +03:00
<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 18:18:47 +04:00
<object class="GtkLabel" id="label60">
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2017-05-31 16:08:40 +03:00
<property name="valign">center</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 18:18:47 +04:00
<property name="label" translatable="yes">Current a_llocation:</property>
<property name="use_underline">True</property>
2015-09-14 01:01:39 +03:00
<property name="mnemonic_widget">mem-memory</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 18:18:47 +04:00
</object>
<packing>
2017-05-31 16:08:40 +03:00
<property name="left_attach">0</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 18:18:47 +04:00
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label307">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2017-05-31 16:08:40 +03:00
<property name="valign">center</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 18:18:47 +04:00
<property name="label" translatable="yes">Ma_ximum allocation:</property>
<property name="use_underline">True</property>
2015-09-14 01:01:39 +03:00
<property name="mnemonic_widget">mem-maxmem</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 18:18:47 +04:00
</object>
<packing>
2017-05-31 16:08:40 +03:00
<property name="left_attach">0</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 18:18:47 +04:00
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label61">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2017-05-31 16:08:40 +03:00
<property name="valign">center</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 18:18:47 +04:00
<property name="label" translatable="yes">Total host memory:</property>
</object>
<packing>
2017-05-31 16:08:40 +03:00
<property name="left_attach">0</property>
<property name="top_attach">0</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 18:18:47 +04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="state-host-memory">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2017-05-31 16:08:40 +03:00
<property name="valign">center</property>
2014-06-16 07:56:02 +04:00
<property name="label">2 GiB</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 18:18:47 +04:00
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
2017-05-31 16:08:40 +03:00
<property name="top_attach">0</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 18:18:47 +04:00
</packing>
</child>
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="hbox46">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:40 +03:00
<property name="valign">center</property>
<property name="hexpand">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 18:18:47 +04:00
<property name="spacing">3</property>
2010-12-11 03:20:14 +03:00
<child>
2015-09-14 01:01:39 +03:00
<object class="GtkSpinButton" id="mem-memory">
2010-12-11 03:20:14 +03:00
<property name="visible">True</property>
2010-12-12 00:40:24 +03:00
<property name="can_focus">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 18:18:47 +04:00
<property name="invisible_char">●</property>
<property name="adjustment">adjustment2</property>
<property name="climb_rate">2</property>
<property name="numeric">True</property>
<property name="update_policy">if-valid</property>
2015-09-14 01:01:39 +03:00
<signal name="changed" handler="on_mem_memory_changed" 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 18:18:47 +04:00
<child internal-child="accessible">
2015-09-14 01:01:39 +03:00
<object class="AtkObject" id="mem-memory-atkobject">
2015-09-24 00:01:41 +03:00
<property name="AtkObject::accessible-name">Memory Select</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 18:18:47 +04:00
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label306">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-06-16 07:56:02 +04:00
<property name="label" translatable="yes">MiB</property>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
2009-11-04 23:41:18 +03:00
</child>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
</packing>
2010-12-12 00:40:24 +03:00
</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 18:18:47 +04:00
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="hbox47">
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:40 +03:00
<property name="valign">center</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 18:18:47 +04:00
<property name="spacing">3</property>
<child>
2015-09-14 01:01:39 +03:00
<object class="GtkSpinButton" id="mem-maxmem">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
<property name="adjustment">adjustment1</property>
<property name="climb_rate">2</property>
<property name="numeric">True</property>
<property name="update_policy">if-valid</property>
2015-09-14 01:01:39 +03:00
<signal name="changed" handler="on_mem_maxmem_changed" 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 18:18:47 +04:00
<child internal-child="accessible">
2015-09-14 01:01:39 +03:00
<object class="AtkObject" id="mem-maxmem-atkobject">
2015-09-24 00:01:41 +03:00
<property name="AtkObject::accessible-name">Max Memory Select</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 18:18:47 +04:00
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label346">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-06-16 07:56:02 +04:00
<property name="label" translatable="yes">MiB</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 18:18:47 +04:00
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">2</property>
</packing>
2010-03-04 02:43:48 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2010-12-12 00:40:24 +03:00
</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 18:18:47 +04:00
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label101">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>Memory</b></property>
<property name="use_markup">True</property>
</object>
</child>
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="vbox7-atkobject">
<property name="AtkObject::accessible-name">memory-tab</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 18:18:47 +04:00
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">4</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 18:18:47 +04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label54">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">mem</property>
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">4</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 18:18:47 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
2014-02-10 01:21:26 +04:00
<object class="GtkGrid" id="vbox4">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2014-02-10 01:21:26 +04:00
<property name="row_spacing">24</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 18:18:47 +04:00
<child>
2014-02-10 01:21:26 +04:00
<object class="GtkFrame" id="frame4">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2014-02-10 01:21:26 +04:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</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 18:18:47 +04:00
<child>
2014-02-10 01:21:26 +04:00
<object class="GtkAlignment" id="alignment2">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2014-02-10 01:21:26 +04:00
<property name="top_padding">3</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 18:18:47 +04:00
<child>
2015-09-14 01:01:39 +03:00
<object class="GtkCheckButton" id="boot-autostart">
2014-02-10 01:21:26 +04:00
<property name="label" translatable="yes">Start virt_ual machine on host boot up</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
<property name="use_underline">True</property>
<property name="draw_indicator">True</property>
2015-09-14 01:01:39 +03:00
<signal name="toggled" handler="on_boot_autostart_changed" swapped="no"/>
2014-02-10 01:21:26 +04:00
</object>
</child>
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label2">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>Autostart</b></property>
<property name="use_markup">True</property>
</object>
</child>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkFrame" id="boot-init-frame">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<child>
<object class="GtkAlignment" id="alignment36">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<child>
2014-06-01 01:34:23 +04:00
<object class="GtkGrid" id="grid3">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2014-06-01 01:34:23 +04:00
<property name="row_spacing">6</property>
<property name="column_spacing">6</property>
<child>
<object class="GtkEntry" id="boot-init-path">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
<property name="width_chars">25</property>
<signal name="changed" handler="on_boot_init_path_changed" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
</child>
2014-02-10 01:21:26 +04:00
<child>
<object class="GtkLabel" id="label69">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-06-01 01:34:23 +04:00
<property name="label" translatable="yes">Init _path:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">boot-init-path</property>
2014-02-10 01:21:26 +04:00
</object>
<packing>
2014-06-01 01:34:23 +04:00
<property name="left_attach">0</property>
<property name="top_attach">0</property>
2014-02-10 01:21:26 +04:00
</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 18:18:47 +04:00
<child>
2014-06-01 01:34:23 +04:00
<object class="GtkLabel" id="label64">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-06-01 01:34:23 +04:00
<property name="label" translatable="yes">Init ar_gs:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">boot-init-args</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkEntry" id="boot-init-args">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
2014-02-10 01:21:26 +04:00
<property name="width_chars">25</property>
2014-06-01 01:34:23 +04:00
<signal name="changed" handler="on_boot_init_args_changed" 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 18:18:47 +04:00
</object>
2014-02-10 01:21:26 +04:00
<packing>
2014-06-01 01:34:23 +04:00
<property name="left_attach">1</property>
<property name="top_attach">1</property>
2014-02-10 01:21:26 +04:00
</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 18:18:47 +04:00
</child>
</object>
</child>
</object>
</child>
2014-02-10 01:21:26 +04:00
<child type="label">
<object class="GtkLabel" id="labelll">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>Container init</b></property>
<property name="use_markup">True</property>
</object>
</child>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">3</property>
</packing>
</child>
<child>
<object class="GtkExpander" id="boot-kernel-expander">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="valign">start</property>
<property name="vexpand">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 18:18:47 +04:00
<child>
2014-02-10 01:21:26 +04:00
<object class="GtkAlignment" id="alignment20">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2014-02-10 01:21:26 +04:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
2010-12-12 00:40:24 +03:00
<child>
2014-02-10 01:21:26 +04:00
<object class="GtkBox" id="box1">
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2014-02-10 01:21:26 +04:00
<property name="orientation">vertical</property>
<property name="spacing">6</property>
<child>
<object class="GtkCheckButton" id="boot-kernel-enable">
2014-11-11 11:06:13 +03:00
<property name="label" translatable="yes">Ena_ble direct kernel boot</property>
2014-02-10 01:21:26 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-11-11 11:06:13 +03:00
<property name="use_underline">True</property>
2014-02-10 01:21:26 +04:00
<property name="draw_indicator">True</property>
<signal name="toggled" handler="on_boot_kernel_enable_toggled" swapped="no"/>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
2010-05-20 16:34:32 +04:00
<child>
2014-02-10 01:21:26 +04:00
<object class="GtkBox" id="boot-kernel-box">
2010-05-20 16:34:32 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2014-02-10 01:21:26 +04:00
<property name="spacing">6</property>
2010-05-20 16:34:32 +04:00
<child>
2017-05-31 16:08:40 +03:00
<object class="GtkGrid" id="table13">
2010-05-20 16:34:32 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2014-02-10 01:21:26 +04:00
<property name="column_spacing">6</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 18:18:47 +04:00
<child>
2014-02-10 01:21:26 +04:00
<object class="GtkLabel" id="label38">
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 18:18:47 +04:00
<property name="visible">True</property>
2014-02-10 01:21:26 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2017-05-31 16:08:38 +03:00
<property name="margin_top">8</property>
<property name="margin_bottom">8</property>
2014-11-11 11:06:13 +03:00
<property name="label" translatable="yes">Ke_rnel path:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">boot-kernel</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 18:18:47 +04:00
</object>
<packing>
2017-05-31 16:08:40 +03:00
<property name="left_attach">0</property>
<property name="top_attach">0</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 18:18:47 +04:00
</packing>
</child>
2010-12-11 03:20:14 +03:00
<child>
2014-02-10 01:21:26 +04:00
<object class="GtkLabel" id="label39">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2017-05-31 16:08:38 +03:00
<property name="margin_top">8</property>
<property name="margin_bottom">8</property>
2014-11-11 11:06:13 +03:00
<property name="label" translatable="yes">_Initrd path:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">boot-initrd</property>
2014-02-10 01:21:26 +04:00
</object>
<packing>
2017-05-31 16:08:40 +03:00
<property name="left_attach">0</property>
2014-02-10 01:21:26 +04:00
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkBox" id="box3">
2010-12-12 06:00:52 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:40 +03:00
<property name="valign">center</property>
<property name="hexpand">True</property>
2010-12-12 06:00:52 +03:00
<property name="spacing">6</property>
2010-12-11 03:20:14 +03:00
<child>
2014-02-10 01:21:26 +04:00
<object class="GtkEntry" id="boot-initrd">
2010-12-11 03:20:14 +03:00
<property name="visible">True</property>
2014-02-10 01:21:26 +04:00
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
<signal name="changed" handler="on_boot_initrd_changed" 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 18:18:47 +04:00
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
2014-02-10 01:21:26 +04:00
<object class="GtkButton" id="boot-initrd-browse">
<property name="label" translatable="yes">Browse</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 18:18:47 +04:00
<property name="visible">True</property>
2014-02-10 01:21:26 +04:00
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<signal name="clicked" handler="on_boot_initrd_browse_clicked" swapped="no"/>
2018-01-21 01:25:16 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="boot-initrd-browse-atkobject">
<property name="AtkObject::accessible-name">initrd-browse</property>
</object>
</child>
2014-02-10 01:21:26 +04:00
</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>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkBox" id="box4">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:40 +03:00
<property name="valign">center</property>
<property name="hexpand">True</property>
2014-02-10 01:21:26 +04:00
<property name="spacing">6</property>
<child>
<object class="GtkEntry" id="boot-kernel">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
<signal name="changed" handler="on_boot_kernel_changed" swapped="no"/>
2012-02-02 02:26:46 +04:00
</object>
2010-12-11 03:20:14 +03:00
<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 18:18:47 +04:00
<property name="expand">True</property>
2012-02-02 02:26:46 +04:00
<property name="fill">True</property>
2014-02-10 01:21:26 +04:00
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkButton" id="boot-kernel-browse">
<property name="label" translatable="yes">Browse</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<signal name="clicked" handler="on_boot_kernel_browse_clicked" swapped="no"/>
2018-01-21 01:25:16 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="boot-kernel-browse-atkobject">
<property name="AtkObject::accessible-name">kernel-browse</property>
</object>
</child>
2014-02-10 01:21:26 +04:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
2010-12-12 06:00:52 +03:00
<property name="position">1</property>
2010-12-11 03:20:14 +03:00
</packing>
</child>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
<packing>
2014-02-10 01:21:26 +04:00
<property name="left_attach">1</property>
2017-05-31 16:08:40 +03:00
<property name="top_attach">0</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 18:18:47 +04:00
</packing>
2010-12-11 04:33:41 +03:00
</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 18:18:47 +04:00
<child>
2014-02-10 01:21:26 +04:00
<object class="GtkLabel" id="label40">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2017-05-31 16:08:38 +03:00
<property name="margin_top">8</property>
<property name="margin_bottom">8</property>
2014-11-11 11:06:13 +03:00
<property name="label" translatable="yes">Kernel ar_gs:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">boot-kernel-args</property>
2014-02-10 01:21:26 +04:00
</object>
<packing>
2017-05-31 16:08:40 +03:00
<property name="left_attach">0</property>
2014-02-10 01:21:26 +04:00
<property name="top_attach">3</property>
</packing>
</child>
<child>
<object class="GtkEntry" id="boot-kernel-args">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
2017-05-31 16:08:40 +03:00
<property name="hexpand">True</property>
2014-02-10 01:21:26 +04:00
<property name="invisible_char">●</property>
<property name="width_chars">40</property>
<signal name="changed" handler="on_boot_kernel_args_changed" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">3</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="boot-dtb-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2017-05-31 16:08:38 +03:00
<property name="margin_top">8</property>
<property name="margin_bottom">8</property>
2018-01-21 01:25:16 +03:00
<property name="label" translatable="yes">D_TB path:</property>
2014-11-11 11:06:13 +03:00
<property name="use_underline">True</property>
<property name="mnemonic_widget">boot-dtb</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 18:18:47 +04:00
</object>
<packing>
2017-05-31 16:08:40 +03:00
<property name="left_attach">0</property>
2014-02-10 01:21:26 +04: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 18:18:47 +04:00
</packing>
</child>
2010-12-12 07:00:19 +03:00
<child>
2014-02-10 01:21:26 +04:00
<object class="GtkBox" id="boot-dtb-box">
2010-12-12 07:00:19 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:40 +03:00
<property name="valign">center</property>
<property name="hexpand">True</property>
2013-08-18 20:25:20 +04:00
<property name="spacing">6</property>
2011-05-26 20:38:48 +04:00
<child>
2014-02-10 01:21:26 +04:00
<object class="GtkEntry" id="boot-dtb">
2011-05-26 20:38:48 +04:00
<property name="visible">True</property>
2014-02-10 01:21:26 +04:00
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
<signal name="changed" handler="on_boot_dtb_changed" 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 18:18:47 +04:00
</object>
<packing>
2014-02-10 01:21:26 +04:00
<property name="expand">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 18:18:47 +04:00
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
2014-02-10 01:21:26 +04:00
<object class="GtkButton" id="boot-dtb-browse">
<property name="label" translatable="yes">Browse</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 18:18:47 +04:00
<property name="visible">True</property>
2014-02-10 01:21:26 +04:00
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<signal name="clicked" handler="on_boot_dtb_browse_clicked" swapped="no"/>
2018-01-21 01:25:16 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="boot-dtb-browse-atkobject">
<property name="AtkObject::accessible-name">dtb-browse</property>
</object>
</child>
2012-02-02 02:26:46 +04:00
</object>
2011-05-26 20:38:48 +04:00
<packing>
2014-02-10 01:21:26 +04:00
<property name="expand">False</property>
2013-08-18 20:25:20 +04:00
<property name="fill">True</property>
<property name="position">1</property>
2010-12-12 07:00:19 +03:00
</packing>
</child>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
<packing>
2014-02-10 01:21:26 +04:00
<property name="left_attach">1</property>
<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 18:18:47 +04:00
</packing>
2010-12-12 07:00:19 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2014-02-10 01:21:26 +04:00
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<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 18:18:47 +04:00
</object>
2014-02-10 01:21:26 +04:00
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
2010-12-12 07:00:19 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2011-05-26 20:38:48 +04:00
</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 18:18:47 +04:00
</object>
</child>
2014-02-10 01:21:26 +04:00
<child type="label">
<object class="GtkLabel" id="label37">
<property name="visible">True</property>
<property name="can_focus">False</property>
2014-11-11 11:06:13 +03:00
<property name="label" translatable="yes"><b>Dir_ect kernel boot</b></property>
2014-02-10 01:21:26 +04:00
<property name="use_markup">True</property>
2014-11-11 11:06:13 +03:00
<property name="use_underline">True</property>
2014-02-10 01:21:26 +04:00
</object>
</child>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkFrame" id="boot-order-frame">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</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 18:18:47 +04:00
<child>
2014-02-10 01:21:26 +04:00
<object class="GtkAlignment" id="bootalign">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2014-02-10 01:21:26 +04:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
2011-05-26 20:38:48 +04:00
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="bootvbox">
2011-05-26 20:38:48 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</property>
2014-02-10 01:21:26 +04:00
<property name="spacing">6</property>
2010-12-12 07:00:19 +03:00
<child>
2014-02-10 01:21:26 +04:00
<object class="GtkCheckButton" id="boot-menu">
<property name="label" translatable="yes">Enable boot me_nu</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-02-10 01:21:26 +04:00
<property name="use_underline">True</property>
<property name="draw_indicator">True</property>
<signal name="toggled" handler="on_boot_menu_changed" swapped="no"/>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkGrid" id="table2">
2010-12-12 07:00:19 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2014-02-10 01:21:26 +04:00
<property name="halign">start</property>
<property name="hexpand">False</property>
<property name="row_spacing">6</property>
<property name="column_spacing">6</property>
<child>
<object class="GtkScrolledWindow" id="scrolledwindow3">
<property name="width_request">125</property>
<property name="height_request">125</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="hscrollbar_policy">never</property>
<property name="shadow_type">in</property>
<child>
2015-09-14 01:01:39 +03:00
<object class="GtkTreeView" id="boot-list">
2014-02-10 01:21:26 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="headers_visible">False</property>
<child internal-child="selection">
<object class="GtkTreeSelection" id="treeview-selection4">
2015-09-14 01:01:39 +03:00
<signal name="changed" handler="on_boot_list_changed" swapped="no"/>
2014-02-10 01:21:26 +04:00
</object>
</child>
</object>
</child>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
2011-05-26 20:38:48 +04:00
<child>
2014-02-10 01:21:26 +04:00
<object class="GtkBox" id="box13">
2011-05-26 20:38:48 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2014-02-10 01:21:26 +04:00
<property name="orientation">vertical</property>
<property name="spacing">6</property>
2011-05-26 20:38:48 +04:00
<child>
2015-09-14 01:01:39 +03:00
<object class="GtkButton" id="boot-moveup">
2011-05-26 20:38:48 +04:00
<property name="visible">True</property>
2014-02-10 01:21:26 +04:00
<property name="sensitive">False</property>
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<property name="valign">start</property>
2015-09-14 01:01:39 +03:00
<signal name="clicked" handler="on_boot_moveup_clicked" swapped="no"/>
2014-02-10 01:21:26 +04:00
<child>
<object class="GtkImage" id="image7">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="stock">gtk-go-up</property>
</object>
</child>
2018-01-21 01:25:16 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="boot-moveup-atkobject">
<property name="AtkObject::accessible-name">boot-moveup</property>
</object>
</child>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
2015-09-14 01:01:39 +03:00
<object class="GtkButton" id="boot-movedown">
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 18:18:47 +04:00
<property name="visible">True</property>
2014-02-10 01:21:26 +04:00
<property name="sensitive">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 18:18:47 +04:00
<property name="can_focus">True</property>
2014-02-10 01:21:26 +04:00
<property name="receives_default">True</property>
<property name="valign">start</property>
<property name="vexpand">False</property>
2015-09-14 01:01:39 +03:00
<signal name="clicked" handler="on_boot_movedown_clicked" swapped="no"/>
2014-02-10 01:21:26 +04:00
<child>
<object class="GtkImage" id="image8">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="stock">gtk-go-down</property>
</object>
</child>
2018-01-21 01:25:16 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="boot-movedown-atkobject">
<property name="AtkObject::accessible-name">boot-movedown</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 18:18:47 +04:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
2011-05-26 20:38:48 +04:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2014-02-10 01:21:26 +04:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
2011-05-26 20:38:48 +04:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2014-02-10 01:21:26 +04:00
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">1</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 18:18:47 +04:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2010-12-12 07:00:19 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2014-02-10 01:21:26 +04:00
</child>
<child type="label">
<object class="GtkLabel" id="label1">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>Boot device order</b></property>
<property name="use_markup">True</property>
</object>
2010-12-12 00:40:24 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2010-12-12 00:40:24 +03:00
<packing>
2014-02-10 01:21:26 +04:00
<property name="left_attach">0</property>
<property name="top_attach">1</property>
2010-12-12 00:40:24 +03:00
</packing>
</child>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="vbox4-atkobject">
<property name="AtkObject::accessible-name">boot-tab</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 18:18:47 +04:00
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">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 18:18:47 +04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="boot-options-lbl">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">boot</property>
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">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 18:18:47 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="vbox55">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</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 18:18:47 +04:00
<property name="spacing">12</property>
2010-12-12 00:40:24 +03:00
<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 18:18:47 +04:00
<object class="GtkFrame" id="frame10">
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
2010-12-12 00:40:24 +03:00
<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 18:18:47 +04:00
<object class="GtkAlignment" id="alignment149">
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
2010-12-12 00:40:24 +03:00
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="vbox13">
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</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 18:18:47 +04:00
<property name="spacing">12</property>
2010-12-12 00:40:24 +03:00
<child>
2013-10-04 16:01:18 +04:00
<object class="GtkGrid" id="table32">
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="border_width">3</property>
<property name="row_spacing">4</property>
2013-10-04 16:01:18 +04:00
<property name="column_spacing">8</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 18:18:47 +04:00
<child>
<object class="GtkLabel" id="permissions-label">
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</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 18:18:47 +04:00
<property name="label" translatable="yes">R_eadonly:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">disk-readonly</property>
</object>
<packing>
2013-10-04 16:01:18 +04:00
<property name="left_attach">0</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 18:18:47 +04:00
<property name="top_attach">3</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label3">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</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 18:18:47 +04:00
<property name="label" translatable="yes">Sharea_ble:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">disk-shareable</property>
</object>
<packing>
2013-10-04 16:01:18 +04:00
<property name="left_attach">0</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 18:18:47 +04:00
<property name="top_attach">4</property>
</packing>
</child>
<child>
<object class="GtkCheckButton" id="disk-readonly">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
<property name="draw_indicator">True</property>
<signal name="toggled" handler="on_disk_readonly_changed" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">3</property>
</packing>
</child>
<child>
<object class="GtkCheckButton" id="disk-shareable">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
2017-05-31 16:08:33 +03: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 18:18:47 +04:00
<property name="draw_indicator">True</property>
<signal name="toggled" handler="on_disk_shareable_changed" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">4</property>
</packing>
</child>
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkLabel" id="label4">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-09-28 20:21:35 +04:00
<property name="label" translatable="yes">Storage size:</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 18:18:47 +04:00
</object>
<packing>
2013-10-04 16:01:18 +04:00
<property name="left_attach">0</property>
2013-09-28 20:21:35 +04: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 18:18:47 +04:00
</packing>
</child>
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkLabel" id="disk-size">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-09-28 20:21:35 +04:00
<property name="label">size</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 18:18:47 +04:00
</object>
<packing>
<property name="left_attach">1</property>
2013-09-28 20:21:35 +04: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 18:18:47 +04:00
</packing>
</child>
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkLabel" id="label392">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-09-28 20:21:35 +04:00
<property name="label" translatable="yes">Source path:</property>
<property name="use_underline">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 18:18:47 +04:00
</object>
<packing>
2013-10-04 16:01:18 +04:00
<property name="left_attach">0</property>
<property name="top_attach">0</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 18:18:47 +04:00
</packing>
</child>
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkLabel" id="disk-target-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-09-28 20:21:35 +04:00
<property name="label">disk </property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkBox" id="box9">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2013-09-28 20:21:35 +04:00
<property name="spacing">6</property>
<child>
<object class="GtkLabel" id="disk-source-path">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-09-28 20:21:35 +04:00
<property name="label">path</property>
<property name="selectable">True</property>
<property name="ellipsize">start</property>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="disk-source-path-atkobject">
<property name="AtkObject::accessible-name">disk-source-path</property>
</object>
</child>
2013-09-28 20:21:35 +04:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
2010-12-12 00:40:24 +03:00
<child>
2015-09-14 01:01:39 +03:00
<object class="GtkButton" id="disk-cdrom-connect">
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 18:18:47 +04:00
<property name="label">gtk-connect</property>
2010-12-12 00:40:24 +03:00
<property name="visible">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 18:18:47 +04:00
<property name="can_focus">True</property>
<property name="can_default">True</property>
<property name="receives_default">True</property>
<property name="has_tooltip">True</property>
<property name="tooltip_text" translatable="yes">Connect or disconnect media</property>
<property name="use_stock">True</property>
2015-09-14 01:01:39 +03:00
<signal name="clicked" handler="on_disk_cdrom_connect_clicked" swapped="no"/>
2012-02-02 02:26:46 +04:00
</object>
2013-09-28 20:21:35 +04:00
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
2010-12-12 00:40:24 +03:00
</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 18:18:47 +04:00
</object>
<packing>
<property name="left_attach">1</property>
2013-10-04 16:01:18 +04:00
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label375">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-10-04 16:01:18 +04:00
<property name="label" translatable="yes">Device type:</property>
<property name="use_underline">True</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">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 18:18:47 +04:00
</packing>
</child>
2013-10-04 05:39:01 +04:00
<child>
<object class="GtkLabel" id="label46">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-10-04 05:39:01 +04:00
<property name="label" translatable="yes">Removab_le:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">disk-removable</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">5</property>
</packing>
</child>
<child>
<object class="GtkCheckButton" id="disk-removable">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-10-04 05:39:01 +04:00
<property name="use_stock">True</property>
<property name="draw_indicator">True</property>
<signal name="toggled" handler="on_disk_removable_changed" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">5</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 18:18:47 +04:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkExpander" id="expander4">
<property name="visible">True</property>
<property name="can_focus">True</property>
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkBox" id="box10">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2013-09-28 20:21:35 +04:00
<property name="orientation">vertical</property>
<property name="spacing">6</property>
2010-12-12 00:40:24 +03:00
<child>
2013-10-04 16:01:18 +04:00
<object class="GtkGrid" id="table11">
2010-12-12 00:40:24 +03:00
<property name="visible">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 18:18:47 +04:00
<property name="can_focus">False</property>
2013-09-28 20:21:35 +04:00
<property name="row_spacing">3</property>
2013-10-04 16:01:18 +04:00
<property name="column_spacing">8</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 18:18:47 +04:00
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkLabel" id="label32">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-09-28 20:21:35 +04:00
<property name="label" translatable="yes">Disk b_us:</property>
<property name="use_underline">True</property>
2014-12-12 13:31:11 +03:00
<property name="mnemonic_widget">disk-bus-combobox-entry</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 18:18:47 +04:00
</object>
<packing>
2013-10-04 16:01:18 +04:00
<property name="left_attach">0</property>
<property name="top_attach">0</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 18:18:47 +04:00
</packing>
</child>
2010-12-12 00:40:24 +03:00
<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 18:18:47 +04:00
<object class="GtkEntry" id="disk-serial">
2010-12-11 04:33:41 +03:00
<property name="visible">True</property>
2010-12-12 00:40:24 +03:00
<property name="can_focus">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 18:18:47 +04:00
<property name="invisible_char">●</property>
<property name="width_chars">20</property>
<signal name="changed" handler="on_disk_serial_changed" swapped="no"/>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
<packing>
2013-09-28 20:21:35 +04:00
<property name="left_attach">1</property>
<property name="top_attach">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 18:18:47 +04:00
</packing>
</child>
2013-09-28 20:21:35 +04:00
<child>
<object class="GtkComboBox" id="disk-bus">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="has_entry">True</property>
<signal name="changed" handler="on_disk_bus_combo_changed" swapped="no"/>
<child internal-child="entry">
2014-12-12 13:31:11 +03:00
<object class="GtkEntry" id="disk-bus-combobox-entry">
2013-09-28 20:21:35 +04:00
<property name="can_focus">True</property>
</object>
</child>
</object>
<packing>
<property name="left_attach">1</property>
2013-10-04 16:01:18 +04:00
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label6">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2014-12-12 13:31:11 +03:00
<property name="label" translatable="yes">Seria_l number:</property>
2013-10-04 16:01:18 +04:00
<property name="use_underline">True</property>
2014-12-12 13:31:11 +03:00
<property name="mnemonic_widget">disk-serial</property>
2013-10-04 16:01:18 +04:00
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
2014-04-22 01:04:33 +04:00
</packing>
</child>
<child>
<object class="GtkBox" id="box15">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<property name="spacing">6</property>
<child>
2015-09-14 02:05:02 +03:00
<object class="GtkEntry" id="disk-format">
2014-04-22 01:04:33 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
2015-09-14 02:05:02 +03:00
<signal name="changed" handler="on_disk_format_changed" swapped="no"/>
2014-04-22 01:04:33 +04:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkBox" id="disk-format-warn">
<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-dialog-warning</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="label34">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><small>Changing this will not change the disk image format, it only tells libvirt about the existing image format. </small></property>
<property name="use_markup">True</property>
<property name="wrap">True</property>
<property name="max_width_chars">30</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">False</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>
2015-03-13 16:39:47 +03:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">3</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label30">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2017-05-31 16:08:36 +03:00
<property name="valign">start</property>
2017-05-31 16:08:38 +03:00
<property name="margin_top">4</property>
<property name="margin_bottom">4</property>
2015-03-13 16:39:47 +03:00
<property name="label" translatable="yes">Storage forma_t:</property>
<property name="use_underline">True</property>
2015-09-14 02:05:02 +03:00
<property name="mnemonic_widget">disk-format</property>
2015-03-13 16:39:47 +03:00
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">3</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label66">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2015-03-13 16:39:47 +03:00
<property name="label" translatable="yes">_SGIO:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">disk-sgio-entry</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkComboBox" id="disk-sgio">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="has_entry">True</property>
<child internal-child="entry">
<object class="GtkEntry" id="disk-sgio-entry">
<property name="can_focus">True</property>
<signal name="changed" handler="on_disk_sgio_entry_changed" swapped="no"/>
</object>
</child>
</object>
2014-04-22 01:04:33 +04:00
<packing>
<property name="left_attach">1</property>
<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 18:18:47 +04:00
</packing>
2010-12-12 00:40:24 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2010-12-12 00:40:24 +03:00
<packing>
2013-09-28 20:21:35 +04:00
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
2010-12-12 00:40:24 +03:00
</packing>
</child>
<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 18:18:47 +04:00
<object class="GtkExpander" id="expander8">
2010-12-12 00:40:24 +03:00
<property name="visible">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 18:18:47 +04:00
<property name="can_focus">True</property>
2010-12-12 00:40:24 +03:00
<child>
2013-10-04 16:01:18 +04:00
<object class="GtkGrid" id="table19">
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="row_spacing">3</property>
2013-10-04 16:01:18 +04:00
<property name="column_spacing">8</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 18:18:47 +04:00
<child>
<object class="GtkLabel" id="label123">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</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 18:18:47 +04:00
<property name="label" translatable="yes">Cac_he mode:</property>
<property name="use_underline">True</property>
2014-12-12 13:31:11 +03:00
<property name="mnemonic_widget">cachemode-entry-box</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 18:18:47 +04:00
</object>
<packing>
2013-10-04 16:01:18 +04:00
<property name="left_attach">0</property>
<property name="top_attach">0</property>
2010-12-12 00:40:24 +03:00
</packing>
</child>
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkComboBox" id="disk-cache">
2010-12-11 04:33:41 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2013-09-28 20:21:35 +04:00
<property name="has_entry">True</property>
<signal name="changed" handler="on_disk_cache_combo_changed" swapped="no"/>
<child internal-child="entry">
2014-12-12 13:31:11 +03:00
<object class="GtkEntry" id="cachemode-entry-box">
2013-09-28 20:21:35 +04:00
<property name="can_focus">True</property>
2012-02-02 02:26:46 +04:00
</object>
2010-12-12 00:40:24 +03:00
</child>
2013-09-28 20:21:35 +04:00
</object>
<packing>
<property name="left_attach">1</property>
2013-10-04 16:01:18 +04:00
<property name="top_attach">0</property>
2013-09-28 20:21:35 +04:00
</packing>
</child>
<child>
<object class="GtkComboBox" id="disk-io">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2013-09-28 20:21:35 +04:00
<property name="has_entry">True</property>
<signal name="changed" handler="on_disk_io_combo_changed" swapped="no"/>
<child internal-child="entry">
2014-12-12 13:31:11 +03:00
<object class="GtkEntry" id="iomode-entry-box">
2013-09-28 20:21:35 +04:00
<property name="can_focus">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 18:18:47 +04:00
</object>
</child>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
2013-10-04 16:01:18 +04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="label79">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-10-04 16:01:18 +04:00
<property name="label" translatable="yes">_IO mode:</property>
<property name="use_underline">True</property>
2014-12-12 13:31:11 +03:00
<property name="mnemonic_widget">iomode-entry-box</property>
2013-10-04 16:01:18 +04:00
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
2010-12-12 00:40:24 +03:00
</packing>
2010-12-11 04:33:41 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2011-07-13 21:16:19 +04:00
</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 18:18:47 +04:00
<child type="label">
<object class="GtkLabel" id="label78">
2011-07-13 21:16:19 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="label" translatable="yes">_Performance options</property>
2011-07-13 21:16:19 +04:00
<property name="use_underline">True</property>
2012-02-02 02:26:46 +04:00
</object>
2011-07-24 04:41:35 +04:00
</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 18:18:47 +04:00
</object>
<packing>
2013-09-28 20:21:35 +04:00
<property name="expand">False</property>
<property name="fill">True</property>
<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 18:18:47 +04:00
</packing>
</child>
2012-02-02 02:26:46 +04:00
</object>
2011-03-17 23:33:40 +03:00
</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 18:18:47 +04:00
<child type="label">
<object class="GtkLabel" id="label31">
2011-04-19 15:08:15 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="label" translatable="yes">Advanced _options</property>
2010-12-12 00:40:24 +03:00
<property name="use_underline">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 18:18:47 +04:00
<property name="mnemonic_widget">expander4</property>
2012-02-02 02:26:46 +04:00
</object>
2010-12-12 00:40:24 +03:00
</child>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
2010-12-12 00:40:24 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2010-12-12 00:40:24 +03:00
</child>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
</child>
<child type="label">
<object class="GtkLabel" id="label376">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>Virtual Disk</b></property>
<property name="use_markup">True</property>
</object>
2009-02-09 22:55:18 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2009-02-09 22:55:18 +03:00
<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 18:18:47 +04:00
<property name="expand">False</property>
2013-09-28 20:21:35 +04:00
<property name="fill">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 18:18:47 +04:00
<property name="position">0</property>
2009-02-09 22:55:18 +03:00
</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 18:18:47 +04:00
<child>
2017-05-31 16:08:32 +03:00
<object class="GtkButtonBox" id="hbuttonbox9">
2009-02-09 22:55:18 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="spacing">5</property>
<property name="layout_style">end</property>
2012-02-02 02:26:46 +04:00
</object>
2009-02-09 22:55:18 +03:00
<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 18:18:47 +04:00
<property name="expand">False</property>
<property name="fill">False</property>
<property name="pack_type">end</property>
<property name="position">1</property>
2009-02-09 22:55:18 +03:00
</packing>
</child>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="vbox55-atkobject">
<property name="AtkObject::accessible-name">disk-tab</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 18:18:47 +04:00
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">6</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 18:18:47 +04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label55">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">dsk</property>
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">6</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 18:18:47 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="vbox54">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</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 18:18:47 +04:00
<property name="spacing">12</property>
2009-02-09 22:55:18 +03:00
<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 18:18:47 +04:00
<object class="GtkFrame" id="frame9">
2009-02-09 22:55:18 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
2009-02-09 22:55:18 +03:00
<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 18:18:47 +04:00
<object class="GtkAlignment" id="alignment137">
2009-02-09 22:55:18 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
2008-10-31 17:18:55 +03:00
<child>
2013-09-09 19:37:32 +04:00
<object class="GtkGrid" id="table31">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="border_width">3</property>
2013-09-09 19:37:32 +04:00
<property name="row_spacing">6</property>
<property name="column_spacing">6</property>
<child>
<object class="GtkLabel" id="label509">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2014-01-28 01:58:45 +04:00
<property name="label" translatable="yes">Device mode_l:</property>
2013-09-09 19:37:32 +04:00
<property name="use_underline">True</property>
2014-12-12 13:31:11 +03:00
<property name="mnemonic_widget">network-model-combobox</property>
2013-09-09 19:37:32 +04:00
</object>
<packing>
<property name="left_attach">0</property>
2014-01-28 01:58:45 +04:00
<property name="top_attach">1</property>
2013-09-09 19:37:32 +04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="mac-address-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-09-09 19:37:32 +04:00
<property name="label" translatable="yes">MAC address:</property>
<property name="use_underline">True</property>
</object>
<packing>
<property name="left_attach">0</property>
2014-01-28 01:58:45 +04:00
<property name="top_attach">2</property>
2013-09-09 19:37:32 +04:00
</packing>
</child>
<child>
2014-01-28 01:58:45 +04:00
<object class="GtkComboBox" id="network-model">
2013-09-09 19:37:32 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2014-01-28 01:58:45 +04:00
<property name="halign">start</property>
<property name="hexpand">False</property>
<property name="has_entry">True</property>
<signal name="changed" handler="on_network_model_combo_changed" swapped="no"/>
<child internal-child="entry">
2014-12-12 13:31:11 +03:00
<object class="GtkEntry" id="network-model-combobox">
2013-09-09 19:37:32 +04:00
<property name="can_focus">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 18:18:47 +04:00
</object>
2011-03-17 21:24:36 +03:00
</child>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
<packing>
<property name="left_attach">1</property>
2013-09-09 19:37:32 +04:00
<property name="top_attach">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 18:18:47 +04:00
</packing>
</child>
<child>
2014-01-28 01:58:45 +04:00
<object class="GtkAlignment" id="network-source-label-align">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2014-01-28 01:58:45 +04:00
<property name="hexpand">False</property>
<property name="vexpand">False</property>
2013-09-09 19:37:32 +04:00
<child>
<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 18:18:47 +04:00
</object>
<packing>
2013-09-09 19:37:32 +04:00
<property name="left_attach">0</property>
2014-01-28 01:58:45 +04:00
<property name="top_attach">0</property>
2013-09-28 20:21:35 +04:00
</packing>
</child>
<child>
2014-01-28 01:58:45 +04:00
<object class="GtkAlignment" id="network-source-ui-align">
2013-09-28 20:21:35 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2014-01-28 01:58:45 +04:00
<property name="hexpand">False</property>
<property name="vexpand">False</property>
<child>
<placeholder/>
2013-09-09 19:37:32 +04:00
</child>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</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 18:18:47 +04:00
</packing>
</child>
2015-04-08 01:52:35 +03:00
<child>
<object class="GtkBox" id="box18">
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<object class="GtkLabel" id="network-mac-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2015-04-08 01:52:35 +03:00
<property name="label">mac</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkEntry" id="network-mac-entry">
<property name="visible">True</property>
<property name="can_focus">True</property>
<signal name="changed" handler="on_network_mac_entry_changed" swapped="no"/>
</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>
<property name="top_attach">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 18:18:47 +04:00
</object>
</child>
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label367">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>Virtual Network Interface</b></property>
<property name="use_markup">True</property>
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
2014-01-28 01:58:45 +04:00
<object class="GtkAlignment" id="network-vport-align">
<property name="visible">True</property>
<property name="can_focus">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 18:18:47 +04:00
<child>
2014-01-28 01:58:45 +04:00
<placeholder/>
2009-07-09 22:35:36 +04:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2009-07-09 22:35:36 +04:00
<packing>
2014-01-28 01:58:45 +04:00
<property name="expand">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 18:18:47 +04:00
<property name="fill">True</property>
<property name="position">1</property>
2009-02-09 22:55:18 +03:00
</packing>
</child>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="vbox54-atkobject">
<property name="AtkObject::accessible-name">network-tab</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 18:18:47 +04:00
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">7</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 18:18:47 +04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label56">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">net</property>
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">7</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 18:18:47 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="vbox56">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</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 18:18:47 +04:00
<property name="spacing">12</property>
2009-02-09 22:55:18 +03:00
<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 18:18:47 +04:00
<object class="GtkFrame" id="frame11">
2009-02-09 22:55:18 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
2009-02-09 22:55:18 +03:00
<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 18:18:47 +04:00
<object class="GtkAlignment" id="alignment150">
2009-02-09 22:55:18 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
2009-01-23 01:00:38 +03:00
<child>
2014-05-04 21:23:54 +04:00
<object class="GtkGrid" id="table33">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="border_width">3</property>
<property name="row_spacing">4</property>
2014-05-04 21:23:54 +04:00
<property name="column_spacing">8</property>
2009-07-09 22:35:36 +04:00
<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 18:18:47 +04:00
<object class="GtkLabel" id="label402">
2009-07-09 22:35:36 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</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 18:18:47 +04:00
<property name="label" translatable="yes">Type:</property>
<property name="use_underline">True</property>
</object>
<packing>
2014-05-04 21:23:54 +04:00
<property name="left_attach">0</property>
<property name="top_attach">0</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 18:18:47 +04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="label405">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</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 18:18:47 +04:00
<property name="label" translatable="yes">Mode:</property>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
<packing>
2014-05-04 21:23:54 +04:00
<property name="left_attach">0</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 18:18:47 +04:00
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="input-dev-mode">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03: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 18:18:47 +04:00
<property name="label">label401</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="input-dev-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03: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 18:18:47 +04:00
<property name="label">label403</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
2014-05-04 21:23:54 +04:00
<property name="top_attach">0</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 18:18:47 +04:00
</packing>
2009-02-09 22:55:18 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2010-12-12 00:40:24 +03:00
</child>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
</child>
<child type="label">
<object class="GtkLabel" id="label407">
<property name="visible">True</property>
<property name="can_focus">False</property>
2015-04-09 20:36:40 +03:00
<property name="label" translatable="yes"><b>Virtual Input Device</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 18:18:47 +04:00
<property name="use_markup">True</property>
</object>
2009-01-23 01:00:38 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2009-01-23 01:00:38 +03:00
<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 18:18:47 +04:00
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">0</property>
2009-02-09 22:55:18 +03:00
</packing>
2009-01-23 01:00:38 +03:00
</child>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="vbox56-atkobject">
<property name="AtkObject::accessible-name">input-tab</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 18:18:47 +04:00
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">8</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 18:18:47 +04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label401">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">inp</property>
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">8</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 18:18:47 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="vbox57">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</property>
2009-01-23 01:00:38 +03:00
<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 18:18:47 +04:00
<object class="GtkFrame" id="vnc-frame">
2009-01-23 01:00:38 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
2009-01-23 01:00:38 +03:00
<child>
2014-01-29 03:44:40 +04:00
<object class="GtkAlignment" id="graphics-align">
2009-01-23 01:00:38 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
2009-01-23 01:00:38 +03:00
<child>
2014-01-29 03:44:40 +04:00
<placeholder/>
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 18:18:47 +04:00
</child>
</object>
</child>
<child type="label">
<object class="GtkLabel" id="graphics-title">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label"><b>Display title</b></property>
<property name="use_markup">True</property>
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="vbox57-atkobject">
<property name="AtkObject::accessible-name">graphics-tab</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 18:18:47 +04:00
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">9</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 18:18:47 +04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label500">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">gfx</property>
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">9</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 18:18:47 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="vbox58">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</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 18:18:47 +04:00
<child>
<object class="GtkFrame" id="frame13">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<child>
<object class="GtkAlignment" id="alignment159">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<child>
2017-05-31 16:08:40 +03:00
<object class="GtkGrid" id="table36">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="border_width">3</property>
<property name="row_spacing">4</property>
2017-05-31 16:08:40 +03:00
<property name="column_spacing">8</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 18:18:47 +04:00
<child>
<object class="GtkLabel" id="label452">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2017-05-31 16:08:40 +03:00
<property name="valign">center</property>
2018-01-21 02:21:54 +03:00
<property name="label" translatable="yes">M_odel:</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 18:18:47 +04:00
<property name="use_underline">True</property>
2014-12-12 13:31:11 +03:00
<property name="mnemonic_widget">combobox-entry12</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 18:18:47 +04:00
</object>
<packing>
2017-05-31 16:08:40 +03:00
<property name="left_attach">0</property>
<property name="top_attach">0</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 18:18:47 +04:00
</packing>
</child>
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkComboBox" id="sound-model">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2013-09-28 20:21:35 +04:00
<property name="has_entry">True</property>
<signal name="changed" handler="on_sound_model_combo_changed" swapped="no"/>
<child internal-child="entry">
<object class="GtkEntry" id="combobox-entry12">
<property name="can_focus">True</property>
2012-02-02 02:26:46 +04:00
</object>
2011-04-05 03:35:33 +04:00
</child>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
<packing>
<property name="left_attach">1</property>
2017-05-31 16:08:40 +03:00
<property name="top_attach">0</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 18:18:47 +04:00
</packing>
</child>
</object>
</child>
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label451">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>Sound Device</b></property>
<property name="use_markup">True</property>
</object>
</child>
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="vbox58-atkobject">
<property name="AtkObject::accessible-name">sound-tab</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 18:18:47 +04:00
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">10</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 18:18:47 +04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label440">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">snd</property>
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">10</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 18:18:47 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="vbox59">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</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 18:18:47 +04:00
<child>
<object class="GtkFrame" id="frame14">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<child>
<object class="GtkAlignment" id="alignment160">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkGrid" id="table37">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="border_width">3</property>
2013-09-28 20:21:35 +04:00
<property name="row_spacing">4</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 18:18:47 +04:00
<property name="column_spacing">8</property>
<child>
<object class="GtkLabel" id="char-dev-type-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</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 18:18:47 +04:00
<property name="label" translatable="yes">Device type:</property>
</object>
<packing>
2013-09-28 20:21:35 +04:00
<property name="left_attach">0</property>
<property name="top_attach">0</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 18:18:47 +04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="char-dev-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03: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 18:18:47 +04:00
<property name="label" translatable="yes">label506</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
2013-09-28 20:21:35 +04:00
<property name="top_attach">0</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 18:18:47 +04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="char-source-path">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03: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 18:18:47 +04:00
<property name="label" translatable="yes">label508</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkLabel" id="char-bind-host">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-09-28 20:21:35 +04:00
<property name="label">label</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 18:18:47 +04:00
</object>
<packing>
2013-09-28 20:21:35 +04:00
<property name="left_attach">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 18:18:47 +04:00
<property name="top_attach">3</property>
2013-09-28 20:21:35 +04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="char-target-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-09-28 20:21:35 +04:00
<property name="label">label</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">4</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="char-target-name">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-09-28 20:21:35 +04:00
<property name="label" translatable="yes">label508</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<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 18:18:47 +04:00
</packing>
</child>
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkLabel" id="char-source-host">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03: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 18:18:47 +04:00
<property name="label">label</property>
</object>
<packing>
<property name="left_attach">1</property>
2013-09-28 20:21:35 +04: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 18:18:47 +04:00
</packing>
</child>
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkLabel" id="char-source-host-label">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-09-28 20:21:35 +04:00
<property name="label" translatable="yes">Source host:</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 18:18:47 +04:00
</object>
<packing>
2013-09-28 20:21:35 +04:00
<property name="left_attach">0</property>
<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 18:18:47 +04:00
</packing>
</child>
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkLabel" id="char-bind-host-label">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-09-28 20:21:35 +04:00
<property name="label" translatable="yes">Bind host:</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 18:18:47 +04:00
</object>
<packing>
2013-09-28 20:21:35 +04:00
<property name="left_attach">0</property>
<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 18:18:47 +04:00
</packing>
</child>
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkLabel" id="char-target-type-label">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-09-28 20:21:35 +04:00
<property name="label" translatable="yes">Target type:</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 18:18:47 +04:00
</object>
<packing>
2013-09-28 20:21:35 +04:00
<property name="left_attach">0</property>
<property name="top_attach">4</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 18:18:47 +04:00
</packing>
</child>
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkLabel" id="char-target-name-label">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-09-28 20:21:35 +04:00
<property name="label" translatable="yes">Target name:</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 18:18:47 +04:00
</object>
<packing>
2013-09-28 20:21:35 +04:00
<property name="left_attach">0</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 18:18:47 +04:00
<property name="top_attach">5</property>
</packing>
2009-02-09 22:55:18 +03:00
</child>
2009-07-09 22:35:55 +04:00
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkLabel" id="char-source-path-label">
2009-07-09 22:35:55 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-09-28 20:21:35 +04:00
<property name="label" translatable="yes">Source path:</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 18:18:47 +04:00
</object>
<packing>
2013-09-28 20:21:35 +04:00
<property name="left_attach">0</property>
<property name="top_attach">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 18:18:47 +04:00
</packing>
2009-07-09 22:35:36 +04:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2010-12-12 00:40:24 +03:00
</child>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
</child>
<child type="label">
<object class="GtkLabel" id="char-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>insert type</b></property>
<property name="use_markup">True</property>
</object>
2010-12-12 00:40:24 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2010-12-12 00:40:24 +03:00
<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 18:18:47 +04:00
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
2010-12-12 00:40:24 +03:00
</packing>
</child>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="vbox59-atkobject">
<property name="AtkObject::accessible-name">char-tab</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 18:18:47 +04:00
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">11</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 18:18:47 +04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label501">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">chr</property>
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">11</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 18:18:47 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="vbox8">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</property>
2010-12-12 00:40:24 +03:00
<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 18:18:47 +04:00
<object class="GtkFrame" id="frame6">
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
2010-12-12 00:40:24 +03:00
<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 18:18:47 +04:00
<object class="GtkAlignment" id="alignment22">
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
2010-12-12 00:40:24 +03:00
<child>
2014-02-10 23:24:22 +04:00
<object class="GtkGrid" id="table50">
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2014-02-10 23:24:22 +04:00
<property name="row_spacing">6</property>
<property name="column_spacing">6</property>
2009-11-05 22:59:11 +03:00
<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 18:18:47 +04:00
<object class="GtkLabel" id="label15">
2009-11-05 22:59:11 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03: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 18:18:47 +04:00
<property name="label" translatable="yes">Device:</property>
</object>
<packing>
2014-02-10 23:24:22 +04:00
<property name="left_attach">0</property>
<property name="top_attach">0</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 18:18:47 +04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="hostdev-source">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03: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 18:18:47 +04:00
<property name="label">label</property>
<property name="selectable">True</property>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
<packing>
<property name="left_attach">1</property>
2014-02-10 23:24:22 +04:00
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label5">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-02-10 23:24:22 +04:00
<property name="label" translatable="yes">ROM _BAR:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">hostdev-rombar</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkCheckButton" id="hostdev-rombar">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-02-10 23:24:22 +04:00
<property name="draw_indicator">True</property>
<signal name="toggled" handler="on_hostdev_rombar_toggled" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">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 18:18:47 +04:00
</packing>
2009-11-05 22:59:11 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2009-07-09 22:35:36 +04:00
</child>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
</child>
<child type="label">
<object class="GtkLabel" id="hostdev-title">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label"><b>Physical Host Device</b></property>
<property name="use_markup">True</property>
</object>
2009-07-09 22:35:36 +04:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2009-02-09 22:55:18 +03:00
<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 18:18:47 +04:00
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
2009-02-09 22:55:18 +03:00
</packing>
2008-10-31 17:18:55 +03:00
</child>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="vbox8-atkobject">
<property name="AtkObject::accessible-name">host-tab</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 18:18:47 +04:00
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">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 18:18:47 +04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label16">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">phy</property>
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">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 18:18:47 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="vbox9">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</property>
2010-03-24 07:22:17 +03:00
<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 18:18:47 +04:00
<object class="GtkFrame" id="frame8">
2010-03-24 07:22:17 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
2010-03-24 07:22:17 +03:00
<child>
2017-02-21 16:01:02 +03:00
<object class="GtkGrid">
2010-03-24 07:22:17 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-02-21 16:01:02 +03:00
<property name="margin_left">12</property>
<property name="margin_top">3</property>
<property name="row_spacing">6</property>
<property name="column_spacing">6</property>
2010-03-24 07:22:17 +03:00
<child>
2017-02-21 16:01:02 +03:00
<object class="GtkLabel" id="label18">
2010-03-24 07:22:17 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2017-02-21 16:01:02 +03:00
<property name="label" translatable="yes">M_odel:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">combobox-entry13</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkComboBox" id="video-model">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="has_entry">True</property>
<signal name="changed" handler="on_video_model_combo_changed" swapped="no"/>
<child internal-child="entry">
<object class="GtkEntry" id="combobox-entry13">
<property name="can_focus">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 18:18:47 +04:00
</object>
</child>
2017-02-21 16:01:02 +03:00
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label17">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2017-02-21 16:01:02 +03:00
<property name="label" translatable="yes">RAM:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="video-ram">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2017-02-21 16:01:02 +03:00
<property name="label">label</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label25">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2017-02-21 16:01:02 +03:00
<property name="label" translatable="yes">Heads:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="video-heads">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2017-02-21 16:01:02 +03:00
<property name="label">label</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label9">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2018-01-21 02:21:54 +03:00
<property name="label" translatable="yes">_3D acceleration:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">video-3d</property>
2017-02-21 16:01:02 +03:00
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">3</property>
</packing>
</child>
<child>
<object class="GtkCheckButton" id="video-3d">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
<property name="draw_indicator">True</property>
<signal name="toggled" handler="on_video_3d_toggled" 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 18:18:47 +04:00
<child>
2017-02-21 16:01:02 +03:00
<placeholder/>
2010-03-24 07:22:17 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2017-02-21 16:01:02 +03:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">3</property>
</packing>
2010-03-24 07:22:17 +03:00
</child>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
</child>
<child type="label">
<object class="GtkLabel" id="hostdev-title1">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>Video</b></property>
<property name="use_markup">True</property>
</object>
2010-03-24 07:22:17 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2010-03-24 07:22:17 +03:00
<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 18:18:47 +04:00
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
2010-03-24 07:22:17 +03:00
</packing>
</child>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="vbox9-atkobject">
<property name="AtkObject::accessible-name">video-tab</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 18:18:47 +04:00
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">13</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 18:18:47 +04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label26">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">vid</property>
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">13</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 18:18:47 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="vbox12">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</property>
2010-12-16 20:41:47 +03:00
<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 18:18:47 +04:00
<object class="GtkFrame" id="frame15">
2010-12-16 20:41:47 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2010-12-16 20:41:47 +03:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<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 18:18:47 +04:00
<object class="GtkAlignment" id="alignment34">
2010-12-16 20:41:47 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2010-12-16 20:41:47 +03:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<child>
2017-05-31 16:08:40 +03:00
<object class="GtkGrid" id="table8">
2010-12-16 20:41:47 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="row_spacing">4</property>
2017-05-31 16:08:40 +03:00
<property name="column_spacing">8</property>
2010-12-16 20:41:47 +03:00
<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 18:18:47 +04:00
<object class="GtkLabel" id="label27">
2010-12-16 20:41:47 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2017-05-31 16:08:40 +03:00
<property name="valign">center</property>
2014-11-11 11:02:02 +03:00
<property name="label" translatable="yes">Ac_tion:</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 18:18:47 +04:00
<property name="use_underline">True</property>
2014-11-11 11:02:02 +03:00
<property name="mnemonic_widget">combobox-entry14</property>
2012-02-02 02:26:46 +04:00
</object>
2010-12-16 20:41:47 +03:00
<packing>
2017-05-31 16:08:40 +03:00
<property name="left_attach">0</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 18:18:47 +04:00
<property name="top_attach">1</property>
2010-12-16 20:41:47 +03:00
</packing>
</child>
<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 18:18:47 +04:00
<object class="GtkLabel" id="label35">
2010-12-16 20:41:47 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2017-05-31 16:08:40 +03:00
<property name="valign">center</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 18:18:47 +04:00
<property name="label" translatable="yes">M_odel:</property>
<property name="use_underline">True</property>
2014-11-11 11:02:02 +03:00
<property name="mnemonic_widget">combobox-entry15</property>
2012-02-02 02:26:46 +04:00
</object>
2010-12-16 20:41:47 +03:00
<packing>
2017-05-31 16:08:40 +03:00
<property name="left_attach">0</property>
<property name="top_attach">0</property>
2010-12-16 20:41:47 +03:00
</packing>
</child>
2011-09-02 05:23:26 +04:00
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkComboBox" id="watchdog-action">
2011-09-02 05:23:26 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2013-09-28 20:21:35 +04:00
<property name="has_entry">True</property>
<signal name="changed" handler="on_watchdog_action_combo_changed" swapped="no"/>
<child internal-child="entry">
<object class="GtkEntry" id="combobox-entry14">
<property name="can_focus">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 18:18:47 +04:00
</object>
</child>
2012-02-02 02:26:46 +04:00
</object>
2011-09-02 05:23:26 +04:00
<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 18:18:47 +04:00
<property name="left_attach">1</property>
2013-09-28 20:21:35 +04:00
<property name="top_attach">1</property>
2011-09-02 05:23:26 +04:00
</packing>
</child>
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkComboBox" id="watchdog-model">
2011-09-02 05:23:26 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2013-09-28 20:21:35 +04:00
<property name="has_entry">True</property>
<signal name="changed" handler="on_watchdog_model_combo_changed" swapped="no"/>
<child internal-child="entry">
<object class="GtkEntry" id="combobox-entry15">
<property name="can_focus">True</property>
2012-02-02 02:26:46 +04:00
</object>
2011-09-23 19:14:15 +04:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2011-09-02 05:23:26 +04:00
<packing>
<property name="left_attach">1</property>
2017-05-31 16:08:40 +03:00
<property name="top_attach">0</property>
2011-09-02 05:23:26 +04:00
</packing>
</child>
2012-02-02 02:26:46 +04:00
</object>
2010-12-16 20:41:47 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2010-12-16 20:41:47 +03:00
</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 18:18:47 +04:00
<child type="label">
<object class="GtkLabel" id="hostdev-title2">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label"><b>Watchdog</b></property>
<property name="use_markup">True</property>
</object>
</child>
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="vbox12-atkobject">
<property name="AtkObject::accessible-name">watchdog-tab</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 18:18:47 +04:00
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">14</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 18:18:47 +04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label36">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">wdog</property>
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">14</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 18:18:47 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkFrame" id="frame12">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<child>
<object class="GtkAlignment" id="alignment35">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<child>
2013-10-04 00:34:28 +04:00
<object class="GtkGrid" id="table14">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="row_spacing">6</property>
2013-10-04 00:34:28 +04:00
<property name="column_spacing">6</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 18:18:47 +04:00
<child>
<object class="GtkLabel" id="label48">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</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 18:18:47 +04:00
<property name="label" translatable="yes">Type:</property>
</object>
<packing>
2013-10-04 00:34:28 +04:00
<property name="left_attach">0</property>
<property name="top_attach">0</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 18:18:47 +04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="controller-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03: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 18:18:47 +04:00
<property name="label">foo</property>
</object>
<packing>
<property name="left_attach">1</property>
2013-10-04 00:34:28 +04:00
<property name="top_attach">0</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 18:18:47 +04:00
</packing>
</child>
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkComboBox" id="controller-model">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2013-09-28 20:21:35 +04:00
<property name="has_entry">True</property>
<signal name="changed" handler="on_controller_model_combo_changed" swapped="no"/>
<child internal-child="entry">
<object class="GtkEntry" id="combobox-entry16">
<property name="can_focus">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 18:18:47 +04:00
</object>
</child>
2018-01-21 02:21:54 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="controller-model-atkobject">
<property name="AtkObject::accessible-name">controller-model</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 18:18:47 +04:00
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
2013-10-04 00:34:28 +04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="mlabel48">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-11-23 12:32:48 +03:00
<property name="halign">end</property>
<property name="hexpand">False</property>
2014-11-11 11:04:28 +03:00
<property name="label" translatable="yes">M_odel:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">combobox-entry16</property>
2013-10-04 00:34:28 +04:00
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">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 18:18:47 +04:00
</packing>
2017-11-23 12:32:48 +03:00
</child>
<child>
<object class="GtkLabel" id="device-list-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="valign">start</property>
<property name="vexpand">False</property>
<property name="label" translatable="yes">Devices:</property>
<property name="use_markup">True</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkBox" id="controller-device-box">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<property name="spacing">3</property>
<child>
<object class="GtkScrolledWindow" id="controller-device-scroll">
<property name="width_request">270</property>
<property name="height_request">100</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="shadow_type">in</property>
<child>
<object class="GtkTreeView" id="controller-device-list">
<property name="visible">True</property>
<property name="can_focus">True</property>
<child internal-child="selection">
<object class="GtkTreeSelection" id="controller-device-selection"/>
</child>
</object>
</child>
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">2</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 18:18:47 +04:00
</child>
</object>
</child>
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label42">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>Controller</b></property>
<property name="use_markup">True</property>
</object>
</child>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="frame12-atkobject">
<property name="AtkObject::accessible-name">controller-tab</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 18:18:47 +04:00
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">15</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 18:18:47 +04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label47">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">ctrl</property>
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">15</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 18:18:47 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkFrame" id="frame16">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<child>
2014-01-21 13:05:31 +04:00
<object class="GtkAlignment" id="fs-alignment">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<child>
2014-01-21 13:05:31 +04:00
<placeholder/>
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 18:18:47 +04:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2010-12-16 20:41:47 +03:00
</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 18:18:47 +04:00
<child type="label">
<object class="GtkLabel" id="label41">
2010-12-16 20:41:47 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="label" translatable="yes"><b>Filesystem</b></property>
<property name="use_markup">True</property>
2012-02-02 02:26:46 +04:00
</object>
2010-12-16 20:41:47 +03:00
</child>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="frame16-atkobject">
<property name="AtkObject::accessible-name">filesystem-tab</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 18:18:47 +04:00
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">16</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 18:18:47 +04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label63">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">fs</property>
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">16</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 18:18:47 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="vbox16">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</property>
2011-05-19 23:18:33 +04:00
<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 18:18:47 +04:00
<object class="GtkFrame" id="frame18">
2011-05-19 23:18:33 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2011-05-19 23:18:33 +04:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<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 18:18:47 +04:00
<object class="GtkAlignment" id="alignment46">
2011-05-19 23:18:33 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2011-05-19 23:18:33 +04:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<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 18:18:47 +04:00
<object class="GtkTable" id="table18">
2011-05-19 23:18:33 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="border_width">3</property>
2011-05-19 23:18:33 +04:00
<property name="n_columns">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 18:18:47 +04:00
<property name="column_spacing">8</property>
<property name="row_spacing">4</property>
2011-05-19 23:18:33 +04:00
<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 18:18:47 +04:00
<object class="GtkLabel" id="label74">
2011-05-19 23:18:33 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03: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 18:18:47 +04:00
<property name="label" translatable="yes">M_ode:</property>
<property name="use_underline">True</property>
2014-11-11 11:08:02 +03:00
<property name="mnemonic_widget">combobox-entry17</property>
2012-02-02 02:26:46 +04:00
</object>
2011-05-19 23:18:33 +04:00
<packing>
<property name="x_options">GTK_FILL</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 18:18:47 +04:00
<property name="y_options"/>
2011-05-19 23:18:33 +04:00
</packing>
</child>
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkComboBox" id="smartcard-mode">
2011-05-19 23:18:33 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2013-09-28 20:21:35 +04:00
<property name="has_entry">True</property>
<signal name="changed" handler="on_smartcard_mode_combo_changed" swapped="no"/>
<child internal-child="entry">
<object class="GtkEntry" id="combobox-entry17">
<property name="can_focus">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 18:18:47 +04:00
</object>
</child>
2018-01-21 02:21:54 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="smartcard-mode-atkobject">
<property name="AtkObject::accessible-name">smartcard-mode</property>
</object>
</child>
2012-02-02 02:26:46 +04:00
</object>
2011-05-19 23:18:33 +04:00
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="x_options">GTK_FILL</property>
2013-09-28 20:21:35 +04:00
<property name="y_options">GTK_FILL</property>
2011-05-19 23:18:33 +04:00
</packing>
</child>
2012-02-02 02:26:46 +04:00
</object>
2011-05-19 23:18:33 +04:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2011-05-19 23:18:33 +04:00
</child>
2012-02-02 02:26:46 +04:00
<child type="label">
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 18:18:47 +04:00
<object class="GtkLabel" id="label75">
2011-05-19 23:18:33 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="label" translatable="yes"><b>Smartcard Device</b></property>
2011-05-19 23:18:33 +04:00
<property name="use_markup">True</property>
2012-02-02 02:26:46 +04:00
</object>
2011-05-19 23:18:33 +04:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2011-05-19 23:18:33 +04:00
<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 18:18:47 +04:00
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
2011-05-19 23:18:33 +04:00
</packing>
</child>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="vbox16-atkobject">
<property name="AtkObject::accessible-name">smartcard-tab</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 18:18:47 +04:00
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">17</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 18:18:47 +04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label76">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">sc</property>
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">17</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 18:18:47 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkFrame" id="frame19">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
2011-06-23 19:42:03 +04:00
<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 18:18:47 +04:00
<object class="GtkAlignment" id="alignment161">
2011-06-23 19:42:03 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
2011-06-23 19:42:03 +04:00
<child>
2014-09-20 18:23:19 +04:00
<object class="GtkGrid" id="table51">
2011-06-23 19:42:03 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="border_width">3</property>
<property name="row_spacing">4</property>
2014-09-20 18:23:19 +04:00
<property name="column_spacing">8</property>
2011-06-23 19:42:03 +04:00
<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 18:18:47 +04:00
<object class="GtkLabel" id="label516">
2011-06-23 19:42:03 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2014-11-11 11:10:04 +03:00
<property name="label" translatable="yes">Type:</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 18:18:47 +04:00
</object>
<packing>
2014-09-20 18:23:19 +04:00
<property name="left_attach">0</property>
<property name="top_attach">0</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 18:18:47 +04:00
</packing>
</child>
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkLabel" id="label519">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-09-28 20:21:35 +04:00
<property name="label" translatable="yes">Address:</property>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
<packing>
2014-09-20 18:23:19 +04:00
<property name="left_attach">0</property>
2013-09-28 20:21:35 +04:00
<property name="top_attach">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 18:18:47 +04:00
</packing>
2011-06-23 19:42:03 +04:00
</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 18:18:47 +04:00
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkLabel" id="redir-address">
2011-06-23 19:42:03 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-09-28 20:21:35 +04:00
<property name="label" translatable="yes">foo:12</property>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
<packing>
2013-09-28 20:21:35 +04:00
<property name="left_attach">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 18:18:47 +04:00
<property name="top_attach">1</property>
</packing>
</child>
<child>
2013-09-28 20:21:35 +04:00
<object class="GtkLabel" id="redir-type">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-09-28 20:21:35 +04:00
<property name="label">redir type</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 18:18:47 +04:00
</object>
<packing>
<property name="left_attach">1</property>
2014-09-20 18:23:19 +04:00
<property name="top_attach">0</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 18:18:47 +04:00
</packing>
2011-06-23 19:42:03 +04:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2011-06-23 19:42:03 +04:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2011-06-23 19:42:03 +04:00
</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 18:18:47 +04:00
<child type="label">
<object class="GtkLabel" id="redir-title">
2011-06-23 19:42:03 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="label" translatable="yes"><b>Redirected device</b></property>
<property name="use_markup">True</property>
2012-02-02 02:26:46 +04:00
</object>
2011-09-02 05:23:27 +04:00
</child>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="frame19-atkobject">
<property name="AtkObject::accessible-name">redir-tab</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 18:18:47 +04:00
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">18</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 18:18:47 +04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label515">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">rd</property>
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">18</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 18:18:47 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
2017-04-12 13:47:41 +03:00
<object class="GtkBox" id="vbox17">
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 18:18:47 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</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 18:18:47 +04:00
<property name="spacing">12</property>
2011-09-02 05:23:27 +04:00
<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 18:18:47 +04:00
<object class="GtkFrame" id="frame20">
2011-09-02 05:23:27 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2011-09-02 05:23:27 +04:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<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 18:18:47 +04:00
<object class="GtkAlignment" id="alignment47">
2011-09-02 05:23:27 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2011-09-02 05:23:27 +04:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<child>
2013-09-24 02:43:50 +04:00
<object class="GtkGrid" id="table200">
2011-09-02 05:23:27 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
<property name="border_width">3</property>
<property name="row_spacing">4</property>
2013-09-24 02:43:50 +04:00
<property name="column_spacing">8</property>
2011-09-02 05:23:27 +04:00
<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 18:18:47 +04:00
<object class="GtkLabel" id="tpm-dev-type">
2011-09-02 05:23:27 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03: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 18:18:47 +04:00
<property name="label">tpm-dev-type</property>
2012-02-02 02:26:46 +04:00
</object>
2011-09-02 05:23:27 +04:00
<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 18:18:47 +04:00
<property name="left_attach">1</property>
2013-09-24 02:43:50 +04:00
<property name="top_attach">0</property>
2011-09-02 05:23:27 +04:00
</packing>
</child>
<child>
2013-09-24 02:43:50 +04:00
<object class="GtkLabel" id="tpm-device-path">
2011-09-02 05:23:27 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-09-24 02:43:50 +04:00
<property name="label">tpm-device-path</property>
2012-02-02 02:26:46 +04:00
</object>
2011-09-02 05:23:27 +04:00
<packing>
2013-09-24 02:43:50 +04:00
<property name="left_attach">1</property>
<property name="top_attach">1</property>
2011-09-02 05:23:27 +04:00
</packing>
</child>
<child>
2013-09-24 02:43:50 +04:00
<object class="GtkLabel" id="label183">
2011-09-02 05:23:27 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2014-12-30 13:20:10 +03:00
<property name="label" translatable="yes">Type:</property>
2012-02-02 02:26:46 +04:00
</object>
2011-09-02 05:23:27 +04:00
<packing>
2013-09-24 02:43:50 +04:00
<property name="left_attach">0</property>
<property name="top_attach">0</property>
2011-09-02 05:23:27 +04:00
</packing>
</child>
<child>
2013-09-24 02:43:50 +04:00
<object class="GtkLabel" id="tpm-device-path-label">
2011-09-02 05:23:27 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-09-24 02:43:50 +04:00
<property name="label" translatable="yes">Path:</property>
2012-02-02 02:26:46 +04:00
</object>
2011-09-02 05:23:27 +04:00
<packing>
2013-09-24 02:43:50 +04:00
<property name="left_attach">0</property>
2011-09-02 05:23:27 +04:00
<property name="top_attach">1</property>
</packing>
</child>
2018-06-09 00:42:43 +03:00
<child>
<object class="GtkLabel" id="tpm-version-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="label" translatable="yes">Version:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="tpm-version">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label">tpm-version</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">2</property>
</packing>
</child>
2012-02-02 02:26:46 +04:00
</object>
2011-09-02 05:23:27 +04:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2011-09-02 05:23:27 +04:00
</child>
2012-02-02 02:26:46 +04:00
<child type="label">
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 18:18:47 +04:00
<object class="GtkLabel" id="label180">
2011-09-02 05:23:27 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">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 18:18:47 +04:00
<property name="label" translatable="yes"><b>TPM Device</b></property>
2011-09-02 05:23:27 +04:00
<property name="use_markup">True</property>
2012-02-02 02:26:46 +04:00
</object>
2011-09-02 05:23:27 +04:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2011-09-02 05:23:27 +04:00
<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 18:18:47 +04:00
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
2013-06-27 04:05:32 +04:00
</packing>
</child>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="vbox17-atkobject">
<property name="AtkObject::accessible-name">tpm-tab</property>
</object>
</child>
2012-02-02 02:26:46 +04:00
</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 18:18:47 +04:00
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">19</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 18:18:47 +04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label182">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">tpm</property>
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">19</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 18:18:47 +04:00
<property name="tab_fill">False</property>
</packing>
2010-03-24 07:22:17 +03:00
</child>
2013-09-23 17:39:56 +04:00
<child>
<object class="GtkFrame" id="frame21">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<child>
<object class="GtkAlignment" id="alignment28">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="left_padding">12</property>
<child>
<object class="GtkGrid" id="table16">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="border_width">3</property>
<property name="row_spacing">4</property>
<property name="column_spacing">8</property>
<child>
<object class="GtkLabel" id="rng-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-09-23 17:39:56 +04:00
<property name="label">rng-type</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label90">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-09-23 17:39:56 +04:00
<property name="label" translatable="yes">Type:</property>
<property name="use_underline">True</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="rng-device">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-09-23 17:39:56 +04:00
<property name="label">rng-device</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="rng-label1">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2017-03-09 01:48:26 +03:00
<property name="label" translatable="yes">Host Device:</property>
2013-09-23 17:39:56 +04:00
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
2013-10-25 19:13:29 +04:00
<object class="GtkLabel" id="rng-label4">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-10-25 19:13:29 +04:00
<property name="label" translatable="yes">Backend type:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="rng-backend-type">
2013-09-23 17:39:56 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-10-25 19:13:29 +04:00
<property name="label">rng-backend-type</property>
2013-09-23 17:39:56 +04:00
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
2013-10-25 19:13:29 +04:00
<object class="GtkLabel" id="rng-label7">
2013-09-23 17:39:56 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-10-25 19:13:29 +04:00
<property name="label" translatable="yes">Mode:</property>
2013-09-23 17:39:56 +04:00
</object>
<packing>
<property name="left_attach">0</property>
2013-10-25 19:13:29 +04:00
<property name="top_attach">3</property>
2013-09-23 17:39:56 +04:00
</packing>
</child>
<child>
2013-10-25 19:13:29 +04:00
<object class="GtkLabel" id="rng-mode">
2013-09-23 17:39:56 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-10-25 19:13:29 +04:00
<property name="label">rng-mode</property>
2013-09-23 17:39:56 +04:00
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">3</property>
</packing>
</child>
<child>
2013-10-25 19:13:29 +04:00
<object class="GtkLabel" id="rng-label2">
2013-09-23 17:39:56 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-10-25 19:13:29 +04:00
<property name="label" translatable="yes">Host:</property>
2013-09-23 17:39:56 +04:00
</object>
<packing>
<property name="left_attach">0</property>
2013-10-25 19:13:29 +04:00
<property name="top_attach">4</property>
2013-09-23 17:39:56 +04:00
</packing>
</child>
<child>
2013-10-25 19:13:29 +04:00
<object class="GtkLabel" id="rng-connect-host">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-10-25 19:13:29 +04:00
<property name="label">rng-connect-host</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">4</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="rng-label3">
2013-09-23 17:39:56 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-10-25 19:13:29 +04:00
<property name="label" translatable="yes">Service:</property>
2013-09-23 17:39:56 +04:00
</object>
<packing>
<property name="left_attach">0</property>
2013-10-25 19:13:29 +04:00
<property name="top_attach">5</property>
2013-09-23 17:39:56 +04:00
</packing>
</child>
<child>
2013-10-25 19:13:29 +04:00
<object class="GtkLabel" id="rng-connect-service">
2013-09-23 17:39:56 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-10-25 19:13:29 +04:00
<property name="label">rng-connect-service</property>
2013-09-23 17:39:56 +04:00
</object>
<packing>
<property name="left_attach">1</property>
2013-10-25 19:13:29 +04:00
<property name="top_attach">5</property>
2013-09-23 17:39:56 +04:00
</packing>
</child>
<child>
2013-10-25 19:13:29 +04:00
<object class="GtkLabel" id="rng-label8">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-10-25 19:13:29 +04:00
<property name="label" translatable="yes">Bind Host:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">6</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="rng-bind-host">
2013-09-23 17:39:56 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-10-25 19:13:29 +04:00
<property name="label">rng-bind-host</property>
2013-09-23 17:39:56 +04:00
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">6</property>
</packing>
</child>
<child>
2013-10-25 19:13:29 +04:00
<object class="GtkLabel" id="rng-label9">
2013-09-23 17:39:56 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-10-25 19:13:29 +04:00
<property name="label" translatable="yes">Bind Service:</property>
2013-09-23 17:39:56 +04:00
</object>
<packing>
<property name="left_attach">0</property>
2013-10-25 19:13:29 +04:00
<property name="top_attach">7</property>
2013-09-23 17:39:56 +04:00
</packing>
</child>
<child>
2013-10-25 19:13:29 +04:00
<object class="GtkLabel" id="rng-bind-service">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-10-25 19:13:29 +04:00
<property name="label">rng-bind-service</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">7</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="rng-label6">
2013-09-23 17:39:56 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-10-25 19:13:29 +04:00
<property name="label" translatable="yes">Rate (period):</property>
2013-09-23 17:39:56 +04:00
</object>
<packing>
<property name="left_attach">0</property>
2013-10-25 19:13:29 +04:00
<property name="top_attach">8</property>
2013-09-23 17:39:56 +04:00
</packing>
</child>
<child>
2013-10-25 19:13:29 +04:00
<object class="GtkLabel" id="rng-rate-period">
2013-09-23 17:39:56 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-10-25 19:13:29 +04:00
<property name="label">rng-rate-period</property>
2013-09-23 17:39:56 +04:00
</object>
<packing>
<property name="left_attach">1</property>
2013-10-25 19:13:29 +04:00
<property name="top_attach">8</property>
2013-09-23 17:39:56 +04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="rng-label5">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:34 +03:00
<property name="halign">end</property>
2013-09-23 17:39:56 +04:00
<property name="label" translatable="yes">Rate (bytes):</property>
</object>
<packing>
<property name="left_attach">0</property>
2013-10-25 19:13:29 +04:00
<property name="top_attach">9</property>
2013-09-23 17:39:56 +04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="rng-rate-bytes">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-09-23 17:39:56 +04:00
<property name="label">rng-rate-bytes</property>
</object>
<packing>
<property name="left_attach">1</property>
2013-10-25 19:13:29 +04:00
<property name="top_attach">9</property>
2013-09-23 17:39:56 +04:00
</packing>
</child>
</object>
</child>
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label89">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>Random Number Generator</b></property>
<property name="use_markup">True</property>
</object>
</child>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="frame21-atkobject">
<property name="AtkObject::accessible-name">rng-tab</property>
</object>
</child>
2013-09-23 17:39:56 +04:00
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">20</property>
2013-09-23 17:39:56 +04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label81">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">rng</property>
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">20</property>
2013-09-23 17:39:56 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
2014-01-10 13:37:55 +04:00
<child>
<object class="GtkFrame" id="frame17">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<child>
2014-01-12 00:08:00 +04:00
<object class="GtkAlignment" id="alignment10">
2014-01-10 13:37:55 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="left_padding">12</property>
<child>
2014-01-12 00:08:00 +04:00
<object class="GtkGrid" id="table_panic">
2014-01-10 13:37:55 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2014-01-12 00:08:00 +04:00
<property name="row_spacing">4</property>
<property name="column_spacing">8</property>
2014-01-10 13:37:55 +04:00
<child>
2017-09-04 19:40:34 +03:00
<object class="GtkLabel" id="panic-model-label">
2014-01-10 13:37:55 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2017-05-31 16:08:38 +03:00
<property name="margin_top">3</property>
<property name="margin_bottom">3</property>
2017-09-04 19:40:34 +03:00
<property name="label" translatable="yes">Model:</property>
2014-01-12 00:08:00 +04:00
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
2017-09-04 19:40:34 +03:00
<object class="GtkLabel" id="panic-model">
2014-01-12 00:08:00 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2017-09-04 19:40:34 +03:00
<property name="label" translatable="yes">panic-model</property>
2014-01-10 13:37:55 +04:00
</object>
2014-01-12 00:08:00 +04:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
</child>
2014-01-10 13:37:55 +04:00
</object>
</child>
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label94">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes"><b>Panic Notifier</b></property>
<property name="use_markup">True</property>
</object>
</child>
2018-01-20 01:34:32 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="frame17-atkobject">
<property name="AtkObject::accessible-name">panic-tab</property>
</object>
</child>
2014-01-10 13:37:55 +04:00
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">21</property>
2014-01-10 13:37:55 +04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label93">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">panic</property>
</object>
<packing>
2014-01-26 23:07:35 +04:00
<property name="position">21</property>
2014-01-10 13:37:55 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
2012-02-02 02:26:46 +04:00
</object>
2009-09-23 18:45:44 +04:00
<packing>
2012-02-02 02:26:46 +04:00
<property name="expand">True</property>
<property name="fill">True</property>
2009-09-23 18:45:44 +04:00
<property name="position">0</property>
</packing>
2009-07-09 22:35:36 +04:00
</child>
<child>
2017-05-31 16:08:32 +03:00
<object class="GtkButtonBox" id="hbuttonbox3">
2009-07-09 22:35:36 +04:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2009-07-09 22:35:36 +04:00
<property name="spacing">12</property>
2009-09-23 18:45:44 +04:00
<property name="layout_style">end</property>
2009-07-09 22:35:36 +04:00
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkButton" id="config-remove">
2009-11-05 23:22:00 +03:00
<property name="label">gtk-remove</property>
2009-07-09 22:35:36 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="can_default">True</property>
2009-09-23 18:45:44 +04:00
<property name="receives_default">False</property>
2009-07-09 22:35:36 +04:00
<property name="use_stock">True</property>
2012-02-02 02:26:46 +04:00
<signal name="clicked" handler="on_config_remove_clicked" swapped="no"/>
2015-09-09 16:49:45 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="config-remove-atkobject">
2015-09-24 00:01:41 +03:00
<property name="AtkObject::accessible-name">config-remove</property>
2015-09-09 16:49:45 +03:00
</object>
</child>
2012-02-02 02:26:46 +04:00
</object>
2009-09-23 18:45:44 +04:00
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">0</property>
</packing>
2009-07-09 22:35:36 +04:00
</child>
2011-07-19 22:51:16 +04:00
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkButton" id="config-cancel">
2011-07-19 22:51:16 +04:00
<property name="label">gtk-cancel</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<property name="use_stock">True</property>
2012-02-02 02:26:46 +04:00
<signal name="clicked" handler="on_config_cancel_clicked" swapped="no"/>
2015-09-09 16:49:45 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="config-cancel-atkobject">
2015-09-24 00:01:41 +03:00
<property name="AtkObject::accessible-name">config-cancel</property>
2015-09-09 16:49:45 +03:00
</object>
</child>
2012-02-02 02:26:46 +04:00
</object>
2011-07-19 22:51:16 +04:00
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">1</property>
</packing>
</child>
2009-07-09 22:35:36 +04:00
<child>
2012-02-02 02:26:46 +04:00
<object class="GtkButton" id="config-apply">
2009-11-05 23:22:00 +03:00
<property name="label">gtk-apply</property>
2009-07-09 22:35:36 +04:00
<property name="visible">True</property>
2009-11-05 23:22:00 +03:00
<property name="sensitive">False</property>
2009-07-09 22:35:36 +04:00
<property name="can_focus">True</property>
<property name="can_default">True</property>
2009-09-23 18:45:44 +04:00
<property name="receives_default">False</property>
2009-07-09 22:35:36 +04:00
<property name="use_stock">True</property>
2012-02-02 02:26:46 +04:00
<signal name="clicked" handler="on_config_apply_clicked" swapped="no"/>
2015-09-09 16:49:45 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="config-apply-atkobject">
2015-09-24 00:01:41 +03:00
<property name="AtkObject::accessible-name">config-apply</property>
2015-09-09 16:49:45 +03:00
</object>
</child>
2012-02-02 02:26:46 +04:00
</object>
2009-07-09 22:35:36 +04:00
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
2011-07-19 22:51:16 +04:00
<property name="position">2</property>
2008-10-31 17:18:55 +03:00
</packing>
</child>
2012-02-02 02:26:46 +04:00
</object>
2009-07-09 22:35:36 +04:00
<packing>
<property name="expand">False</property>
2012-02-02 02:26:46 +04:00
<property name="fill">True</property>
2009-07-09 22:35:36 +04:00
<property name="position">1</property>
</packing>
2008-10-31 17:18:55 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2009-07-09 22:35:36 +04:00
<packing>
2012-02-02 02:26:46 +04:00
<property name="expand">True</property>
<property name="fill">True</property>
2009-07-09 22:35:36 +04:00
<property name="position">1</property>
</packing>
2008-10-31 17:18:55 +03:00
</child>
2012-02-02 02:26:46 +04:00
</object>
2013-09-02 01:40:38 +04:00
</child>
<child type="tab">
<object class="GtkLabel" id="label77">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">Details</property>
</object>
<packing>
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkNotebook" id="console-pages">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="show_border">False</property>
<signal name="switch-page" handler="on_console_pages_switch_page" after="yes" swapped="no"/>
<child>
<object class="GtkLabel" id="console-unavailable">
<property name="visible">True</property>
<property name="can_focus">False</property>
2016-05-18 23:32:07 +03:00
<property name="halign">center</property>
<property name="valign">center</property>
2013-09-02 01:40:38 +04:00
<property name="label" translatable="yes"><b>The console is currently unavailable</b></property>
<property name="use_markup">True</property>
<property name="justify">center</property>
<property name="wrap">True</property>
2016-05-16 22:19:52 +03:00
<property name="selectable">True</property>
2016-05-18 23:32:07 +03:00
<property name="width_chars">60</property>
<property name="max_width_chars">60</property>
2013-09-02 01:40:38 +04:00
</object>
<packing>
<property name="tab_expand">True</property>
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label434">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">Unavailable</property>
</object>
<packing>
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkTable" id="console-auth">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="border_width">3</property>
<property name="n_rows">3</property>
<property name="n_columns">3</property>
<property name="column_spacing">3</property>
<property name="row_spacing">3</property>
<child>
<object class="GtkLabel" id="label-auth-password">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-09-02 01:40:38 +04:00
<property name="label" translatable="yes">_Password:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">console-auth-password</property>
</object>
<packing>
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkEntry" id="console-auth-password">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="visibility">False</property>
<signal name="activate" handler="on_console_auth_password_activate" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkCheckButton" id="console-auth-remember">
<property name="label" translatable="yes">_Save this password in your keyring</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
2017-02-08 18:55:34 +03:00
<property name="tooltip_text" translatable="yes">Check to save password, uncheck to forget password.</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-09-02 01:40:38 +04:00
<property name="use_underline">True</property>
<property name="draw_indicator">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="top_attach">2</property>
<property name="bottom_attach">3</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkLabel" id="label-auth-username">
<property name="visible">True</property>
<property name="can_focus">False</property>
2017-05-31 16:08:33 +03:00
<property name="halign">start</property>
2013-09-02 01:40:38 +04:00
<property name="label" translatable="yes">_Username:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">console-auth-username</property>
</object>
<packing>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkEntry" id="console-auth-username">
<property name="visible">True</property>
<property name="can_focus">True</property>
<signal name="activate" handler="on_console_auth_password_activate" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkButton" id="console-auth-login">
<property name="label" translatable="yes">_Login</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
2013-09-22 20:18:49 +04:00
<property name="image">image70</property>
2013-09-02 01:40:38 +04:00
<property name="use_underline">True</property>
<signal name="clicked" handler="on_console_auth_login_clicked" swapped="no"/>
</object>
<packing>
<property name="left_attach">2</property>
<property name="right_attach">3</property>
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkAlignment" id="alignment17">
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<placeholder/>
</child>
</object>
<packing>
<property name="top_attach">2</property>
<property name="bottom_attach">3</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options">GTK_FILL</property>
</packing>
</child>
<child>
<object class="GtkAlignment" id="alignment18">
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<placeholder/>
</child>
</object>
<packing>
<property name="left_attach">2</property>
<property name="right_attach">3</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options">GTK_FILL</property>
</packing>
</child>
<child>
<object class="GtkAlignment" id="alignment19">
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<placeholder/>
</child>
</object>
<packing>
<property name="left_attach">2</property>
<property name="right_attach">3</property>
<property name="top_attach">2</property>
<property name="bottom_attach">3</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options">GTK_FILL</property>
</packing>
</child>
</object>
<packing>
<property name="position">1</property>
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label438">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">Auth</property>
</object>
<packing>
<property name="position">1</property>
<property name="tab_fill">False</property>
</packing>
</child>
2015-09-18 18:55:15 +03:00
<child>
<object class="GtkNotebook" id="serial-pages">
<property name="visible">True</property>
<property name="can_focus">True</property>
2018-01-21 20:40:15 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="serial-pages-atkobject">
<property name="AtkObject::accessible-name">serial-pages</property>
</object>
</child>
2015-09-18 18:55:15 +03:00
</object>
<packing>
<property name="position">2</property>
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label82">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">Serial</property>
</object>
<packing>
<property name="position">2</property>
<property name="tab_fill">False</property>
</packing>
</child>
2013-09-02 01:40:38 +04:00
<child>
2016-05-17 19:14:32 +03:00
<object class="GtkOverlay" id="console-overlay">
2013-09-02 01:40:38 +04:00
<property name="visible">True</property>
2016-05-17 19:14:32 +03:00
<property name="can_focus">False</property>
2013-09-02 01:40:38 +04:00
<child>
2016-05-17 19:14:32 +03:00
<object class="GtkScrolledWindow" id="console-gfx-scroll">
2013-09-02 01:40:38 +04:00
<property name="visible">True</property>
2016-05-17 19:14:32 +03:00
<property name="can_focus">True</property>
2013-09-02 01:40:38 +04:00
<child>
2016-05-17 19:14:32 +03:00
<object class="GtkViewport" id="console-gfx-viewport">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="resize_mode">queue</property>
<property name="shadow_type">none</property>
<child>
<placeholder/>
</child>
2018-01-21 18:56:35 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="console-gfx-viewport-atkobject">
<property name="AtkObject::accessible-name">console-gfx-viewport</property>
</object>
</child>
2016-05-17 19:14:32 +03:00
</object>
2013-09-02 01:40:38 +04:00
</child>
</object>
2016-05-17 19:14:32 +03:00
<packing>
<property name="index">-1</property>
</packing>
2013-09-02 01:40:38 +04:00
</child>
</object>
<packing>
2015-09-18 18:55:15 +03:00
<property name="position">3</property>
2013-09-02 01:40:38 +04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label439">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">Graphics</property>
</object>
<packing>
2015-09-18 18:55:15 +03:00
<property name="position">3</property>
2013-09-02 01:40:38 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
</object>
2008-10-31 17:18:55 +03:00
<packing>
2009-02-09 22:55:18 +03:00
<property name="position">1</property>
2008-10-31 17:18:55 +03:00
</packing>
</child>
2012-02-02 02:26:46 +04:00
<child type="tab">
2013-09-02 01:40:38 +04:00
<object class="GtkLabel" id="label420">
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
2013-09-02 01:40:38 +04:00
<property name="label">Console</property>
2012-02-02 02:26:46 +04:00
</object>
2008-10-31 17:18:55 +03:00
<packing>
2009-02-09 22:55:18 +03:00
<property name="position">1</property>
2008-10-31 17:18:55 +03:00
<property name="tab_fill">False</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 18:18:47 +04:00
<child>
<object class="GtkBox" id="snapshot-placeholder">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<child>
<placeholder/>
</child>
</object>
<packing>
<property name="position">2</property>
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label88">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">Snapshots</property>
</object>
<packing>
<property name="position">2</property>
<property name="tab_fill">False</property>
</packing>
</child>
2012-02-02 02:26:46 +04:00
</object>
2008-10-31 17:18:55 +03:00
<packing>
2012-02-02 02:26:46 +04:00
<property name="expand">True</property>
<property name="fill">True</property>
2008-10-31 17:18:55 +03:00
<property name="position">2</property>
</packing>
</child>
2012-02-02 02:26:46 +04:00
</object>
2008-10-31 17:18:55 +03:00
</child>
2017-11-25 23:15:08 +03:00
<child type="titlebar">
<placeholder/>
</child>
2012-02-02 02:26:46 +04:00
</object>
</interface>