shaba/virt-manager
1
0
Fork 0
mirror of https://github.com/virt-manager/virt-manager.git synced 2024-12-22 13:34:07 +03:00
Code Issues Projects Releases Wiki Activity
d073ee9a48
virt-manager/ui/details.ui

4740 lines
286 KiB
Plaintext
Raw Normal View History

Save UI files using F14 glade (without swapped="no") change. libglade complains about the swapped="no" property, so sed that part out.
2010-11-24 23:57:40 +03:00
<?xml version="1.0" encoding="UTF-8"?>
uitests: add some mock inspection.py testing Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-08-26 15:46:25 +03:00
<!-- Generated with glade 3.36.0 -->
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<interface>
ui: Bump gtk3 dep to our app wide 3.22
2019-06-17 07:25:31 +03:00
<requires lib="gtk+" version="3.22"/>
details: add UI interface for LXC user namespace We could config user namespace for LXC container in details->overview page. Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-02-21 14:13:11 +04:00
<object class="GtkAdjustment" id="adjustment16">
details: Raise upper limits for lxc ID namespaces (bz 1244490)
2015-08-10 20:14:37 +03:00
<property name="upper">10000000</property>
details: add UI interface for LXC user namespace We could config user namespace for LXC container in details->overview page. Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
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">
details: Raise upper limits for lxc ID namespaces (bz 1244490)
2015-08-10 20:14:37 +03:00
<property name="upper">10000000</property>
details: add UI interface for LXC user namespace We could config user namespace for LXC container in details->overview page. Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
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>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
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="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>
ui: Set non-stock button images in glade, not explicitly in code
2013-09-22 20:18:49 +04:00
<object class="GtkImage" id="image80">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="stock">gtk-add</property>
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkBox" id="details-top-box">
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="border_width">12</property>
<property name="spacing">12</property>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkBox" id="vbox53">
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
Format UI files with Glade 3.20 Glade performs XML formatting on save. The changes in this commit are generated by Glade 3.20
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="spacing">6</property>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkScrolledWindow" id="scrolledwindow5">
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">True</property>
<property name="hscrollbar_policy">never</property>
<property name="shadow_type">in</property>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkTreeView" id="hw-list">
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">True</property>
<property name="headers_visible">False</property>
<property name="enable_search">False</property>
<signal name="button-press-event" handler="on_hw_list_button_press_event" swapped="no"/>
<child internal-child="selection">
<object class="GtkTreeSelection">
<property name="mode">browse</property>
<signal name="changed" handler="on_hw_list_changed" swapped="no"/>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="hw-list-atkobject">
<property name="AtkObject::accessible-name">hw-list</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="scrolledwindow5-atkobject">
<property name="AtkObject::accessible-name">hw-list-scroll</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="expand">True</property>
<property name="fill">True</property>
Fix up vbox orientation with latest glade version. Resave all files with the latest version as well, which causes lots of churn.
2009-09-23 18:45:44 +04:00
<property name="position">0</property>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
</packing>
</child>
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkButton" id="add-hardware-button">
<property name="label" translatable="yes">A_dd Hardware</property>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">True</property>
<property name="receives_default">False</property>
<property name="image">image80</property>
<property name="use_underline">True</property>
<signal name="clicked" handler="on_add_hardware_button_clicked" swapped="no"/>
<child internal-child="accessible">
<object class="AtkObject" id="add-hardware-button-atkobject">
<property name="AtkObject::accessible-name">add-hardware</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<packing>
<property name="expand">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="fill">False</property>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<property name="position">1</property>
</packing>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03: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="vbox1">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<property name="spacing">6</property>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkAlignment" id="hw-panel-align">
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">False</property>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkNotebook" id="hw-panel">
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">True</property>
<property name="tab_pos">left</property>
<property name="show_border">False</property>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkBox" id="vbox6">
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
Format UI files with Glade 3.20 Glade performs XML formatting on save. The changes in this commit are generated by Glade 3.20
2017-05-31 16:08:31 +03:00
<property name="orientation">vertical</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="spacing">12</property>
Some 'Details' UI cleanup. The main change is removing the duplication of the 'Apply' and 'Remove' buttons in the UI. This has no functional change, but from a dev perspective this saves annoying duplication when new device support is added. Also fix up some minor layout and spacing issues.
2009-07-09 22:35:36 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkFrame" id="frame2">
Some 'Details' UI cleanup. The main change is removing the duplication of the 'Apply' and 'Remove' buttons in the UI. This has no functional change, but from a dev perspective this saves annoying duplication when new device support is added. Also fix up some minor layout and spacing issues.
2009-07-09 22:35:36 +04:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
Some 'Details' UI cleanup. The main change is removing the duplication of the 'Apply' and 'Remove' buttons in the UI. This has no functional change, but from a dev perspective this saves annoying duplication when new device support is added. Also fix up some minor layout and spacing issues.
2009-07-09 22:35:36 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkAlignment" id="alignment9">
Some 'Details' UI cleanup. The main change is removing the duplication of the 'Apply' and 'Remove' buttons in the UI. This has no functional change, but from a dev perspective this saves annoying duplication when new device support is added. Also fix up some minor layout and spacing issues.
2009-07-09 22:35:36 +04:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<child>
<object class="GtkGrid" id="table5">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="border_width">3</property>
<property name="row_spacing">6</property>
<property name="column_spacing">6</property>
<child>
<object class="GtkLabel" id="label44">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<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>
<property name="halign">start</property>
<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>
<property name="halign">start</property>
<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>
<property name="halign">start</property>
<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>
<property name="halign">start</property>
<property name="label" translatable="yes">T_itle:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">overview-title</property>
</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>
<child>
<object class="GtkLabel" id="overview-status-text">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label" translatable="yes">Shut down</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkImage" id="overview-status-icon">
<property name="width_request">22</property>
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="stock">gtk-missing-image</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
</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>
<property name="halign">start</property>
<property name="valign">start</property>
<property name="label" translatable="yes">D_escription:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">overview-description</property>
</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>
<child>
<object class="GtkTextView" id="overview-description">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="hexpand">True</property>
<property name="wrap_mode">word</property>
<property name="left_margin">2</property>
<property name="right_margin">2</property>
</object>
</child>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">4</property>
</packing>
</child>
</object>
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
Some 'Details' UI cleanup. The main change is removing the duplication of the 'Apply' and 'Remove' buttons in the UI. This has no functional change, but from a dev perspective this saves annoying duplication when new device support is added. Also fix up some minor layout and spacing issues.
2009-07-09 22:35:36 +04:00
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03: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">&lt;b&gt;Basic Details&lt;/b&gt;</property>
<property name="use_markup">True</property>
uitests: Several more 'New VM' tests, and cli --show tests
2015-09-09 16:49:45 +03:00
</object>
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
Some 'Details' UI cleanup. The main change is removing the duplication of the 'Apply' and 'Remove' buttons in the UI. This has no functional change, but from a dev perspective this saves annoying duplication when new device support is added. Also fix up some minor layout and spacing issues.
2009-07-09 22:35:36 +04:00
<packing>
<property name="expand">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="fill">True</property>
<property name="position">0</property>
Some 'Details' UI cleanup. The main change is removing the duplication of the 'Apply' and 'Remove' buttons in the UI. This has no functional change, but from a dev perspective this saves annoying duplication when new device support is added. Also fix up some minor layout and spacing issues.
2009-07-09 22:35:36 +04:00
</packing>
</child>
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkFrame" id="frame7">
Some 'Details' UI cleanup. The main change is removing the duplication of the 'Apply' and 'Remove' buttons in the UI. This has no functional change, but from a dev perspective this saves annoying duplication when new device support is added. Also fix up some minor layout and spacing issues.
2009-07-09 22:35:36 +04:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkAlignment" id="alignment6">
Save glade files with glade-3
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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkGrid" id="table1">
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03: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>
<property name="halign">start</property>
<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>
<property name="halign">start</property>
<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>
<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="overview-arch">
<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">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="overview-emulator">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label">foooooooooooooo</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="label13">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label" translatable="yes">Emulator:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="machine-type-title">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<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>
<child>
<object class="GtkLabel" id="overview-chipset-title">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label" translatable="yes">Chipse_t:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">overview-chipset</property>
<property name="ellipsize">middle</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">4</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="overview-firmware-title">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label" translatable="yes">Firm_ware:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">overview-firmware</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">5</property>
</packing>
</child>
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkBox" id="box11">
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="spacing">3</property>
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkBox" id="box16">
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: Move inspection info to its own page
2014-01-26 23:07:35 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkComboBox" id="overview-firmware">
details: Move inspection info to its own page
2014-01-26 23:07:35 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<signal name="changed" handler="on_overview_firmware_changed" swapped="no"/>
details: Move inspection info to its own page
2014-01-26 23:07:35 +04:00
</object>
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
details: Move inspection info to its own page
2014-01-26 23:07:35 +04:00
</packing>
</child>
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkLabel" id="overview-firmware-label">
details: Move inspection info to its own page
2014-01-26 23:07:35 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="label">label</property>
details: Move inspection info to its own page
2014-01-26 23:07:35 +04:00
<property name="selectable">True</property>
</object>
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
details: Move inspection info to its own page
2014-01-26 23:07:35 +04:00
</packing>
Add basic operating system inspection data to the VMM details page. This adds hostname, product name, and list of applications.
2011-07-18 22:53:57 +04:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<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>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">5</property>
</packing>
</child>
<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"/>
uitests: details/domain/config coverage additions Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-08-27 23:37:15 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="machine-type-atkobject">
<property name="AtkObject::accessible-name">machine-combo</property>
</object>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</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>
<property name="selectable">True</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
Add basic operating system inspection data to the VMM details page. This adds hostname, product name, and list of applications.
2011-07-18 22:53:57 +04:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">3</property>
</packing>
Add basic operating system inspection data to the VMM details page. This adds hostname, product name, and list of applications.
2011-07-18 22:53:57 +04:00
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child>
<object class="GtkBox" id="overview-chipset-box">
details: Move inspection info to its own page
2014-01-26 23:07:35 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<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="label">label</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
details: Move inspection info to its own page
2014-01-26 23:07:35 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">4</property>
</packing>
details: Move inspection info to its own page
2014-01-26 23:07:35 +04:00
</child>
</object>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
</child>
<child type="label">
<object class="GtkLabel" id="frame">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;Hypervisor Details&lt;/b&gt;</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>
<child internal-child="accessible">
<object class="AtkObject" id="vbox6-atkobject">
<property name="AtkObject::accessible-name">overview-tab</property>
</object>
</child>
</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>
<object class="GtkBox" id="box14">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<property name="spacing">12</property>
<child>
<object class="GtkFrame" id="details-inspection-os">
<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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkAlignment" id="alignment43">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03: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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkGrid" id="table17">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="border_width">3</property>
<property name="row_spacing">6</property>
<property name="column_spacing">6</property>
details: Allow setting CPU topology and model Provide a button 'Copy from host CPU', which effectively sets up the equiv of qemu -cpu host
2010-12-17 00:05:55 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkAlignment" id="details-os-align">
details: Allow setting CPU topology and model Provide a button 'Copy from host CPU', which effectively sets up the equiv of qemu -cpu host
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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="hexpand">True</property>
details: Allow setting CPU topology and model Provide a button 'Copy from host CPU', which effectively sets up the equiv of qemu -cpu host
2010-12-17 00:05:55 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<placeholder/>
details: Allow setting CPU topology and model Provide a button 'Copy from host CPU', which effectively sets up the equiv of qemu -cpu host
2010-12-17 00:05:55 +03:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
details: Allow setting CPU topology and model Provide a button 'Copy from host CPU', which effectively sets up the equiv of qemu -cpu host
2010-12-17 00:05:55 +03:00
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
</child>
</object>
</child>
<child type="label">
<object class="GtkLabel" id="details-os-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;Operating Sys_tem&lt;/b&gt;</property>
<property name="use_markup">True</property>
<property name="use_underline">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>
<child>
<object class="GtkAlignment" id="alignment44">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">21</property>
<child>
<object class="GtkScrolledWindow" id="scrolledwindow6">
<property name="height_request">150</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="shadow_type">etched-in</property>
<child>
<object class="GtkTreeView" id="inspection-apps">
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">True</property>
<child internal-child="selection">
<object class="GtkTreeSelection"/>
</child>
uitests: add some mock inspection.py testing Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-08-26 15:46:25 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="inspection-apps-atkobject">
<property name="AtkObject::accessible-name">inspection-apps</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>
</child>
</object>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
</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">&lt;b&gt;Applications&lt;/b&gt;</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>
<child>
<object class="GtkBox">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">12</property>
<child>
<object class="GtkGrid" id="details-inspection-error-box">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="valign">center</property>
<property name="orientation">vertical</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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkImage" id="image1">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: Make CPU config a frame, not an expander It's very commonly tweaked, so move it front and center.
2015-04-07 18:53:16 +03:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="halign">start</property>
<property name="valign">start</property>
<property name="stock">gtk-dialog-warning</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkLabel" id="details-overview-error">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<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>
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkButton" id="details-inspection-refresh">
<property name="label" translatable="yes">Refresh</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<property name="halign">end</property>
<property name="valign">start</property>
<signal name="clicked" handler="on_details_inspection_refresh_clicked" swapped="no"/>
</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">2</property>
</packing>
</child>
<child internal-child="accessible">
<object class="AtkObject" id="box14-atkobject">
<property name="AtkObject::accessible-name">os-tab</property>
</object>
</child>
</object>
<packing>
<property name="position">1</property>
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label14">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">osinfo</property>
</object>
<packing>
<property name="position">1</property>
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkBox" id="box2">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<child>
<object class="GtkBox" id="vbox5">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<property name="spacing">12</property>
<child>
<object class="GtkFrame" id="frame24">
<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="alignment50">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="left_padding">12</property>
<child>
<object class="GtkBox" id="box7">
<property name="visible">True</property>
<property name="can_focus">False</property>
<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/>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 22:55:18 +03:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<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>
<property name="halign">end</property>
<property name="label">18%</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
Save glade files with glade-3
2008-10-31 17:18: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>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 22:55:18 +03:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child type="label">
<object class="GtkLabel" id="label45">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;CPU usage&lt;/b&gt;</property>
<property name="use_markup">True</property>
uitests: Add choosecd dialog tests
2018-01-20 01:34:32 +03:00
</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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="expand">False</property>
<property name="fill">False</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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child>
<object class="GtkFrame" id="frame3">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<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>
<child>
<object class="GtkBox" id="box6">
<property name="visible">True</property>
<property name="can_focus">False</property>
<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>
<property name="halign">end</property>
<property name="label">30 MiB of 128 MiB</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
</object>
</child>
</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">&lt;b&gt;Memory usage&lt;/b&gt;</property>
<property name="use_markup">True</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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="expand">False</property>
<property name="fill">False</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>
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkFrame" id="frame22">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkAlignment" id="alignment48">
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="left_padding">12</property>
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkBox" id="box5">
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="orientation">vertical</property>
<property name="spacing">3</property>
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkAlignment" id="overview-disk-usage-align">
<property name="height_request">75</property>
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
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
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<placeholder/>
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</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>
<property name="halign">end</property>
<property name="label" translatable="yes">0 KiBytes/s 0 KiBytes/s</property>
<property name="use_markup">True</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
</object>
</child>
</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">&lt;b&gt;Disk I/O&lt;/b&gt;</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>
<child>
<object class="GtkBox" id="box8">
<property name="visible">True</property>
<property name="can_focus">False</property>
<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/>
details: Show disk size if available
2010-03-04 02:43:48 +03:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<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>
<property name="halign">end</property>
<property name="label">0 KiBytes/s 0 KiBytes/s</property>
<property name="use_markup">True</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
details: Centralize most hardware page spacing
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>
</object>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03: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">&lt;b&gt;Network I/O&lt;/b&gt;</property>
<property name="use_markup">True</property>
uitests: Add choosecd dialog tests
2018-01-20 01:34:32 +03:00
</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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="expand">False</property>
<property name="fill">False</property>
<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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child internal-child="accessible">
<object class="AtkObject" id="box2-atkobject">
<property name="AtkObject::accessible-name">performance-tab</property>
</object>
</child>
</object>
<packing>
<property name="position">2</property>
<property name="tab_fill">False</property>
</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>
<property name="position">2</property>
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkBox" id="vbox14">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="valign">start</property>
<property name="orientation">vertical</property>
<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>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkAlignment" id="alignment11">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkBox" id="hbox5">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkGrid" id="table30">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="border_width">3</property>
<property name="row_spacing">6</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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkLabel" id="state-host-cpus">
details: Expose fine grained boot config Basically put an explicit device list in the boot UI, if the hypervisor supports it. For unsupported hv, use the same old disk/cd/floppy/net UI.
2014-02-10 01:21:26 +04:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="valign">center</property>
<property name="label">8</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="label334">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="valign">center</property>
<property name="label" translatable="yes">Logical host CPUs:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label333">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="valign">center</property>
i18n: fix few spellings "iSCSI", "KVM", "QEMU", "UNIX", "UUID", "VirtIO", "XML", "vCPU". Reviewed-by: Cole Robinson <crobinso@redhat.com> Signed-off-by: Pino Toscano <ptoscano@redhat.com>
2020-07-13 11:25:39 +03:00
<property name="label" translatable="yes">vCPU a_llocation:</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="use_underline">True</property>
<property name="mnemonic_widget">cpu-vcpus</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkSpinButton" id="cpu-vcpus">
<property name="visible">True</property>
<property name="can_focus">True</property>
virtManager: Remove maximum VCPUS API and VCPU hotplug This was proposed here: https://www.redhat.com/archives/virt-tools-list/2019-June/msg00117.html """ * UI maxmem and maxcpu notions, and related memballoon and cpu hotplug operations. These have been in the UI forever but I'm not sure people actually use them. cpu hotplug has always been a mess, and unless the user plans ahead by setting a high maxmem value ballooning is only good for reducing memory. These all sound like advanced usage to me that just confuses the typical usecase of adding more mem or vcpus to an offline VM. And the hotplug operations with virsh are simple to invoke. So I'd like to drop this from the UI """ The remaining UI field now sets both maximum and current VCPU allocation. Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-01-25 23:11:02 +03:00
<property name="halign">start</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="valign">center</property>
virtManager: Remove maximum VCPUS API and VCPU hotplug This was proposed here: https://www.redhat.com/archives/virt-tools-list/2019-June/msg00117.html """ * UI maxmem and maxcpu notions, and related memballoon and cpu hotplug operations. These have been in the UI forever but I'm not sure people actually use them. cpu hotplug has always been a mess, and unless the user plans ahead by setting a high maxmem value ballooning is only good for reducing memory. These all sound like advanced usage to me that just confuses the typical usecase of adding more mem or vcpus to an offline VM. And the hotplug operations with virsh are simple to invoke. So I'd like to drop this from the UI """ The remaining UI field now sets both maximum and current VCPU allocation. Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-01-25 23:11:02 +03:00
<property name="hexpand">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="invisible_char">●</property>
<property name="text" translatable="yes">2</property>
<property name="adjustment">adjustment7</property>
<property name="climb_rate">1</property>
<property name="numeric">True</property>
<property name="update_policy">if-valid</property>
<property name="value">2</property>
<signal name="changed" handler="on_cpu_vcpus_changed" swapped="no"/>
<child internal-child="accessible">
<object class="AtkObject" id="cpu-vcpus-atkobject">
<property name="AtkObject::accessible-name">Virtual CPU Select</property>
</object>
</child>
details: Expose fine grained boot config Basically put an explicit device list in the boot UI, if the hypervisor supports it. For unsupported hv, use the same old disk/cd/floppy/net UI.
2014-02-10 01:21:26 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
</packing>
details: Expose fine grained boot config Basically put an explicit device list in the boot UI, if the hypervisor supports it. For unsupported hv, use the same old disk/cd/floppy/net UI.
2014-02-10 01:21:26 +04:00
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child>
virtManager: Remove maximum VCPUS API and VCPU hotplug This was proposed here: https://www.redhat.com/archives/virt-tools-list/2019-June/msg00117.html """ * UI maxmem and maxcpu notions, and related memballoon and cpu hotplug operations. These have been in the UI forever but I'm not sure people actually use them. cpu hotplug has always been a mess, and unless the user plans ahead by setting a high maxmem value ballooning is only good for reducing memory. These all sound like advanced usage to me that just confuses the typical usecase of adding more mem or vcpus to an offline VM. And the hotplug operations with virsh are simple to invoke. So I'd like to drop this from the UI """ The remaining UI field now sets both maximum and current VCPU allocation. Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-01-25 23:11:02 +03:00
<object class="GtkBox" id="cpu-vcpus-warn-box">
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
virtManager: Remove maximum VCPUS API and VCPU hotplug This was proposed here: https://www.redhat.com/archives/virt-tools-list/2019-June/msg00117.html """ * UI maxmem and maxcpu notions, and related memballoon and cpu hotplug operations. These have been in the UI forever but I'm not sure people actually use them. cpu hotplug has always been a mess, and unless the user plans ahead by setting a high maxmem value ballooning is only good for reducing memory. These all sound like advanced usage to me that just confuses the typical usecase of adding more mem or vcpus to an offline VM. And the hotplug operations with virsh are simple to invoke. So I'd like to drop this from the UI """ The remaining UI field now sets both maximum and current VCPU allocation. Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-01-25 23:11:02 +03:00
<property name="spacing">6</property>
<child>
<object class="GtkImage" id="image9">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<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">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;small&gt;Overcommitting vCPUs can hurt performance&lt;/small&gt;</property>
<property name="use_markup">True</property>
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
<packing>
virtManager: Remove maximum VCPUS API and VCPU hotplug This was proposed here: https://www.redhat.com/archives/virt-tools-list/2019-June/msg00117.html """ * UI maxmem and maxcpu notions, and related memballoon and cpu hotplug operations. These have been in the UI forever but I'm not sure people actually use them. cpu hotplug has always been a mess, and unless the user plans ahead by setting a high maxmem value ballooning is only good for reducing memory. These all sound like advanced usage to me that just confuses the typical usecase of adding more mem or vcpus to an offline VM. And the hotplug operations with virsh are simple to invoke. So I'd like to drop this from the UI """ The remaining UI field now sets both maximum and current VCPU allocation. Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-01-25 23:11:02 +03:00
<property name="left_attach">0</property>
<property name="top_attach">2</property>
<property name="width">2</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</packing>
</child>
details: Expose fine grained boot config Basically put an explicit device list in the boot UI, if the hypervisor supports it. For unsupported hv, use the same old disk/cd/floppy/net UI.
2014-02-10 01:21:26 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
virtManager: Remove maximum VCPUS API and VCPU hotplug This was proposed here: https://www.redhat.com/archives/virt-tools-list/2019-June/msg00117.html """ * UI maxmem and maxcpu notions, and related memballoon and cpu hotplug operations. These have been in the UI forever but I'm not sure people actually use them. cpu hotplug has always been a mess, and unless the user plans ahead by setting a high maxmem value ballooning is only good for reducing memory. These all sound like advanced usage to me that just confuses the typical usecase of adding more mem or vcpus to an offline VM. And the hotplug operations with virsh are simple to invoke. So I'd like to drop this from the UI """ The remaining UI field now sets both maximum and current VCPU allocation. Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-01-25 23:11:02 +03:00
<property name="expand">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="fill">True</property>
virtManager: Remove maximum VCPUS API and VCPU hotplug This was proposed here: https://www.redhat.com/archives/virt-tools-list/2019-June/msg00117.html """ * UI maxmem and maxcpu notions, and related memballoon and cpu hotplug operations. These have been in the UI forever but I'm not sure people actually use them. cpu hotplug has always been a mess, and unless the user plans ahead by setting a high maxmem value ballooning is only good for reducing memory. These all sound like advanced usage to me that just confuses the typical usecase of adding more mem or vcpus to an offline VM. And the hotplug operations with virsh are simple to invoke. So I'd like to drop this from the UI """ The remaining UI field now sets both maximum and current VCPU allocation. Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-01-25 23:11:02 +03:00
<property name="position">0</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</packing>
details: Expose fine grained boot config Basically put an explicit device list in the boot UI, if the hypervisor supports it. For unsupported hv, use the same old disk/cd/floppy/net UI.
2014-02-10 01:21:26 +04:00
</child>
</object>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label100">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;CPUs&lt;/b&gt;</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="frame1">
<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="alignment5">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">12</property>
details: Expose fine grained boot config Basically put an explicit device list in the boot UI, if the hypervisor supports it. For unsupported hv, use the same old disk/cd/floppy/net UI.
2014-02-10 01:21:26 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkGrid" id="table15">
details: Expose fine grained boot config Basically put an explicit device list in the boot UI, if the hypervisor supports it. For unsupported hv, use the same old disk/cd/floppy/net UI.
2014-02-10 01:21:26 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="halign">start</property>
<property name="valign">start</property>
<property name="row_spacing">3</property>
<property name="column_spacing">12</property>
details: Expose fine grained boot config Basically put an explicit device list in the boot UI, if the hypervisor supports it. For unsupported hv, use the same old disk/cd/floppy/net UI.
2014-02-10 01:21:26 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkLabel" id="label52">
details: Expose fine grained boot config Basically put an explicit device list in the boot UI, if the hypervisor supports it. For unsupported hv, use the same old disk/cd/floppy/net UI.
2014-02-10 01:21:26 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="halign">start</property>
<property name="label" translatable="yes">M_odel:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">cpu-model-text</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkCheckButton" id="cpu-copy-host">
<property name="label" translatable="yes">Copy host CP_U configuration</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
<property name="halign">start</property>
<property name="use_underline">True</property>
<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>
details: Align cpu model combo left
2019-05-17 22:35:41 +03:00
<property name="halign">start</property>
<property name="hexpand">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="has_entry">True</property>
<signal name="changed" handler="on_cpu_model_changed" swapped="no"/>
<child internal-child="entry">
<object class="GtkEntry" id="cpu-model-text">
<property name="can_focus">True</property>
</object>
</child>
<child internal-child="accessible">
<object class="AtkObject" id="cpu-model-atkobject">
<property name="AtkObject::accessible-name">cpu-model</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child>
<object class="GtkCheckButton" id="cpu-secure">
<property name="label" translatable="yes">Enable available CPU security flaw mitigations</property>
details: Expose fine grained boot config Basically put an explicit device list in the boot UI, if the hypervisor supports it. For unsupported hv, use the same old disk/cd/floppy/net UI.
2014-02-10 01:21:26 +04:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">True</property>
<property name="receives_default">False</property>
<property name="draw_indicator">True</property>
<signal name="toggled" handler="on_cpu_secure_toggled" swapped="no"/>
details: Expose fine grained boot config Basically put an explicit device list in the boot UI, if the hypervisor supports it. For unsupported hv, use the same old disk/cd/floppy/net UI.
2014-02-10 01:21:26 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
<property name="width">2</property>
</packing>
details: Expose fine grained boot config Basically put an explicit device list in the boot UI, if the hypervisor supports it. For unsupported hv, use the same old disk/cd/floppy/net UI.
2014-02-10 01:21:26 +04:00
</child>
</object>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label49">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;Configu_ration&lt;/b&gt;</property>
<property name="use_markup">True</property>
<property name="use_underline">True</property>
</object>
</child>
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
<child>
<object class="GtkExpander" id="cpu-topology-expander">
<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>
details: Expose fine grained boot config Basically put an explicit device list in the boot UI, if the hypervisor supports it. For unsupported hv, use the same old disk/cd/floppy/net UI.
2014-02-10 01:21:26 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkBox" id="vbox15">
details: Expose fine grained boot config Basically put an explicit device list in the boot UI, if the hypervisor supports it. For unsupported hv, use the same old disk/cd/floppy/net UI.
2014-02-10 01:21:26 +04:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<property name="spacing">4</property>
<child>
<object class="GtkCheckButton" id="cpu-topology-enable">
<property name="label" translatable="yes">Manuall_y set CPU topology</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
<property name="halign">start</property>
<property name="use_underline">True</property>
<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>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: Remove the threads warning for CPUs that don't support it This is pretty obscure, and if it's problematic then libvirt or qemu should be throwing an error or otherwise reporting it Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-08-27 17:58:06 +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>
details: Remove the threads warning for CPUs that don't support it This is pretty obscure, and if it's problematic then libvirt or qemu should be throwing an error or otherwise reporting it Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-08-27 17:58:06 +03:00
<property name="row_spacing">4</property>
<property name="column_spacing">12</property>
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
<child>
details: Remove the threads warning for CPUs that don't support it This is pretty obscure, and if it's problematic then libvirt or qemu should be throwing an error or otherwise reporting it Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-08-27 17:58:06 +03:00
<object class="GtkLabel" id="label59">
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: Remove the threads warning for CPUs that don't support it This is pretty obscure, and if it's problematic then libvirt or qemu should be throwing an error or otherwise reporting it Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-08-27 17:58:06 +03:00
<property name="halign">start</property>
<property name="label" translatable="yes">Thread_s:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">cpu-threads</property>
</object>
<packing>
<property name="left_attach">0</property>
<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>
<property name="halign">start</property>
<property name="label" translatable="yes">Cor_es:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">cpu-cores</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: Remove the threads warning for CPUs that don't support it This is pretty obscure, and if it's problematic then libvirt or qemu should be throwing an error or otherwise reporting it Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-08-27 17:58:06 +03:00
<packing>
<property name="left_attach">0</property>
<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>
<property name="halign">start</property>
<property name="label" translatable="yes">Socke_ts:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">cpu-sockets</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</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="text" translatable="yes">1</property>
<property name="adjustment">adjustment3</property>
<property name="value">1</property>
<signal name="changed" handler="on_cpu_sockets_changed" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</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>
<property name="vexpand">True</property>
<property name="invisible_char">●</property>
<property name="text" translatable="yes">1</property>
<property name="adjustment">adjustment4</property>
<property name="value">1</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>
<property name="hexpand">True</property>
<property name="vexpand">True</property>
<property name="invisible_char">●</property>
<property name="text" translatable="yes">1</property>
<property name="adjustment">adjustment5</property>
<property name="value">1</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>
details: Allow setting direct kernel/initrd boot
2010-12-12 07:00:19 +03:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
</object>
</child>
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label62">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;To_pology&lt;/b&gt;</property>
<property name="use_markup">True</property>
<property name="use_underline">True</property>
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">2</property>
</packing>
</child>
<child internal-child="accessible">
<object class="AtkObject" id="vbox14-atkobject">
<property name="AtkObject::accessible-name">cpu-tab</property>
</object>
</child>
</object>
<packing>
<property name="position">3</property>
</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>
<property name="position">3</property>
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkBox" id="vbox7">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<child>
<object class="GtkFrame" id="frame5">
<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="alignment23">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<child>
<object class="GtkGrid" id="table6">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="border_width">3</property>
<property name="row_spacing">6</property>
<property name="column_spacing">6</property>
<child>
<object class="GtkLabel" id="label60">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="valign">center</property>
virtManager: Remove max memory UI and memory hotplug support This was proposed here: https://www.redhat.com/archives/virt-tools-list/2019-June/msg00117.html """ * UI maxmem and maxcpu notions, and related memballoon and cpu hotplug operations. These have been in the UI forever but I'm not sure people actually use them. cpu hotplug has always been a mess, and unless the user plans ahead by setting a high maxmem value ballooning is only good for reducing memory. These all sound like advanced usage to me that just confuses the typical usecase of adding more mem or vcpus to an offline VM. And the hotplug operations with virsh are simple to invoke. So I'd like to drop this from the UI """ The remaining field sets both max and current memory in the inactive XML Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-01-25 23:25:16 +03:00
<property name="label" translatable="yes">Memory a_llocation:</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="use_underline">True</property>
<property name="mnemonic_widget">mem-memory</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label61">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="valign">center</property>
<property name="label" translatable="yes">Total host memory:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="state-host-memory">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="valign">center</property>
<property name="label">2 GiB</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="GtkBox" id="hbox46">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="valign">center</property>
<property name="hexpand">True</property>
<property name="spacing">3</property>
<child>
<object class="GtkSpinButton" id="mem-memory">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
<property name="text" translatable="yes">50</property>
<property name="adjustment">adjustment2</property>
<property name="climb_rate">2</property>
<property name="numeric">True</property>
<property name="update_policy">if-valid</property>
<property name="value">50</property>
<signal name="changed" handler="on_mem_memory_changed" swapped="no"/>
<child internal-child="accessible">
<object class="AtkObject" id="mem-memory-atkobject">
<property name="AtkObject::accessible-name">Memory Select</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="GtkLabel" id="label306">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label" translatable="yes">MiB</property>
</object>
<packing>
<property name="expand">True</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>
</object>
</child>
</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">&lt;b&gt;Memory&lt;/b&gt;</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>
<child internal-child="accessible">
<object class="AtkObject" id="vbox7-atkobject">
<property name="AtkObject::accessible-name">memory-tab</property>
</object>
</child>
</object>
<packing>
<property name="position">4</property>
</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>
<property name="position">4</property>
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkGrid" id="vbox4">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="row_spacing">24</property>
<child>
<object class="GtkFrame" id="frame4">
<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="alignment2">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<child>
<object class="GtkCheckButton" id="boot-autostart">
<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="halign">start</property>
<property name="use_underline">True</property>
<property name="draw_indicator">True</property>
<signal name="toggled" handler="on_boot_autostart_changed" swapped="no"/>
</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">&lt;b&gt;Autostart&lt;/b&gt;</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>
<object class="GtkGrid" id="grid3">
<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="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>
details: Expose fine grained boot config Basically put an explicit device list in the boot UI, if the hypervisor supports it. For unsupported hv, use the same old disk/cd/floppy/net UI.
2014-02-10 01:21:26 +04:00
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child>
<object class="GtkLabel" id="label69">
details: Expose fine grained boot config Basically put an explicit device list in the boot UI, if the hypervisor supports it. For unsupported hv, use the same old disk/cd/floppy/net UI.
2014-02-10 01:21:26 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="halign">start</property>
<property name="label" translatable="yes">Init _path:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">boot-init-path</property>
details: Expose fine grained boot config Basically put an explicit device list in the boot UI, if the hypervisor supports it. For unsupported hv, use the same old disk/cd/floppy/net UI.
2014-02-10 01:21:26 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label64">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<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">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="width_chars">25</property>
<signal name="changed" handler="on_boot_init_args_changed" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
</packing>
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
</child>
uitests: Add choosecd dialog tests
2018-01-20 01:34:32 +03:00
</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>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child type="label">
<object class="GtkLabel" id="labelll">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="label" translatable="yes">&lt;b&gt;Container init&lt;/b&gt;</property>
<property name="use_markup">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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03: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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkBox" id="box1">
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="orientation">vertical</property>
<property name="spacing">6</property>
<child>
<object class="GtkCheckButton" id="boot-kernel-enable">
<property name="label" translatable="yes">Ena_ble direct kernel boot</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
<property name="halign">start</property>
<property name="use_underline">True</property>
<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>
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkBox" id="boot-kernel-box">
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="spacing">6</property>
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkGrid" id="table13">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="column_spacing">6</property>
<child>
<object class="GtkLabel" id="label38">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="margin_top">8</property>
<property name="margin_bottom">8</property>
<property name="label" translatable="yes">Ke_rnel path:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">boot-kernel</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label39">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="margin_top">8</property>
<property name="margin_bottom">8</property>
<property name="label" translatable="yes">_Initrd path:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">boot-initrd</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkBox" id="box3">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="valign">center</property>
<property name="hexpand">True</property>
<property name="spacing">6</property>
<child>
<object class="GtkEntry" id="boot-initrd">
<property name="visible">True</property>
<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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
details: Convert disk UI from table to grid
2013-10-04 16:01:18 +04:00
</packing>
</child>
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkButton" id="boot-initrd-browse">
<property name="label" translatable="yes">Browse</property>
details: Convert disk UI from table to grid
2013-10-04 16:01:18 +04:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<signal name="clicked" handler="on_boot_initrd_browse_clicked" swapped="no"/>
<child internal-child="accessible">
<object class="AtkObject" id="boot-initrd-browse-atkobject">
<property name="AtkObject::accessible-name">initrd-browse</property>
</object>
</child>
details: Convert disk UI from table to grid
2013-10-04 16:01:18 +04:00
</object>
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03: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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</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>
<property name="valign">center</property>
<property name="hexpand">True</property>
<property name="spacing">6</property>
virt-manager: Add checkbox controlling disk 'removable' flag (crobinso: Fix to use grid rework)
2013-10-04 05:39:01 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkEntry" id="boot-kernel">
virt-manager: Add checkbox controlling disk 'removable' flag (crobinso: Fix to use grid rework)
2013-10-04 05:39:01 +04:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
<signal name="changed" handler="on_boot_kernel_changed" swapped="no"/>
virt-manager: Add checkbox controlling disk 'removable' flag (crobinso: Fix to use grid rework)
2013-10-04 05:39:01 +04:00
</object>
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
virt-manager: Add checkbox controlling disk 'removable' flag (crobinso: Fix to use grid rework)
2013-10-04 05:39:01 +04:00
</packing>
</child>
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkButton" id="boot-kernel-browse">
<property name="label" translatable="yes">Browse</property>
virt-manager: Add checkbox controlling disk 'removable' flag (crobinso: Fix to use grid rework)
2013-10-04 05:39:01 +04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="receives_default">True</property>
<signal name="clicked" handler="on_boot_kernel_browse_clicked" swapped="no"/>
<child internal-child="accessible">
<object class="AtkObject" id="boot-kernel-browse-atkobject">
<property name="AtkObject::accessible-name">kernel-browse</property>
</object>
</child>
virt-manager: Add checkbox controlling disk 'removable' flag (crobinso: Fix to use grid rework)
2013-10-04 05:39:01 +04:00
</object>
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
virt-manager: Add checkbox controlling disk 'removable' flag (crobinso: Fix to use grid rework)
2013-10-04 05:39:01 +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
</object>
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label40">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="margin_top">8</property>
<property name="margin_bottom">8</property>
<property name="label" translatable="yes">Kernel ar_gs:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">boot-kernel-args</property>
</object>
<packing>
<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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="hexpand">True</property>
<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>
<property name="halign">start</property>
<property name="margin_top">8</property>
<property name="margin_bottom">8</property>
<property name="label" translatable="yes">D_TB path:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">boot-dtb</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkBox" id="boot-dtb-box">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="valign">center</property>
<property name="hexpand">True</property>
<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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkEntry" id="boot-dtb">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
<signal name="changed" handler="on_boot_dtb_changed" swapped="no"/>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
details: Allow easily changing network source Use the same drop down for network source we use in add hardware and create VM wizard. Allows easily trying different virtual networks or bridges.
2011-03-17 23:33:40 +03:00
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child>
<object class="GtkButton" id="boot-dtb-browse">
<property name="label" translatable="yes">Browse</property>
virt-manager: make mode for direct interfaces selectable Next try ... The following patch adds support to select the mode for direct interfaces. crobinso: small fixes to make check-pylint happy Signed-off-by: Gerhard Stenzel <gerhard.stenzel@de.ibm.com>
2011-04-19 15:08:15 +04:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<signal name="clicked" handler="on_boot_dtb_browse_clicked" swapped="no"/>
<child internal-child="accessible">
<object class="AtkObject" id="boot-dtb-browse-atkobject">
<property name="AtkObject::accessible-name">dtb-browse</property>
</object>
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03: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>
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="expand">False</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>
uitests: Add choosecd dialog tests
2018-01-20 01:34:32 +03:00
</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>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child type="label">
<object class="GtkLabel" id="label37">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="label" translatable="yes">&lt;b&gt;Dir_ect kernel boot&lt;/b&gt;</property>
<property name="use_markup">True</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>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03: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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 22:55:18 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkBox" id="bootvbox">
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 22:55:18 +03:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="orientation">vertical</property>
<property name="spacing">6</property>
<child>
<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>
<property name="halign">start</property>
<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>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 22:55:18 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkGrid" id="table2">
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 22:55:18 +03:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="halign">start</property>
<property name="hexpand">False</property>
<property name="row_spacing">6</property>
<property name="column_spacing">6</property>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkScrolledWindow" id="scrolledwindow3">
<property name="width_request">125</property>
<property name="height_request">125</property>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">True</property>
<property name="hscrollbar_policy">never</property>
<property name="shadow_type">in</property>
addhw: Use gtkgrid for network UI
2013-09-09 19:37:32 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkTreeView" id="boot-list">
addhw: Use gtkgrid for network UI
2013-09-09 19:37:32 +04:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">True</property>
<property name="headers_visible">False</property>
<child internal-child="selection">
<object class="GtkTreeSelection">
<signal name="changed" handler="on_boot_list_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>
details: Allow easily changing between VNC and SPICE
2011-03-17 21:24:36 +03:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkBox" id="box13">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkButton" id="boot-moveup">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="sensitive">False</property>
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<property name="valign">start</property>
<signal name="clicked" handler="on_boot_moveup_clicked" swapped="no"/>
addhw: Use gtkgrid for network UI
2013-09-09 19:37:32 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<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>
<child internal-child="accessible">
<object class="AtkObject" id="boot-moveup-atkobject">
<property name="AtkObject::accessible-name">boot-moveup</property>
</object>
addhw: Use gtkgrid for network UI
2013-09-09 19:37:32 +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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
details: Drop combo_or_label paradigm, use combobox entries So we can handle unknown XML values and give users more flexibility for things we can't predict.
2013-09-28 20:21:35 +04:00
</packing>
</child>
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkButton" id="boot-movedown">
details: Drop combo_or_label paradigm, use combobox entries So we can handle unknown XML values and give users more flexibility for things we can't predict.
2013-09-28 20:21:35 +04:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="sensitive">False</property>
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<property name="valign">start</property>
Break out shared network list UI to netlist.py Use this to show vport stuff in addhw, give a warning about macvtap networking, and allow macvtap from the create wizard.
2014-01-28 01:58:45 +04:00
<property name="vexpand">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<signal name="clicked" handler="on_boot_movedown_clicked" swapped="no"/>
Break out shared network list UI to netlist.py Use this to show vport stuff in addhw, give a warning about macvtap networking, and allow macvtap from the create wizard.
2014-01-28 01:58:45 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<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>
<child internal-child="accessible">
<object class="AtkObject" id="boot-movedown-atkobject">
<property name="AtkObject::accessible-name">boot-movedown</property>
</object>
addhw: Use gtkgrid for network UI
2013-09-09 19:37:32 +04:00
</child>
</object>
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03: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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
</child>
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
</object>
</child>
</object>
</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">&lt;b&gt;Boot device order&lt;/b&gt;</property>
<property name="use_markup">True</property>
</object>
</child>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
<child internal-child="accessible">
<object class="AtkObject" id="vbox4-atkobject">
<property name="AtkObject::accessible-name">boot-tab</property>
</object>
</child>
</object>
<packing>
<property name="position">5</property>
</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>
<property name="position">5</property>
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkBox" id="vbox55">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<property name="spacing">12</property>
<child>
<object class="GtkFrame" id="frame10">
<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="alignment149">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<child>
<object class="GtkBox" id="vbox13">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<property name="spacing">12</property>
<child>
<object class="GtkGrid" id="table32">
<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="label4">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="label" translatable="yes">Storage size:</property>
</object>
<packing>
<property name="left_attach">0</property>
virtManager: Only allow editing disk bus for new VM This was proposed here: https://www.redhat.com/archives/virt-tools-list/2019-June/msg00117.html """ * disk: bus editing: maybe keep this for the customize wizard, but it should go away for existing disks, changing it for an existing VM is definitely a 'shoot yourself in the foot' type of thing for most users """ Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-01-26 00:04:12 +03:00
<property name="top_attach">3</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</packing>
</child>
<child>
<object class="GtkLabel" id="disk-size">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label">size</property>
</object>
<packing>
<property name="left_attach">1</property>
virtManager: Only allow editing disk bus for new VM This was proposed here: https://www.redhat.com/archives/virt-tools-list/2019-June/msg00117.html """ * disk: bus editing: maybe keep this for the customize wizard, but it should go away for existing disks, changing it for an existing VM is definitely a 'shoot yourself in the foot' type of thing for most users """ Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-01-26 00:04:12 +03:00
<property name="top_attach">3</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</packing>
</child>
<child>
<object class="GtkLabel" id="disk-source-mnemonic">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="label" translatable="yes">Source _path:</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="disk-target-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<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">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="hexpand">True</property>
<property name="spacing">6</property>
create: Move mac address editing to customize dialog People should rarely need to edit the mac address, so remove it from the create wizard. However we only allow editing the mac address in the 'customize' dialog: regular network details disables editing, since that should be a rare and potentially dangerous operation.
2015-04-08 01:52:35 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkLabel" id="disk-source-label">
create: Move mac address editing to customize dialog People should rarely need to edit the mac address, so remove it from the create wizard. However we only allow editing the mac address in the 'customize' dialog: regular network details disables editing, since that should be a rare and potentially dangerous operation.
2015-04-08 01:52:35 +03:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="halign">start</property>
<property name="label">pathlabel</property>
<property name="selectable">True</property>
<property name="ellipsize">start</property>
<child internal-child="accessible">
<object class="AtkObject" id="disk-source-label-atkobject">
<property name="AtkObject::accessible-name">disk-source-path</property>
create: Move mac address editing to customize dialog People should rarely need to edit the mac address, so remove it from the create wizard. However we only allow editing the mac address in the 'customize' dialog: regular network details disables editing, since that should be a rare and potentially dangerous operation.
2015-04-08 01:52:35 +03:00
</object>
</child>
</object>
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
details: Show ipv4 and ipv6 address in details page of interface If the interface's type is 'network', then code uses lease as one of parameters of interface_addresses to get ipv4 and ipv6 address. If the result is negative, then uses agent to try again, If the result is still negative, uses arp for final try. Signed-off-by: Lin Ma <lma@suse.com>
2018-08-31 13:37:30 +03:00
</packing>
</child>
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkBox" id="disk-source-box">
details: Show ipv4 and ipv6 address in details page of interface If the interface's type is 'network', then code uses lease as one of parameters of interface_addresses to get ipv4 and ipv6 address. If the result is negative, then uses agent to try again, If the result is still negative, uses arp for final try. Signed-off-by: Lin Ma <lma@suse.com>
2018-08-31 13:37:30 +03:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: IP address fixes/improvements * Tweak the UI * Add accelerator for the refresh button * Make the IP labels selectable * Drop the IP prefix from the UI, it's not the important bit * Call DHCPLeases on the network instead to support this for more drivers, like LXC * Cache the IP results in the domain/network object wrappers * Catch and log errors * Poll for IP address when first visiting the interface page
2018-09-05 02:02:40 +03:00
<property name="spacing">6</property>
details: Show ipv4 and ipv6 address in details page of interface If the interface's type is 'network', then code uses lease as one of parameters of interface_addresses to get ipv4 and ipv6 address. If the result is negative, then uses agent to try again, If the result is still negative, uses arp for final try. Signed-off-by: Lin Ma <lma@suse.com>
2018-08-31 13:37:30 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkAlignment" id="disk-source-align">
details: Show ipv4 and ipv6 address in details page of interface If the interface's type is 'network', then code uses lease as one of parameters of interface_addresses to get ipv4 and ipv6 address. If the result is negative, then uses agent to try again, If the result is still negative, uses arp for final try. Signed-off-by: Lin Ma <lma@suse.com>
2018-08-31 13:37:30 +03:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child>
<placeholder/>
</child>
details: Show ipv4 and ipv6 address in details page of interface If the interface's type is 'network', then code uses lease as one of parameters of interface_addresses to get ipv4 and ipv6 address. If the result is negative, then uses agent to try again, If the result is still negative, uses arp for final try. Signed-off-by: Lin Ma <lma@suse.com>
2018-08-31 13:37:30 +03:00
</object>
<packing>
details: IP address fixes/improvements * Tweak the UI * Add accelerator for the refresh button * Make the IP labels selectable * Drop the IP prefix from the UI, it's not the important bit * Call DHCPLeases on the network instead to support this for more drivers, like LXC * Cache the IP results in the domain/network object wrappers * Catch and log errors * Poll for IP address when first visiting the interface page
2018-09-05 02:02:40 +03:00
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
details: Show ipv4 and ipv6 address in details page of interface If the interface's type is 'network', then code uses lease as one of parameters of interface_addresses to get ipv4 and ipv6 address. If the result is negative, then uses agent to try again, If the result is still negative, uses arp for final try. Signed-off-by: Lin Ma <lma@suse.com>
2018-08-31 13:37:30 +03:00
</packing>
</child>
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkButton" id="disk-source-browse">
<property name="label" translatable="yes">_Browse</property>
details: Show ipv4 and ipv6 address in details page of interface If the interface's type is 'network', then code uses lease as one of parameters of interface_addresses to get ipv4 and ipv6 address. If the result is negative, then uses agent to try again, If the result is still negative, uses arp for final try. Signed-off-by: Lin Ma <lma@suse.com>
2018-08-31 13:37:30 +03:00
<property name="visible">True</property>
details: IP address fixes/improvements * Tweak the UI * Add accelerator for the refresh button * Make the IP labels selectable * Drop the IP prefix from the UI, it's not the important bit * Call DHCPLeases on the network instead to support this for more drivers, like LXC * Cache the IP results in the domain/network object wrappers * Catch and log errors * Poll for IP address when first visiting the interface page
2018-09-05 02:02:40 +03:00
<property name="can_focus">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="receives_default">True</property>
details: IP address fixes/improvements * Tweak the UI * Add accelerator for the refresh button * Make the IP labels selectable * Drop the IP prefix from the UI, it's not the important bit * Call DHCPLeases on the network instead to support this for more drivers, like LXC * Cache the IP results in the domain/network object wrappers * Catch and log errors * Poll for IP address when first visiting the interface page
2018-09-05 02:02:40 +03:00
<property name="use_underline">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<signal name="clicked" handler="on_disk_source_browse_clicked" swapped="no"/>
details: Show ipv4 and ipv6 address in details page of interface If the interface's type is 'network', then code uses lease as one of parameters of interface_addresses to get ipv4 and ipv6 address. If the result is negative, then uses agent to try again, If the result is still negative, uses arp for final try. Signed-off-by: Lin Ma <lma@suse.com>
2018-08-31 13:37:30 +03:00
</object>
<packing>
details: IP address fixes/improvements * Tweak the UI * Add accelerator for the refresh button * Make the IP labels selectable * Drop the IP prefix from the UI, it's not the important bit * Call DHCPLeases on the network instead to support this for more drivers, like LXC * Cache the IP results in the domain/network object wrappers * Catch and log errors * Poll for IP address when first visiting the interface page
2018-09-05 02:02:40 +03:00
<property name="expand">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="fill">True</property>
details: IP address fixes/improvements * Tweak the UI * Add accelerator for the refresh button * Make the IP labels selectable * Drop the IP prefix from the UI, it's not the important bit * Call DHCPLeases on the network instead to support this for more drivers, like LXC * Cache the IP results in the domain/network object wrappers * Catch and log errors * Poll for IP address when first visiting the interface page
2018-09-05 02:02:40 +03:00
<property name="position">1</property>
details: Show ipv4 and ipv6 address in details page of interface If the interface's type is 'network', then code uses lease as one of parameters of interface_addresses to get ipv4 and ipv6 address. If the result is negative, then uses agent to try again, If the result is still negative, uses arp for final try. Signed-off-by: Lin Ma <lma@suse.com>
2018-08-31 13:37:30 +03:00
</packing>
</child>
</object>
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">1</property>
details: Show ipv4 and ipv6 address in details page of interface If the interface's type is 'network', then code uses lease as one of parameters of interface_addresses to get ipv4 and ipv6 address. If the result is negative, then uses agent to try again, If the result is still negative, uses arp for final try. Signed-off-by: Lin Ma <lma@suse.com>
2018-08-31 13:37:30 +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
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</child>
List, display info about, and enable removing VM host devices.
2009-01-23 01:00:38 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkLabel" id="label375">
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="halign">end</property>
<property name="label" translatable="yes">Device type:</property>
<property name="use_underline">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
</child>
virtManager: Only allow editing disk bus for new VM This was proposed here: https://www.redhat.com/archives/virt-tools-list/2019-June/msg00117.html """ * disk: bus editing: maybe keep this for the customize wizard, but it should go away for existing disks, changing it for an existing VM is definitely a 'shoot yourself in the foot' type of thing for most users """ Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-01-26 00:04:12 +03:00
<child>
<object class="GtkLabel" id="disk-bus-labeller">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="label" translatable="yes">Disk b_us:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">disk-bus-text</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkBox">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">3</property>
<child>
<object class="GtkComboBox" id="disk-bus">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="has_entry">True</property>
<signal name="changed" handler="on_disk_bus_combo_changed" swapped="no"/>
<child internal-child="entry">
<object class="GtkEntry" id="disk-bus-text">
<property name="can_focus">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="GtkLabel" id="disk-bus-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">disk-bus-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">2</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +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
</child>
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03: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
<child>
addstorage: Absorb advanced field UI Share the UI for changing all these disk properties: - shareable - readonly - removable - cache - discard - detect zeroes Move them all under the 'Advanced options' expander in details, and add the checkbox options to the addhardware wizard. Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-09-08 01:29:20 +03:00
<object class="GtkAlignment" id="storage-advanced-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>
addstorage: Absorb advanced field UI Share the UI for changing all these disk properties: - shareable - readonly - removable - cache - discard - detect zeroes Move them all under the 'Advanced options' expander in details, and add the checkbox options to the addhardware wizard. Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-09-08 01:29:20 +03: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
<child>
addstorage: Absorb advanced field UI Share the UI for changing all these disk properties: - shareable - readonly - removable - cache - discard - detect zeroes Move them all under the 'Advanced options' expander in details, and add the checkbox options to the addhardware wizard. Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-09-08 01:29:20 +03:00
<placeholder/>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="expand">False</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>
uitests: Add choosecd dialog tests
2018-01-20 01:34:32 +03:00
</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>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child type="label">
<object class="GtkLabel" id="label376">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="label" translatable="yes">&lt;b&gt;Virtual Disk&lt;/b&gt;</property>
<property name="use_markup">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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkButtonBox" id="hbuttonbox9">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">5</property>
<property name="layout_style">end</property>
<child>
<placeholder/>
</child>
<child>
<placeholder/>
</child>
<child>
<placeholder/>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
<property name="pack_type">end</property>
<property name="position">1</property>
</packing>
</child>
<child internal-child="accessible">
<object class="AtkObject" id="vbox55-atkobject">
<property name="AtkObject::accessible-name">disk-tab</property>
</object>
</child>
</object>
<packing>
<property name="position">6</property>
</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>
<property name="position">6</property>
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkBox" id="vbox54">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<property name="spacing">12</property>
<child>
<object class="GtkFrame" id="frame9">
<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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkAlignment" id="alignment137">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkGrid" id="table31">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="border_width">3</property>
<property name="row_spacing">6</property>
<property name="column_spacing">6</property>
<child>
<object class="GtkLabel" id="label509">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="label" translatable="yes">Device mode_l:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">network-model</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="mac-address-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
uitests: Increase details + domain + vmwindow coverage Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-08-27 01:01:02 +03:00
<property name="label" translatable="yes">_MAC address:</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="use_underline">True</property>
uitests: Increase details + domain + vmwindow coverage Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-08-27 01:01:02 +03:00
<property name="mnemonic_widget">network-mac-entry</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkComboBox" id="network-model">
<property name="visible">True</property>
<property name="can_focus">False</property>
<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">
<object class="GtkEntry" id="network-model-text">
<property name="can_focus">True</property>
</object>
</child>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">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
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03: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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="hexpand">False</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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<placeholder/>
</child>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkAlignment" id="network-source-ui-align">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="hexpand">False</property>
<property name="vexpand">False</property>
<child>
<placeholder/>
</child>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
</child>
<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>
<property name="halign">start</property>
<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"/>
uitests: Increase details + domain + vmwindow coverage Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-08-27 01:01:02 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="network-mac-entry-atkobject">
<property name="AtkObject::accessible-name">mac-entry</property>
</object>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03: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">2</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="network-link-state-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="label" translatable="yes">Link _state:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">network-link-state-checkbox</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">4</property>
</packing>
</child>
<child>
<object class="GtkCheckButton" id="network-link-state-checkbox">
<property name="label" translatable="yes">active</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
<property name="halign">start</property>
<property name="draw_indicator">True</property>
<signal name="toggled" handler="on_network_link_state_checkbox_toggled" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">4</property>
</packing>
</child>
<child>
<object class="GtkBox">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">6</property>
<child>
<object class="GtkLabel" id="network-ip">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">label</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="GtkButton" id="refresh-ip">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
<property name="halign">start</property>
<property name="use_underline">True</property>
<signal name="clicked" handler="on_network_refresh_ip_clicked" swapped="no"/>
Support viewing and removing VM 'video' devices.
2009-07-09 22:35:55 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkImage">
Support viewing and removing VM 'video' devices.
2009-07-09 22:35:55 +04:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="stock">gtk-refresh</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</object>
Some 'Details' UI cleanup. The main change is removing the duplication of the 'Apply' and 'Remove' buttons in the UI. This has no functional change, but from a dev perspective this saves annoying duplication when new device support is added. Also fix up some minor layout and spacing issues.
2009-07-09 22:35:36 +04:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">1</property>
</packing>
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child>
<object class="GtkLabel">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="halign">end</property>
<property name="label" translatable="yes">I_P address:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">refresh-ip</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">0</property>
<property name="top_attach">3</property>
</packing>
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
uitests: Add choosecd dialog tests
2018-01-20 01:34:32 +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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child type="label">
<object class="GtkLabel" id="label367">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="label" translatable="yes">&lt;b&gt;Virtual Network Interface&lt;/b&gt;</property>
<property name="use_markup">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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child internal-child="accessible">
<object class="AtkObject" id="vbox54-atkobject">
<property name="AtkObject::accessible-name">network-tab</property>
</object>
</child>
</object>
<packing>
<property name="position">7</property>
</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>
<property name="position">7</property>
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkBox" id="vbox56">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<property name="spacing">12</property>
<child>
<object class="GtkFrame" id="frame11">
<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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkAlignment" id="alignment150">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkGrid" id="table33">
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="border_width">3</property>
<property name="row_spacing">4</property>
<property name="column_spacing">8</property>
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkLabel" id="label402">
details: Centralize most hardware page spacing
2010-12-12 00:40:24 +03:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="halign">end</property>
<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="label405">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="label" translatable="yes">Mode:</property>
</object>
<packing>
<property name="left_attach">0</property>
<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>
<property name="halign">start</property>
<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>
<property name="halign">start</property>
<property name="label">label403</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
</child>
</object>
</child>
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label407">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;Virtual Input Device&lt;/b&gt;</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 internal-child="accessible">
<object class="AtkObject" id="vbox56-atkobject">
<property name="AtkObject::accessible-name">input-tab</property>
</object>
</child>
</object>
<packing>
<property name="position">8</property>
</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>
<property name="position">8</property>
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkBox" id="vbox57">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<child>
<object class="GtkFrame" id="vnc-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="graphics-align">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<child>
<placeholder/>
</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">&lt;b&gt;Display title&lt;/b&gt;</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 internal-child="accessible">
<object class="AtkObject" id="vbox57-atkobject">
<property name="AtkObject::accessible-name">graphics-tab</property>
</object>
</child>
</object>
<packing>
<property name="position">9</property>
</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>
<property name="position">9</property>
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkBox" id="vbox58">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<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>
<object class="GtkGrid" id="table36">
<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="label452">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="valign">center</property>
<property name="label" translatable="yes">M_odel:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">sound-model-text</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child>
<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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03: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="sound-model-text">
<property name="can_focus">True</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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
Some 'Details' UI cleanup. The main change is removing the duplication of the 'Apply' and 'Remove' buttons in the UI. This has no functional change, but from a dev perspective this saves annoying duplication when new device support is added. Also fix up some minor layout and spacing issues.
2009-07-09 22:35:36 +04:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
uitests: Add choosecd dialog tests
2018-01-20 01:34:32 +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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child type="label">
<object class="GtkLabel" id="label451">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="label" translatable="yes">&lt;b&gt;Sound Device&lt;/b&gt;</property>
<property name="use_markup">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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child internal-child="accessible">
<object class="AtkObject" id="vbox58-atkobject">
<property name="AtkObject::accessible-name">sound-tab</property>
</object>
</child>
</object>
<packing>
<property name="position">10</property>
</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>
<property name="position">10</property>
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkBox" id="vbox59">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<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>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkAlignment" id="alignment160">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
watchdog support: Add, remove, edit in place, and enumerate existing devs
2010-03-24 07:22:17 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkGrid" id="table37">
watchdog support: Add, remove, edit in place, and enumerate existing devs
2010-03-24 07:22:17 +03:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="border_width">3</property>
<property name="row_spacing">4</property>
<property name="column_spacing">8</property>
watchdog support: Add, remove, edit in place, and enumerate existing devs
2010-03-24 07:22:17 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkLabel" id="char-dev-type-label">
watchdog support: Add, remove, edit in place, and enumerate existing devs
2010-03-24 07:22:17 +03:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="halign">end</property>
<property name="label" translatable="yes">Device type:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="char-dev-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label" translatable="yes">label506</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="char-source-path">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<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>
<object class="GtkLabel" id="char-bind-host">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label">label</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">3</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="char-target-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<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>
<property name="halign">start</property>
<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>
</packing>
</child>
<child>
<object class="GtkLabel" id="char-target-state">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label" translatable="yes">label507</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">6</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="char-source-host">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label">label</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="char-source-host-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="label" translatable="yes">Source host:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="char-bind-host-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="label" translatable="yes">Bind host:</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">0</property>
<property name="top_attach">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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child>
<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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="halign">end</property>
<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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">0</property>
<property name="top_attach">4</property>
</packing>
watchdog support: Add, remove, edit in place, and enumerate existing devs
2010-03-24 07:22:17 +03:00
</child>
details: Allow viewing/removing controller devices
2010-12-16 20:41:47 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkLabel" id="char-target-name-label">
details: Allow viewing/removing controller devices
2010-12-16 20:41:47 +03:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="halign">end</property>
<property name="label" translatable="yes">Target name:</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">0</property>
<property name="top_attach">5</property>
</packing>
details: Allow viewing/removing controller devices
2010-12-16 20:41:47 +03:00
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child>
<object class="GtkLabel" id="char-target-state-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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="halign">end</property>
<property name="label" translatable="yes">State:</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">0</property>
<property name="top_attach">6</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="char-source-path-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="label" translatable="yes">Source path:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">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>
uitests: Add choosecd dialog tests
2018-01-20 01:34:32 +03:00
</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>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child type="label">
<object class="GtkLabel" id="char-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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="label" translatable="yes">&lt;b&gt;insert type&lt;/b&gt;</property>
<property name="use_markup">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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child internal-child="accessible">
<object class="AtkObject" id="vbox59-atkobject">
<property name="AtkObject::accessible-name">char-tab</property>
</object>
</child>
</object>
<packing>
<property name="position">11</property>
</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>
<property name="position">11</property>
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkBox" id="vbox8">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<child>
<object class="GtkFrame" id="frame6">
<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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkAlignment" id="alignment22">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkGrid" id="table50">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkLabel" id="label15">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="halign">start</property>
<property name="label" translatable="yes">Device:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="hostdev-source">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label">label</property>
<property name="selectable">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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">1</property>
<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>
<property name="halign">start</property>
<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>
<property name="halign">start</property>
<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>
</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>
uitests: Add choosecd dialog tests
2018-01-20 01:34:32 +03:00
</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>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child type="label">
<object class="GtkLabel" id="hostdev-title">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="label">&lt;b&gt;Physical Host Device&lt;/b&gt;</property>
<property name="use_markup">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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child internal-child="accessible">
<object class="AtkObject" id="vbox8-atkobject">
<property name="AtkObject::accessible-name">host-tab</property>
</object>
</child>
</object>
<packing>
<property name="position">12</property>
</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>
<property name="position">12</property>
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkBox" id="vbox9">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<child>
<object class="GtkFrame" id="frame8">
<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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkGrid">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="margin_top">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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkLabel" id="label18">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="halign">end</property>
<property name="label" translatable="yes">M_odel:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">video-model-text</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="video-model-text">
<property name="can_focus">True</property>
</object>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
details: Allow viewing/removing controller devices
2010-12-16 20:41:47 +03:00
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child>
<object class="GtkLabel" id="label9">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="label" translatable="yes">_3D acceleration:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">video-3d</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: List guest <filesystem> devices
2011-05-19 23:18:33 +04:00
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="left_attach">0</property>
details: Remove explicit video heads and ram reporting RAM is rarely changed from the default heads does not have any explicit virt-manager support and both are viewable from the XML editor. So remove the explicit fields for them Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-09-02 00:32:50 +03:00
<property name="top_attach">1</property>
details: List guest <filesystem> devices
2011-05-19 23:18:33 +04:00
</packing>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<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"/>
uitests: Add choosecd dialog tests
2018-01-20 01:34:32 +03:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">1</property>
details: Remove explicit video heads and ram reporting RAM is rarely changed from the default heads does not have any explicit virt-manager support and both are viewable from the XML editor. So remove the explicit fields for them Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-09-02 00:32:50 +03:00
<property name="top_attach">1</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</packing>
uitests: Add choosecd dialog tests
2018-01-20 01:34:32 +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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child type="label">
<object class="GtkLabel" id="hostdev-title1">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="label" translatable="yes">&lt;b&gt;Video&lt;/b&gt;</property>
<property name="use_markup">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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child internal-child="accessible">
<object class="AtkObject" id="vbox9-atkobject">
<property name="AtkObject::accessible-name">video-tab</property>
</object>
</child>
</object>
<packing>
<property name="position">13</property>
</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>
<property name="position">13</property>
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkBox" id="vbox12">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<child>
<object class="GtkFrame" id="frame15">
<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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkAlignment" id="alignment34">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
Add basic SmartCardDevice support This patch allows to add and list smartcard devices in host or passthrough & spicevmc mode. It doesn't provide all the various smartcard combination options, but it's good enough for Spice usage. (crobinso: various small tweaks)
2011-06-23 19:42:03 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkGrid" id="table8">
Add basic SmartCardDevice support This patch allows to add and list smartcard devices in host or passthrough & spicevmc mode. It doesn't provide all the various smartcard combination options, but it's good enough for Spice usage. (crobinso: various small tweaks)
2011-06-23 19:42:03 +04:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="row_spacing">4</property>
<property name="column_spacing">8</property>
Add basic SmartCardDevice support This patch allows to add and list smartcard devices in host or passthrough & spicevmc mode. It doesn't provide all the various smartcard combination options, but it's good enough for Spice usage. (crobinso: various small tweaks)
2011-06-23 19:42:03 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkLabel" id="label27">
Add basic SmartCardDevice support This patch allows to add and list smartcard devices in host or passthrough & spicevmc mode. It doesn't provide all the various smartcard combination options, but it's good enough for Spice usage. (crobinso: various small tweaks)
2011-06-23 19:42:03 +04:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="halign">end</property>
<property name="valign">center</property>
<property name="label" translatable="yes">Ac_tion:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">watchdog-action-text</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label35">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="valign">center</property>
<property name="label" translatable="yes">M_odel:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">watchdog-model-text</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkComboBox" id="watchdog-action">
<property name="visible">True</property>
<property name="can_focus">False</property>
<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="watchdog-action-text">
<property name="can_focus">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkComboBox" id="watchdog-model">
<property name="visible">True</property>
<property name="can_focus">False</property>
<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="watchdog-model-text">
<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>
Add basic SmartCardDevice support This patch allows to add and list smartcard devices in host or passthrough & spicevmc mode. It doesn't provide all the various smartcard combination options, but it's good enough for Spice usage. (crobinso: various small tweaks)
2011-06-23 19:42:03 +04:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
</child>
uitests: Add choosecd dialog tests
2018-01-20 01:34:32 +03:00
</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>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child type="label">
<object class="GtkLabel" id="hostdev-title2">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="label">&lt;b&gt;Watchdog&lt;/b&gt;</property>
<property name="use_markup">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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child internal-child="accessible">
<object class="AtkObject" id="vbox12-atkobject">
<property name="AtkObject::accessible-name">watchdog-tab</property>
</object>
</child>
</object>
<packing>
<property name="position">14</property>
</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>
<property name="position">14</property>
<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>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03: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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="row_spacing">6</property>
<property name="column_spacing">6</property>
virt-manager: Add redirected devices details
2011-09-02 05:23:27 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkLabel" id="label48">
virt-manager: Add redirected devices details
2011-09-02 05:23:27 +04:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="halign">end</property>
<property name="label" translatable="yes">Type:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="controller-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label">foo</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkComboBox" id="controller-model">
<property name="visible">True</property>
<property name="can_focus">False</property>
<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="controller-model-text">
<property name="can_focus">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
virt-manager: Add redirected devices details
2011-09-02 05:23:27 +04:00
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="controller-model-atkobject">
<property name="AtkObject::accessible-name">controller-model</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
virt-manager: Add redirected devices details
2011-09-02 05:23:27 +04:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
virt-manager: Add redirected devices details
2011-09-02 05:23:27 +04:00
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="left_attach">1</property>
<property name="top_attach">1</property>
Minor TPM UI fixups
2013-06-27 04:05:32 +04:00
</packing>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child>
<object class="GtkLabel" id="mlabel48">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="hexpand">False</property>
<property name="label" translatable="yes">M_odel:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">controller-model-text</property>
uitests: Add choosecd dialog tests
2018-01-20 01:34:32 +03:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
uitests: Add choosecd dialog tests
2018-01-20 01:34:32 +03:00
</child>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 17:39:56 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkLabel" id="device-list-label">
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 17:39:56 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<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>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 17:39:56 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkScrolledWindow" id="controller-device-scroll">
<property name="width_request">270</property>
<property name="height_request">100</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 17:39:56 +04:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">True</property>
<property name="shadow_type">in</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 17:39:56 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkTreeView" id="controller-device-list">
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 17:39:56 +04:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">True</property>
<child internal-child="selection">
<object class="GtkTreeSelection"/>
</child>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 17:39:56 +04:00
</object>
</child>
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 17:39:56 +04:00
</child>
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">2</property>
</packing>
uitests: Add choosecd dialog tests
2018-01-20 01:34:32 +03:00
</child>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 17:39:56 +04:00
</object>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</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">&lt;b&gt;Controller&lt;/b&gt;</property>
<property name="use_markup">True</property>
</object>
</child>
<child internal-child="accessible">
<object class="AtkObject" id="frame12-atkobject">
<property name="AtkObject::accessible-name">controller-tab</property>
</object>
</child>
</object>
<packing>
<property name="position">15</property>
</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>
<property name="position">15</property>
<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>
<object class="GtkAlignment" id="fs-alignment">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<child>
<placeholder/>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 17:39:56 +04:00
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label41">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;Filesystem&lt;/b&gt;</property>
<property name="use_markup">True</property>
</object>
</child>
<child internal-child="accessible">
<object class="AtkObject" id="frame16-atkobject">
<property name="AtkObject::accessible-name">filesystem-tab</property>
</object>
</child>
</object>
<packing>
<property name="position">16</property>
</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>
<property name="position">16</property>
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkBox" id="vbox16">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<child>
<object class="GtkFrame" id="frame18">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
virt-manager: add support for showing panic notifier device Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-01-10 13:37:55 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkAlignment" id="alignment46">
virt-manager: add support for showing panic notifier device Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-01-10 13:37:55 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
virt-manager: add support for showing panic notifier device Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-01-10 13:37:55 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkTable" id="table18">
virt-manager: add support for showing panic notifier device Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-01-10 13:37:55 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="border_width">3</property>
<property name="n_columns">2</property>
<property name="column_spacing">8</property>
<property name="row_spacing">4</property>
virt-manager: add support for showing panic notifier device Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-01-10 13:37:55 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkLabel" id="label74">
virt-manager: add support for showing panic notifier device Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-01-10 13:37:55 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="halign">start</property>
<property name="label" translatable="yes">M_ode:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">smartcard-mode-text</property>
</object>
<packing>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkComboBox" id="smartcard-mode">
<property name="visible">True</property>
<property name="can_focus">False</property>
<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="smartcard-mode-text">
<property name="name">smartcard-mode-text</property>
<property name="can_focus">True</property>
details: Couple mini 'panic' UI cleanups
2014-01-12 00:08:00 +04:00
</object>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="smartcard-mode-atkobject">
<property name="AtkObject::accessible-name">smartcard-mode</property>
virt-manager: add support for showing panic notifier device Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-01-10 13:37:55 +04:00
</object>
details: Couple mini 'panic' UI cleanups
2014-01-12 00:08:00 +04:00
</child>
virt-manager: add support for showing panic notifier device Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-01-10 13:37:55 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options">GTK_FILL</property>
</packing>
virt-manager: add support for showing panic notifier device Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-01-10 13:37:55 +04:00
</child>
</object>
</child>
</object>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child type="label">
<object class="GtkLabel" id="label75">
virt-manager: add support for showing panic notifier device Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-01-10 13:37:55 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="label" translatable="yes">&lt;b&gt;Smartcard Device&lt;/b&gt;</property>
<property name="use_markup">True</property>
virt-manager: add support for showing panic notifier device Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-01-10 13:37:55 +04:00
</object>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child internal-child="accessible">
<object class="AtkObject" id="vbox16-atkobject">
<property name="AtkObject::accessible-name">smartcard-tab</property>
</object>
</child>
</object>
<packing>
<property name="position">17</property>
</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>
<property name="position">17</property>
<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>
<child>
<object class="GtkAlignment" id="alignment161">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">12</property>
virt-manager: Add support for vsock device to Hardware Details UI Add support for vsock devices to Hardware Details UI so that vsock devices can be configured or removed. Signed-off-by: Slavomir Kaslev <kaslevs@vmware.com>
2018-12-14 17:34:19 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkGrid" id="table51">
virt-manager: Add support for vsock device to Hardware Details UI Add support for vsock devices to Hardware Details UI so that vsock devices can be configured or removed. Signed-off-by: Slavomir Kaslev <kaslevs@vmware.com>
2018-12-14 17:34:19 +03:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="border_width">3</property>
<property name="row_spacing">4</property>
<property name="column_spacing">8</property>
virt-manager: Add support for vsock device to Hardware Details UI Add support for vsock devices to Hardware Details UI so that vsock devices can be configured or removed. Signed-off-by: Slavomir Kaslev <kaslevs@vmware.com>
2018-12-14 17:34:19 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkLabel" id="label516">
virt-manager: Add support for vsock device to Hardware Details UI Add support for vsock devices to Hardware Details UI so that vsock devices can be configured or removed. Signed-off-by: Slavomir Kaslev <kaslevs@vmware.com>
2018-12-14 17:34:19 +03:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="halign">start</property>
<property name="label" translatable="yes">Type:</property>
virt-manager: Add support for vsock device to Hardware Details UI Add support for vsock devices to Hardware Details UI so that vsock devices can be configured or removed. Signed-off-by: Slavomir Kaslev <kaslevs@vmware.com>
2018-12-14 17:34:19 +03:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
virt-manager: Add support for vsock device to Hardware Details UI Add support for vsock devices to Hardware Details UI so that vsock devices can be configured or removed. Signed-off-by: Slavomir Kaslev <kaslevs@vmware.com>
2018-12-14 17:34:19 +03:00
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child>
<object class="GtkLabel" id="label519">
virt-manager: Add support for vsock device to Hardware Details UI Add support for vsock devices to Hardware Details UI so that vsock devices can be configured or removed. Signed-off-by: Slavomir Kaslev <kaslevs@vmware.com>
2018-12-14 17:34:19 +03:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="halign">start</property>
<property name="label" translatable="yes">Address:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="redir-address">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label" translatable="yes">foo:12</property>
virt-manager: Add support for vsock device to Hardware Details UI Add support for vsock devices to Hardware Details UI so that vsock devices can be configured or removed. Signed-off-by: Slavomir Kaslev <kaslevs@vmware.com>
2018-12-14 17:34:19 +03:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
</packing>
virt-manager: Add support for vsock device to Hardware Details UI Add support for vsock devices to Hardware Details UI so that vsock devices can be configured or removed. Signed-off-by: Slavomir Kaslev <kaslevs@vmware.com>
2018-12-14 17:34:19 +03:00
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child>
<object class="GtkLabel" id="redir-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label">redir type</property>
virt-manager: Add support for vsock device to Hardware Details UI Add support for vsock devices to Hardware Details UI so that vsock devices can be configured or removed. Signed-off-by: Slavomir Kaslev <kaslevs@vmware.com>
2018-12-14 17:34:19 +03:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
virt-manager: Add support for vsock device to Hardware Details UI Add support for vsock devices to Hardware Details UI so that vsock devices can be configured or removed. Signed-off-by: Slavomir Kaslev <kaslevs@vmware.com>
2018-12-14 17:34:19 +03:00
</child>
</object>
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
Some 'Details' UI cleanup. The main change is removing the duplication of the 'Apply' and 'Remove' buttons in the UI. This has no functional change, but from a dev perspective this saves annoying duplication when new device support is added. Also fix up some minor layout and spacing issues.
2009-07-09 22:35:36 +04:00
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child type="label">
<object class="GtkLabel" id="redir-title">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;Redirected device&lt;/b&gt;</property>
<property name="use_markup">True</property>
</object>
</child>
<child internal-child="accessible">
<object class="AtkObject" id="frame19-atkobject">
<property name="AtkObject::accessible-name">redir-tab</property>
</object>
</child>
</object>
<packing>
<property name="position">18</property>
</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>
<property name="position">18</property>
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkBox" id="vbox17">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<property name="spacing">12</property>
Some 'Details' UI cleanup. The main change is removing the duplication of the 'Apply' and 'Remove' buttons in the UI. This has no functional change, but from a dev perspective this saves annoying duplication when new device support is added. Also fix up some minor layout and spacing issues.
2009-07-09 22:35:36 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkFrame" id="frame20">
Some 'Details' UI cleanup. The main change is removing the duplication of the 'Apply' and 'Remove' buttons in the UI. This has no functional change, but from a dev perspective this saves annoying duplication when new device support is added. Also fix up some minor layout and spacing issues.
2009-07-09 22:35:36 +04:00
<property name="visible">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
details: Add a cancel button for undo-ing hw edits Next we introduce a dialog warning the user they have unapplied HW edits. This gives them a way to undo edits without having to force encounter the dialog.
2011-07-19 22:51:16 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkAlignment" id="alignment47">
details: Add a cancel button for undo-ing hw edits Next we introduce a dialog warning the user they have unapplied HW edits. This gives them a way to undo edits without having to force encounter the dialog.
2011-07-19 22:51:16 +04:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<child>
<object class="GtkGrid" id="table200">
<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="tpm-dev-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label">tpm-dev-type</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="tpm-device-path">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label">tpm-device-path</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label183">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="label" translatable="yes">Type:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="tpm-device-path-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="label" translatable="yes">Path:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
<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>
<child>
<object class="GtkLabel" id="tpm-model-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">end</property>
<property name="label" translatable="yes">Device mode_l:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">tpm-model-text</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">3</property>
</packing>
</child>
<child>
<object class="GtkComboBox" id="tpm-model">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="hexpand">False</property>
<property name="has_entry">True</property>
<signal name="changed" handler="on_tpm_model_combo_changed" swapped="no"/>
<child internal-child="entry">
<object class="GtkEntry" id="tpm-model-text">
<property name="can_focus">True</property>
</object>
</child>
uitests: Increase details + domain + vmwindow coverage Signed-off-by: Cole Robinson <crobinso@redhat.com>
2020-08-27 01:01:02 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="tpm-model-atkobject">
<property name="AtkObject::accessible-name">tpm-model</property>
</object>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">3</property>
</packing>
</child>
uitests: Several more 'New VM' tests, and cli --show tests
2015-09-09 16:49:45 +03:00
</object>
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: Add a cancel button for undo-ing hw edits Next we introduce a dialog warning the user they have unapplied HW edits. This gives them a way to undo edits without having to force encounter the dialog.
2011-07-19 22:51:16 +04:00
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child type="label">
<object class="GtkLabel" id="label180">
Some 'Details' UI cleanup. The main change is removing the duplication of the 'Apply' and 'Remove' buttons in the UI. This has no functional change, but from a dev perspective this saves annoying duplication when new device support is added. Also fix up some minor layout and spacing issues.
2009-07-09 22:35:36 +04:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;TPM Device&lt;/b&gt;</property>
<property name="use_markup">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
Some 'Details' UI cleanup. The main change is removing the duplication of the 'Apply' and 'Remove' buttons in the UI. This has no functional change, but from a dev perspective this saves annoying duplication when new device support is added. Also fix up some minor layout and spacing issues.
2009-07-09 22:35:36 +04:00
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="expand">True</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="fill">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="position">0</property>
Some 'Details' UI cleanup. The main change is removing the duplication of the 'Apply' and 'Remove' buttons in the UI. This has no functional change, but from a dev perspective this saves annoying duplication when new device support is added. Also fix up some minor layout and spacing issues.
2009-07-09 22:35:36 +04:00
</packing>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="vbox17-atkobject">
<property name="AtkObject::accessible-name">tpm-tab</property>
</object>
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
Some 'Details' UI cleanup. The main change is removing the duplication of the 'Apply' and 'Remove' buttons in the UI. This has no functional change, but from a dev perspective this saves annoying duplication when new device support is added. Also fix up some minor layout and spacing issues.
2009-07-09 22:35:36 +04:00
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="position">19</property>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
</packing>
</child>
<child type="tab">
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkLabel" id="label182">
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="label">tpm</property>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
</object>
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="position">19</property>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkFrame" id="frame21">
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkAlignment" id="alignment28">
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="left_padding">12</property>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<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>
<property name="halign">start</property>
<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>
<property name="halign">end</property>
<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>
<property name="halign">start</property>
<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>
<property name="halign">end</property>
<property name="label" translatable="yes">Host Device:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
</packing>
</child>
</object>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
</child>
</object>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child type="label">
<object class="GtkLabel" id="label89">
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="label" translatable="yes">&lt;b&gt;Random Number Generator&lt;/b&gt;</property>
<property name="use_markup">True</property>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
</object>
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child internal-child="accessible">
<object class="AtkObject" id="frame21-atkobject">
<property name="AtkObject::accessible-name">rng-tab</property>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
</object>
</child>
</object>
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="position">20</property>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
</packing>
</child>
<child type="tab">
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkLabel" id="label81">
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="label" translatable="yes">rng</property>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
</object>
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="position">20</property>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
console: Add a separate notebook for serial pages Rather than the 'offset' page hack we previously did that is hard to keep track of. This allows for a handful of code simplifications
2015-09-18 18:55:15 +03:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkFrame" id="frame17">
console: Add a separate notebook for serial pages Rather than the 'offset' page hack we previously did that is hard to keep track of. This allows for a handful of code simplifications
2015-09-18 18:55:15 +03:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<child>
<object class="GtkAlignment" id="alignment10">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="left_padding">12</property>
<child>
<object class="GtkGrid" id="table_panic">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="row_spacing">4</property>
<property name="column_spacing">8</property>
<child>
<object class="GtkLabel" id="panic-model-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="margin_top">3</property>
<property name="margin_bottom">3</property>
<property name="label" translatable="yes">Model:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="panic-model">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="label" translatable="yes">panic-model</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
</packing>
</child>
</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">&lt;b&gt;Panic Notifier&lt;/b&gt;</property>
<property name="use_markup">True</property>
</object>
</child>
uitests: console: Add live lxc serial test
2018-01-21 20:40:15 +03:00
<child internal-child="accessible">
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="AtkObject" id="frame17-atkobject">
<property name="AtkObject::accessible-name">panic-tab</property>
uitests: console: Add live lxc serial test
2018-01-21 20:40:15 +03:00
</object>
</child>
console: Add a separate notebook for serial pages Rather than the 'offset' page hack we previously did that is hard to keep track of. This allows for a handful of code simplifications
2015-09-18 18:55:15 +03:00
</object>
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="position">21</property>
console: Add a separate notebook for serial pages Rather than the 'offset' page hack we previously did that is hard to keep track of. This allows for a handful of code simplifications
2015-09-18 18:55:15 +03:00
</packing>
</child>
<child type="tab">
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkLabel" id="label93">
console: Add a separate notebook for serial pages Rather than the 'offset' page hack we previously did that is hard to keep track of. This allows for a handful of code simplifications
2015-09-18 18:55:15 +03:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="label" translatable="yes">panic</property>
console: Add a separate notebook for serial pages Rather than the 'offset' page hack we previously did that is hard to keep track of. This allows for a handful of code simplifications
2015-09-18 18:55:15 +03:00
</object>
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="position">21</property>
console: Add a separate notebook for serial pages Rather than the 'offset' page hack we previously did that is hard to keep track of. This allows for a handful of code simplifications
2015-09-18 18:55:15 +03:00
<property name="tab_fill">False</property>
</packing>
</child>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkFrame" id="frame25">
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
<property name="visible">True</property>
console: Convert from autodrawer to native Gtk widgets Gtk 3.10 has a GtkOverlay and GtkRevealer widget which we can use to more sustainably implement the autodrawer functionality.
2016-05-17 19:14:32 +03:00
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkAlignment" id="vsock-align">
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">12</property>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
<child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<placeholder/>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
</child>
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</child>
<child type="label">
<object class="GtkLabel" id="label67">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">&lt;b&gt;Virtio VSOCK&lt;/b&gt;</property>
<property name="use_markup">True</property>
</object>
</child>
<child internal-child="accessible">
<object class="AtkObject" id="frame25-atkobject">
<property name="AtkObject::accessible-name">vsock-tab</property>
</object>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
</child>
</object>
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="position">22</property>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
</packing>
</child>
<child type="tab">
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkLabel" id="label95">
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="label">vsock</property>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
</object>
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="position">22</property>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-02 01:40:38 +04:00
<property name="tab_fill">False</property>
</packing>
</child>
</object>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
</child>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkButtonBox" id="hbuttonbox3">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">12</property>
<property name="layout_style">end</property>
<child>
<object class="GtkButton" id="config-remove">
<property name="label">gtk-remove</property>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<property name="visible">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">True</property>
<property name="can_default">True</property>
<property name="receives_default">False</property>
<property name="use_stock">True</property>
<signal name="clicked" handler="on_config_remove_clicked" swapped="no"/>
<child internal-child="accessible">
<object class="AtkObject" id="config-remove-atkobject">
<property name="AtkObject::accessible-name">config-remove</property>
</object>
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">0</property>
Save glade files with glade-3
2008-10-31 17:18:55 +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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<object class="GtkButton" id="config-cancel">
<property name="label">gtk-cancel</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<property name="use_stock">True</property>
<signal name="clicked" handler="on_config_cancel_clicked" swapped="no"/>
<child internal-child="accessible">
<object class="AtkObject" id="config-cancel-atkobject">
<property name="AtkObject::accessible-name">config-cancel</property>
</object>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</child>
</object>
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="expand">False</property>
<property name="fill">False</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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<child>
<object class="GtkButton" id="config-apply">
<property name="label">gtk-apply</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. 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>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="sensitive">False</property>
<property name="can_focus">True</property>
<property name="can_default">True</property>
<property name="receives_default">False</property>
<property name="use_stock">True</property>
<signal name="clicked" handler="on_config_apply_clicked" swapped="no"/>
<child internal-child="accessible">
<object class="AtkObject" id="config-apply-atkobject">
<property name="AtkObject::accessible-name">config-apply</property>
</object>
</child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 18:18:47 +04:00
</object>
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="expand">False</property>
<property name="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
<property name="position">2</property>
</packing>
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
<packing>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="expand">False</property>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
<property name="fill">True</property>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<property name="position">1</property>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
</packing>
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
details: split out a top level vmwindow vmmVMWindow handles all the menuing, and coordinating between the console, snapshots, and details panel. Simplifies the details code a bit which will help when we add xmlediting
2019-05-05 23:25:35 +03:00
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
Save glade files with glade-3
2008-10-31 17:18:55 +03:00
</child>
Convert UI files from glade to gtkbuilder Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't even handle glade format files! This effectively drops support for running virt-manager on a RHEL5 host, which has a GTK that is too old to support gtkbuilder. The process here was: - On RHEL6, open all glade files with glade3, use Edit->Preferences to change format to gtk builder. (the gtk-builder-convert tool produced all sorts of brokenness, and f16 glade3 can't even open old glade files). - Open these new files in glade on f16 and resave (since glade is notorious for reformatting files over new versions, saves churn the first time someone goes to patch the UI using a modern glade)
2012-02-02 02:26:46 +04:00
</object>
</interface>
Reference in New Issue Copy Permalink