shaba/virt-manager
1
0
Fork 0
mirror of https://github.com/virt-manager/virt-manager.git synced 2025-01-25 06:03:55 +03:00
Code Issues Projects Releases Wiki Activity
virt-manager/ui/details.ui

6063 lines
412 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 15:57:40 -05:00
<?xml version="1.0" encoding="UTF-8"?>
details: Remove UI for security, apic, acpi, clock 99% of users never need to tweak them, and now that we have virt-xml, most of what they could want to do is a simple CLI oneliner.
2014-01-26 13:43:53 -05:00
<!-- Generated with glade 3.16.1 -->
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-01 17:26:46 -05:00
<interface>
details: Remove UI for security, apic, acpi, clock 99% of users never need to tweak them, and now that we have virt-xml, most of what they could want to do is a simple CLI oneliner.
2014-01-26 13:43:53 -05:00
<requires lib="gtk+" version="3.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-01 17:26:46 -05:00
<object class="GtkAccelGroup" id="accelgroup1"/>
<object class="GtkAdjustment" id="adjustment1">
<property name="lower">1</property>
<property name="upper">10240000</property>
<property name="value">50</property>
<property name="step_increment">1</property>
<property name="page_increment">25</property>
</object>
Resave glade files to drop gtk2 bits
2012-11-09 09:43:45 +01:00
<object class="GtkAdjustment" id="adjustment10">
<property name="upper">1000000000</property>
<property name="step_increment">1024</property>
</object>
<object class="GtkAdjustment" id="adjustment11">
<property name="upper">1000000000</property>
<property name="step_increment">10</property>
</object>
<object class="GtkAdjustment" id="adjustment12">
<property name="upper">1000000000</property>
<property name="step_increment">1024</property>
</object>
<object class="GtkAdjustment" id="adjustment13">
<property name="upper">1000000000</property>
<property name="step_increment">10</property>
</object>
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-01 17:26:46 -05:00
<object class="GtkAdjustment" id="adjustment2">
<property name="lower">1</property>
<property name="upper">10240000</property>
<property name="value">50</property>
<property name="step_increment">1</property>
<property name="page_increment">25</property>
</object>
<object class="GtkAdjustment" id="adjustment3">
<property name="lower">1</property>
<property name="upper">256</property>
<property name="value">1</property>
<property name="step_increment">1</property>
<property name="page_increment">10</property>
</object>
<object class="GtkAdjustment" id="adjustment4">
<property name="lower">1</property>
<property name="upper">256</property>
<property name="value">1</property>
<property name="step_increment">1</property>
<property name="page_increment">10</property>
</object>
<object class="GtkAdjustment" id="adjustment5">
<property name="lower">1</property>
<property name="upper">256</property>
<property name="value">1</property>
<property name="step_increment">1</property>
<property name="page_increment">10</property>
</object>
<object class="GtkAdjustment" id="adjustment6">
<property name="lower">1</property>
<property name="upper">1024</property>
<property name="value">1</property>
<property name="step_increment">1</property>
<property name="page_increment">2</property>
</object>
<object class="GtkAdjustment" id="adjustment7">
<property name="lower">1</property>
<property name="upper">1024</property>
<property name="value">2</property>
<property name="step_increment">1</property>
<property name="page_increment">2</property>
</object>
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
<object class="GtkAdjustment" id="adjustment8">
<property name="upper">1000000000</property>
<property name="step_increment">1024</property>
</object>
<object class="GtkAdjustment" id="adjustment9">
<property name="upper">1000000000</property>
<property name="step_increment">10</property>
</object>
ui: Set non-stock button images in glade, not explicitly in code
2013-09-22 12:18:49 -04:00
<object class="GtkImage" id="image70">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="stock">gtk-apply</property>
</object>
<object class="GtkImage" id="image80">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="stock">gtk-add</property>
</object>
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-01 17:26:46 -05:00
<object class="GtkWindow" id="vmm-details">
<property name="can_focus">False</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<property name="title" translatable="yes">Virtual Machine</property>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05:00
<property name="default_width">800</property>
<property name="default_height">600</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-01 17:26:46 -05:00
<accel-groups>
<group name="accelgroup1"/>
</accel-groups>
<signal name="configure-event" handler="on_vmm_details_configure_event" swapped="no"/>
<signal name="delete-event" handler="on_vmm_details_delete_event" swapped="no"/>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05:00
<object class="GtkVBox" id="vbox2">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05:00
<object class="GtkMenuBar" id="details-menubar">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05:00
<object class="GtkMenuItem" id="file1">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<property name="label" translatable="yes">_File</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-01 17:26:46 -05:00
<child type="submenu">
<object class="GtkMenu" id="file1_menu">
<property name="can_focus">False</property>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05:00
<object class="GtkMenuItem" id="view_manager">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Add mnemonics for various menu items. Also, try to be a bit more consistent between manager and details menus.
2009-11-17 17:47:34 -05:00
<property name="label" translatable="yes">_View Manager</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<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-01 17:26:46 -05:00
<signal name="activate" handler="on_details_menu_view_manager_activate" swapped="no"/>
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
</child>
<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-01 17:26:46 -05:00
<object class="GtkSeparatorMenuItem" id="separator15">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
</child>
<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-01 17:26:46 -05:00
<object class="GtkImageMenuItem" id="close4">
Add security/selinux info to VM->Overview, allow changing if supported. Allows setting dynamic or static labelling.
2009-07-07 12:16:03 -04:00
<property name="label">gtk-close</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 10:45:44 -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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<property name="use_underline">True</property>
<property name="use_stock">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-01 17:26:46 -05:00
<property name="accel_group">accelgroup1</property>
<signal name="activate" handler="on_details_menu_close_activate" swapped="no"/>
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
</child>
<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-01 17:26:46 -05:00
<object class="GtkImageMenuItem" id="quit3">
Add security/selinux info to VM->Overview, allow changing if supported. Allows setting dynamic or static labelling.
2009-07-07 12:16:03 -04:00
<property name="label">gtk-quit</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 10:45:44 -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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<property name="use_underline">True</property>
<property name="use_stock">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-01 17:26:46 -05:00
<property name="accel_group">accelgroup1</property>
<signal name="activate" handler="on_details_menu_quit_activate" swapped="no"/>
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05:00
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05:00
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
</child>
<child>
details: Use VMActionMenu in top window menu
2013-09-22 15:44:58 -04:00
<object class="GtkMenuItem" id="details-vm-menu">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<property name="label" translatable="yes">Virtual _Machine</property>
<property name="use_underline">True</property>
details: Add auto USB redirection support in console viewer Add "Redirect USB device" option in console viewer. Initialize and embed UsbDeviceWidget object from SpiceClientGtk into a dialog to let user choose available USB devices for redirection. Throw an error message if USB connection failed. Auto-redirection is enable by default. There is race between creating usbredir channel and calling has_usb_redirection() when initializing spice session like happening on virt-viwer. So adding a new signal handler on_details_menu_virtual_manager_activate() to recheck the status of usbredir channel, set "Redirect USB device" option sensitive if it is availiable.
2013-07-01 14:33:59 -04:00
<signal name="activate" handler="on_details_menu_virtual_manager_activate" 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-01 17:26:46 -05:00
<child type="submenu">
<object class="GtkMenu" id="virtual_machine1_menu">
<property name="can_focus">False</property>
Add delete VM option in console viewer. (crobinso: Fix a minor pep8 warning)
2013-06-17 17:29:51 -03:00
<child>
<object class="GtkSeparatorMenuItem" id="separator2">
<property name="visible">True</property>
<property name="can_focus">False</property>
</object>
</child>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05:00
<object class="GtkMenuItem" id="details-menu-vm-screenshot">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<property name="label" translatable="yes">_Take Screenshot</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-01 17:26:46 -05:00
<signal name="activate" handler="on_details_menu_screenshot_activate" swapped="no"/>
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
</child>
details: Add auto USB redirection support in console viewer Add "Redirect USB device" option in console viewer. Initialize and embed UsbDeviceWidget object from SpiceClientGtk into a dialog to let user choose available USB devices for redirection. Throw an error message if USB connection failed. Auto-redirection is enable by default. There is race between creating usbredir channel and calling has_usb_redirection() when initializing spice session like happening on virt-viwer. So adding a new signal handler on_details_menu_virtual_manager_activate() to recheck the status of usbredir channel, set "Redirect USB device" option sensitive if it is availiable.
2013-07-01 14:33:59 -04:00
<child>
<object class="GtkMenuItem" id="details-menu-usb-redirection">
<property name="visible">True</property>
<property name="can_focus">False</property>
details: Simplify 'Redirect USB device' tooltip
2014-02-04 15:27:22 -05:00
<property name="tooltip_text" translatable="yes">Redirect host USB device to virtual machine with SPICE graphics.</property>
details: Add auto USB redirection support in console viewer Add "Redirect USB device" option in console viewer. Initialize and embed UsbDeviceWidget object from SpiceClientGtk into a dialog to let user choose available USB devices for redirection. Throw an error message if USB connection failed. Auto-redirection is enable by default. There is race between creating usbredir channel and calling has_usb_redirection() when initializing spice session like happening on virt-viwer. So adding a new signal handler on_details_menu_virtual_manager_activate() to recheck the status of usbredir channel, set "Redirect USB device" option sensitive if it is availiable.
2013-07-01 14:33:59 -04:00
<property name="label" translatable="yes">_Redirect USB device</property>
<property name="use_underline">True</property>
<signal name="activate" handler="on_details_menu_usb_redirection" swapped="no"/>
</object>
</child>
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-01 17:26:46 -05:00
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05:00
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
</child>
<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-01 17:26:46 -05:00
<object class="GtkMenuItem" id="view2">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<property name="label" translatable="yes">_View</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-01 17:26:46 -05:00
<child type="submenu">
<object class="GtkMenu" id="view2_menu">
<property name="can_focus">False</property>
details: List console vs. details choice in View menu This way, if the user hides the toolbar, the same functionality is still available.
2009-10-21 12:01:53 -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-01 17:26:46 -05:00
<object class="GtkRadioMenuItem" id="details-menu-view-console">
details: List console vs. details choice in View menu This way, if the user hides the toolbar, the same functionality is still available.
2009-10-21 12:01:53 -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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Add mnemonics for various menu items. Also, try to be a bit more consistent between manager and details menus.
2009-11-17 17:47:34 -05:00
<property name="label" translatable="yes">_Console</property>
details: List console vs. details choice in View menu This way, if the user hides the toolbar, the same functionality is still available.
2009-10-21 12:01:53 -04:00
<property name="use_underline">True</property>
<property name="active">True</property>
<property name="draw_as_radio">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-01 17:26:46 -05:00
<signal name="toggled" handler="on_details_menu_view_console_toggled" swapped="no"/>
</object>
details: List console vs. details choice in View menu This way, if the user hides the toolbar, the same functionality is still available.
2009-10-21 12:01:53 -04:00
</child>
<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-01 17:26:46 -05:00
<object class="GtkRadioMenuItem" id="details-menu-view-details">
details: List console vs. details choice in View menu This way, if the user hides the toolbar, the same functionality is still available.
2009-10-21 12:01:53 -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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Add mnemonics for various menu items. Also, try to be a bit more consistent between manager and details menus.
2009-11-17 17:47:34 -05:00
<property name="label" translatable="yes">_Details</property>
details: List console vs. details choice in View menu This way, if the user hides the toolbar, the same functionality is still available.
2009-10-21 12:01:53 -04:00
<property name="use_underline">True</property>
<property name="draw_as_radio">True</property>
<property name="group">details-menu-view-console</property>
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-01 17:26:46 -05:00
<signal name="toggled" handler="on_details_menu_view_details_toggled" swapped="no"/>
</object>
details: List console vs. details choice in View menu This way, if the user hides the toolbar, the same functionality is still available.
2009-10-21 12:01:53 -04:00
</child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<child>
<object class="GtkRadioMenuItem" id="details-menu-view-snapshots">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">Sna_pshots</property>
<property name="use_underline">True</property>
<property name="draw_as_radio">True</property>
<property name="group">details-menu-view-console</property>
<signal name="toggled" handler="on_details_menu_view_snapshots_toggled" swapped="no"/>
</object>
</child>
details: List console vs. details choice in View menu This way, if the user hides the toolbar, the same functionality is still available.
2009-10-21 12:01:53 -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-01 17:26:46 -05:00
<object class="GtkSeparatorMenuItem" id="menuitem2">
details: List console vs. details choice in View menu This way, if the user hides the toolbar, the same functionality is still available.
2009-10-21 12:01:53 -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-01 17:26:46 -05:00
<property name="can_focus">False</property>
</object>
details: List console vs. details choice in View menu This way, if the user hides the toolbar, the same functionality is still available.
2009-10-21 12:01:53 -04:00
</child>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05:00
<object class="GtkCheckMenuItem" id="details-menu-view-fullscreen">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Add mnemonics for various menu items. Also, try to be a bit more consistent between manager and details menus.
2009-11-17 17:47:34 -05:00
<property name="label" translatable="yes">_Fullscreen</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<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-01 17:26:46 -05:00
<signal name="activate" handler="on_details_menu_view_fullscreen_activate" swapped="no"/>
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
</child>
details: Remember previous window dimensions In order to do this, we can't auto resize the window to the VNC desktop resolution when details is brought up. So, to make this desired behavior easier, add a View menu item 'Resize to VM' which resizes the details window to match the active desktop dimensions.
2009-11-28 20:07:01 -05: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-01 17:26:46 -05:00
<object class="GtkMenuItem" id="detains-menu-view-size-to-vm">
details: Remember previous window dimensions In order to do this, we can't auto resize the window to the VNC desktop resolution when details is brought up. So, to make this desired behavior easier, add a View menu item 'Resize to VM' which resizes the details window to match the active desktop dimensions.
2009-11-28 20:07:01 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: Remember previous window dimensions In order to do this, we can't auto resize the window to the VNC desktop resolution when details is brought up. So, to make this desired behavior easier, add a View menu item 'Resize to VM' which resizes the details window to match the active desktop dimensions.
2009-11-28 20:07:01 -05:00
<property name="label" translatable="yes">_Resize to VM</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-01 17:26:46 -05:00
<signal name="activate" handler="on_details_menu_view_size_to_vm_activate" swapped="no"/>
</object>
details: Remember previous window dimensions In order to do this, we can't auto resize the window to the VNC desktop resolution when details is brought up. So, to make this desired behavior easier, add a View menu item 'Resize to VM' which resizes the details window to match the active desktop dimensions.
2009-11-28 20:07:01 -05:00
</child>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05:00
<object class="GtkMenuItem" id="menuitem1">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Add mnemonics for various menu items. Also, try to be a bit more consistent between manager and details menus.
2009-11-17 17:47:34 -05:00
<property name="label" translatable="yes">_Scale Display</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<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-01 17:26:46 -05:00
<child type="submenu">
<object class="GtkMenu" id="menu1">
Change VNC scaling options to 'Always', 'Fullscreen only', or 'Never'
2009-02-23 18:50:27 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Change VNC scaling options to 'Always', 'Fullscreen only', or 'Never'
2009-02-23 18:50:27 -05: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-01 17:26:46 -05:00
<object class="GtkRadioMenuItem" id="details-menu-view-scale-always">
Change VNC scaling options to 'Always', 'Fullscreen only', or 'Never'
2009-02-23 18:50:27 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Add mnemonics for various menu items. Also, try to be a bit more consistent between manager and details menus.
2009-11-17 17:47:34 -05:00
<property name="label" translatable="yes">_Always</property>
Change VNC scaling options to 'Always', 'Fullscreen only', or 'Never'
2009-02-23 18:50:27 -05:00
<property name="use_underline">True</property>
<property name="active">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-01 17:26:46 -05:00
<signal name="toggled" handler="on_details_menu_view_scale_always_toggled" swapped="no"/>
</object>
Change VNC scaling options to 'Always', 'Fullscreen only', or 'Never'
2009-02-23 18:50:27 -05:00
</child>
<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-01 17:26:46 -05:00
<object class="GtkRadioMenuItem" id="details-menu-view-scale-fullscreen">
Change VNC scaling options to 'Always', 'Fullscreen only', or 'Never'
2009-02-23 18:50:27 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Add mnemonics for various menu items. Also, try to be a bit more consistent between manager and details menus.
2009-11-17 17:47:34 -05:00
<property name="label" translatable="yes">_Only when Fullscreen</property>
Change VNC scaling options to 'Always', 'Fullscreen only', or 'Never'
2009-02-23 18:50:27 -05:00
<property name="use_underline">True</property>
<property name="draw_as_radio">True</property>
<property name="group">details-menu-view-scale-always</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-01 17:26:46 -05:00
<signal name="toggled" handler="on_details_menu_view_scale_fullscreen_toggled" swapped="no"/>
</object>
Change VNC scaling options to 'Always', 'Fullscreen only', or 'Never'
2009-02-23 18:50:27 -05:00
</child>
<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-01 17:26:46 -05:00
<object class="GtkRadioMenuItem" id="details-menu-view-scale-never">
Change VNC scaling options to 'Always', 'Fullscreen only', or 'Never'
2009-02-23 18:50:27 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Add mnemonics for various menu items. Also, try to be a bit more consistent between manager and details menus.
2009-11-17 17:47:34 -05:00
<property name="label" translatable="yes">_Never</property>
Change VNC scaling options to 'Always', 'Fullscreen only', or 'Never'
2009-02-23 18:50:27 -05:00
<property name="use_underline">True</property>
<property name="draw_as_radio">True</property>
<property name="group">details-menu-view-scale-always</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-01 17:26:46 -05:00
<signal name="toggled" handler="on_details_menu_view_scale_never_toggled" swapped="no"/>
</object>
Change VNC scaling options to 'Always', 'Fullscreen only', or 'Never'
2009-02-23 18:50:27 -05:00
</child>
console: Support spice 'resize-guest' (bz 754559) This will auto change the guest resolution to match the window size. Off by default, can be enabled like scaling preferences.
2014-01-31 09:13:53 -05:00
<child>
<object class="GtkSeparatorMenuItem" id="menuitem3">
<property name="visible">True</property>
<property name="can_focus">False</property>
</object>
</child>
<child>
<object class="GtkCheckMenuItem" id="details-menu-view-resizeguest">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">Auto _resize VM with window</property>
<property name="use_underline">True</property>
<signal name="toggled" handler="on_details_menu_view_resizeguest_toggled" swapped="no"/>
</object>
</child>
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-01 17:26:46 -05:00
</object>
Change VNC scaling options to 'Always', 'Fullscreen only', or 'Never'
2009-02-23 18:50:27 -05: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-01 17:26:46 -05:00
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
</child>
<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-01 17:26:46 -05:00
<object class="GtkMenuItem" id="details-menu-view-serial-list">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Add mnemonics for various menu items. Also, try to be a bit more consistent between manager and details menus.
2009-11-17 17:47:34 -05:00
<property name="label" translatable="yes">_Text Consoles</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<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-01 17:26:46 -05:00
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
</child>
<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-01 17:26:46 -05:00
<object class="GtkSeparatorMenuItem" id="separator7">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
</child>
<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-01 17:26:46 -05:00
<object class="GtkCheckMenuItem" id="details-menu-view-toolbar">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Add mnemonics for various menu items. Also, try to be a bit more consistent between manager and details menus.
2009-11-17 17:47:34 -05:00
<property name="label" translatable="yes">T_oolbar</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<property name="use_underline">True</property>
<property name="active">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-01 17:26:46 -05:00
<signal name="activate" handler="on_details_menu_view_toolbar_activate" swapped="no"/>
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05:00
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05:00
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
</child>
<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-01 17:26:46 -05:00
<object class="GtkMenuItem" id="details-menu-send-key">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Numerous UI tweaks. - Don't use custom button content, because it doesn't abide typical button gtk button + image preferences. This forces us to set the button image in the code since glade can't handle it. - Use widget mnemonics _everywhere_ - Tweak some default widget focus, and other misc things.
2009-11-17 15:06:15 -05:00
<property name="label" translatable="yes">Send _Key</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<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-01 17:26:46 -05:00
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05:00
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<packing>
<property name="expand">False</property>
<property name="fill">False</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 10:45:44 -04:00
<property name="position">0</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
</packing>
</child>
<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-01 17:26:46 -05:00
<object class="GtkHBox" id="toolbar-box">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05:00
<object class="GtkToolbar" id="details-toolbar">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -04:00
<property name="show_arrow">False</property>
<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-01 17:26:46 -05:00
<object class="GtkRadioToolButton" id="control-vm-console">
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -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-01 17:26:46 -05:00
<property name="can_focus">False</property>
<property name="tooltip_text" translatable="yes">Show the graphical console</property>
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -04:00
<property name="label" translatable="yes">Console</property>
<property name="icon_name">icon_console</property>
<property name="active">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-01 17:26:46 -05:00
<signal name="toggled" handler="on_control_vm_console_toggled" swapped="no"/>
</object>
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -04:00
<packing>
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 10:45:44 -04:00
<property name="expand">False</property>
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -04:00
<property name="homogeneous">True</property>
</packing>
</child>
<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-01 17:26:46 -05:00
<object class="GtkRadioToolButton" id="control-vm-details">
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -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-01 17:26:46 -05:00
<property name="can_focus">False</property>
<property name="tooltip_text" translatable="yes">Show virtual hardware details</property>
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -04:00
<property name="label" translatable="yes">Details</property>
<property name="stock_id">gtk-info</property>
<property name="group">control-vm-console</property>
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-01 17:26:46 -05:00
<signal name="toggled" handler="on_control_vm_details_toggled" swapped="no"/>
</object>
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -04:00
<packing>
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 10:45:44 -04:00
<property name="expand">False</property>
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -04:00
<property name="homogeneous">True</property>
</packing>
</child>
<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-01 17:26:46 -05:00
<object class="GtkSeparatorToolItem" id="toolbutton3">
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -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-01 17:26:46 -05:00
<property name="can_focus">False</property>
</object>
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -04:00
<packing>
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 10:45:44 -04:00
<property name="expand">False</property>
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -04:00
<property name="homogeneous">True</property>
</packing>
</child>
<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-01 17:26:46 -05:00
<object class="GtkToolButton" id="control-run">
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -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-01 17:26:46 -05:00
<property name="can_focus">False</property>
<property name="tooltip_text" translatable="yes">Power on the virtual machine</property>
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -04:00
<property name="label" translatable="yes">Run</property>
<property name="use_underline">True</property>
<property name="stock_id">gtk-media-play</property>
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-01 17:26:46 -05:00
<signal name="clicked" handler="on_control_run_clicked" swapped="no"/>
</object>
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -04:00
<packing>
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 10:45:44 -04:00
<property name="expand">False</property>
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -04:00
<property name="homogeneous">True</property>
</packing>
</child>
<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-01 17:26:46 -05:00
<object class="GtkToggleToolButton" id="control-pause">
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -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-01 17:26:46 -05:00
<property name="can_focus">False</property>
<property name="tooltip_text" translatable="yes">Pause the virtual machine</property>
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -04:00
<property name="label" translatable="yes">Pause</property>
<property name="use_underline">True</property>
<property name="stock_id">gtk-media-pause</property>
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-01 17:26:46 -05:00
<signal name="toggled" handler="on_control_pause_toggled" swapped="no"/>
</object>
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -04:00
<packing>
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 10:45:44 -04:00
<property name="expand">False</property>
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -04:00
<property name="homogeneous">True</property>
</packing>
</child>
<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-01 17:26:46 -05:00
<object class="GtkMenuToolButton" id="control-shutdown">
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -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-01 17:26:46 -05:00
<property name="can_focus">False</property>
<property name="tooltip_text" translatable="yes">Shutdown the virtual machine</property>
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -04:00
<property name="label" translatable="yes">Shut Down</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-01 17:26:46 -05:00
<signal name="clicked" handler="on_control_shutdown_clicked" swapped="no"/>
</object>
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 10:45:44 -04:00
<packing>
<property name="expand">False</property>
details: Couple mini 'panic' UI cleanups
2014-01-11 15:08:00 -05:00
<property name="homogeneous">False</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 10:45:44 -04:00
</packing>
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -04:00
</child>
create: Add an option to 'customize before install' This drops the user into a 'details' dialog where they can add, remove, or tweaks settings before starting the install.
2010-02-07 12:18:28 -05: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-01 17:26:46 -05:00
<object class="GtkSeparatorToolItem" id="toolbutton7">
create: Add an option to 'customize before install' This drops the user into a 'details' dialog where they can add, remove, or tweaks settings before starting the install.
2010-02-07 12:18:28 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
</object>
create: Add an option to 'customize before install' This drops the user into a 'details' dialog where they can add, remove, or tweaks settings before starting the install.
2010-02-07 12:18:28 -05:00
<packing>
<property name="expand">False</property>
<property name="homogeneous">True</property>
</packing>
</child>
details: Move snapshot switcher at end of toolbar This was the original suggested layout from way way back when the designers did mock ups.
2013-09-30 20:59:15 -04:00
<child>
<object class="GtkRadioToolButton" id="control-snapshots">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">Snapshots</property>
<property name="icon_name">vm_clone_wizard</property>
<property name="group">control-vm-console</property>
<signal name="toggled" handler="on_control_snapshots_toggled" swapped="no"/>
</object>
<packing>
<property name="expand">False</property>
<property name="homogeneous">True</property>
</packing>
</child>
create: Add an option to 'customize before install' This drops the user into a 'details' dialog where they can add, remove, or tweaks settings before starting the install.
2010-02-07 12:18:28 -05: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-01 17:26:46 -05:00
<object class="GtkToggleToolButton" id="control-fullscreen">
create: Add an option to 'customize before install' This drops the user into a 'details' dialog where they can add, remove, or tweaks settings before starting the install.
2010-02-07 12:18:28 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
<property name="tooltip_text" translatable="yes">Switch to fullscreen view</property>
details: Move snapshot switcher at end of toolbar This was the original suggested layout from way way back when the designers did mock ups.
2013-09-30 20:59:15 -04:00
<property name="halign">end</property>
create: Add an option to 'customize before install' This drops the user into a 'details' dialog where they can add, remove, or tweaks settings before starting the install.
2010-02-07 12:18:28 -05:00
<property name="stock_id">gtk-fullscreen</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-01 17:26:46 -05:00
<signal name="toggled" handler="on_control_fullscreen_toggled" swapped="no"/>
</object>
create: Add an option to 'customize before install' This drops the user into a 'details' dialog where they can add, remove, or tweaks settings before starting the install.
2010-02-07 12:18:28 -05:00
<packing>
details: Move snapshot switcher at end of toolbar This was the original suggested layout from way way back when the designers did mock ups.
2013-09-30 20:59:15 -04:00
<property name="expand">True</property>
create: Add an option to 'customize before install' This drops the user into a 'details' dialog where they can add, remove, or tweaks settings before starting the install.
2010-02-07 12:18:28 -05:00
<property name="homogeneous">True</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-01 17:26:46 -05:00
</object>
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 10:45:44 -04:00
<packing>
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-01 17:26:46 -05: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 10:45:44 -04:00
<property name="position">0</property>
</packing>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
</child>
<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-01 17:26:46 -05:00
<object class="GtkToolbar" id="customize-toolbar">
<property name="can_focus">False</property>
details: 'Customize' toolbar cleanups Add a tooltip, make sure button text is always shown.
2010-08-24 16:31:55 -04:00
<property name="toolbar_style">both-horiz</property>
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -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-01 17:26:46 -05:00
<object class="GtkToolButton" id="details-finish-customize">
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -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-01 17:26:46 -05:00
<property name="can_focus">False</property>
<property name="tooltip_text" translatable="yes">Begin Installation</property>
details: 'Customize' toolbar cleanups Add a tooltip, make sure button text is always shown.
2010-08-24 16:31:55 -04:00
<property name="is_important">True</property>
<property name="label" translatable="yes">_Begin Installation</property>
create: Add an option to 'customize before install' This drops the user into a 'details' dialog where they can add, remove, or tweaks settings before starting the install.
2010-02-07 12:18:28 -05:00
<property name="use_underline">True</property>
<property name="stock_id">gtk-apply</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-01 17:26:46 -05:00
<signal name="clicked" handler="on_details_customize_finish_clicked" swapped="no"/>
</object>
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -04:00
<packing>
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 10:45:44 -04:00
<property name="expand">False</property>
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -04:00
<property name="homogeneous">True</property>
</packing>
</child>
create: Allow cancelling 'customize' dialog Selecting the 'cancel' option or hitting the window X will erase any customized changes and go back to the final screen of the wizard.
2011-07-18 21:31:06 -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-01 17:26:46 -05:00
<object class="GtkToolButton" id="details-cancel-customize">
create: Allow cancelling 'customize' dialog Selecting the 'cancel' option or hitting the window X will erase any customized changes and go back to the final screen of the wizard.
2011-07-18 21:31:06 -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-01 17:26:46 -05:00
<property name="can_focus">False</property>
create: Allow cancelling 'customize' dialog Selecting the 'cancel' option or hitting the window X will erase any customized changes and go back to the final screen of the wizard.
2011-07-18 21:31:06 -04:00
<property name="is_important">True</property>
<property name="label" translatable="yes">_Cancel</property>
<property name="use_underline">True</property>
<property name="stock_id">gtk-cancel</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-01 17:26:46 -05:00
<signal name="clicked" handler="on_details_cancel_customize_clicked" swapped="no"/>
</object>
create: Allow cancelling 'customize' dialog Selecting the 'cancel' option or hitting the window X will erase any customized changes and go back to the final screen of the wizard.
2011-07-18 21:31:06 -04:00
<packing>
<property name="expand">False</property>
<property name="homogeneous">True</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-01 17:26:46 -05:00
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<packing>
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-01 17:26:46 -05:00
<property name="expand">True</property>
<property name="fill">True</property>
details: Remove console/details tabs, use toolbar buttons instead. Serial consoles are part of the main console tab, which can be chosen from 'View->Consoles'.
2009-07-28 09:40:43 -04:00
<property name="position">1</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04: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-01 17:26:46 -05:00
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<packing>
<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-01 17:26:46 -05:00
<property name="fill">True</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<property name="position">1</property>
</packing>
</child>
<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-01 17:26:46 -05:00
<object class="GtkNotebook" id="details-pages">
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="show_border">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-01 17:26:46 -05:00
<signal name="switch-page" handler="on_details_pages_switch_page" after="yes" swapped="no"/>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05:00
<object class="GtkHBox" id="hbox1">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
console: Remove 6 pixel border around VNC widget
2009-11-01 21:39:48 -05:00
<property name="border_width">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 14:35:36 -04:00
<property name="spacing">12</property>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05:00
<object class="GtkVBox" id="vbox53">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05:00
<property name="can_focus">False</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 14:35:36 -04:00
<property name="spacing">6</property>
<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-01 17:26:46 -05:00
<object class="GtkScrolledWindow" id="scrolledwindow5">
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 14:35:36 -04:00
<property name="visible">True</property>
<property name="can_focus">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 10:45:44 -04:00
<property name="hscrollbar_policy">never</property>
<property name="shadow_type">in</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 14: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-01 17:26:46 -05:00
<object class="GtkTreeView" id="hw-list">
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 14:35:36 -04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="headers_visible">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-01 17:26:46 -05:00
<signal name="button-press-event" handler="on_hw_list_button_press_event" swapped="no"/>
<child internal-child="selection">
Set list selection signals in glade, not code
2013-09-22 16:29:58 -04:00
<object class="GtkTreeSelection" id="treeview-selection1">
<signal name="changed" handler="on_hw_list_changed" swapped="no"/>
</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-01 17:26:46 -05:00
</child>
</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 14: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-01 17:26:46 -05:00
</object>
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 10:45:44 -04:00
<packing>
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-01 17:26:46 -05: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 10:45:44 -04:00
<property name="position">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 14:35:36 -04:00
</child>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05:00
<object class="GtkButton" id="add-hardware-button">
Numerous UI tweaks. - Don't use custom button content, because it doesn't abide typical button gtk button + image preferences. This forces us to set the button image in the code since glade can't handle it. - Use widget mnemonics _everywhere_ - Tweak some default widget focus, and other misc things.
2009-11-17 15:06:15 -05:00
<property name="label" translatable="yes">A_dd Hardware</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<property name="visible">True</property>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05:00
<property name="can_focus">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 10:45:44 -04:00
<property name="receives_default">False</property>
ui: Set non-stock button images in glade, not explicitly in code
2013-09-22 12:18:49 -04:00
<property name="image">image80</property>
Numerous UI tweaks. - Don't use custom button content, because it doesn't abide typical button gtk button + image preferences. This forces us to set the button image in the code since glade can't handle it. - Use widget mnemonics _everywhere_ - Tweak some default widget focus, and other misc things.
2009-11-17 15:06:15 -05:00
<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-01 17:26:46 -05:00
<signal name="clicked" handler="on_add_hardware_button_clicked" swapped="no"/>
</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 14:35:36 -04:00
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">1</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-01 17:26:46 -05: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 14:35:36 -04:00
<packing>
<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-01 17:26:46 -05:00
<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 10:45:44 -04: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 14:35:36 -04:00
</packing>
</child>
<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-01 17:26:46 -05:00
<object class="GtkVBox" id="vbox1">
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 14: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-01 17:26:46 -05:00
<property name="can_focus">False</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 14:35:36 -04:00
<property name="spacing">6</property>
<child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<object class="GtkNotebook" id="hw-panel">
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 14:35:36 -04:00
<property name="visible">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="can_focus">True</property>
<property name="show_border">False</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<child>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<object class="GtkVBox" id="vbox6">
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<property name="visible">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="can_focus">False</property>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="spacing">12</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<child>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<object class="GtkFrame" id="frame2">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<child>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<object class="GtkAlignment" id="alignment9">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<child>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<object class="GtkGrid" id="table5">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="border_width">3</property>
<property name="row_spacing">6</property>
<property name="column_spacing">6</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<child>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<object class="GtkLabel" id="label44">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="xalign">0</property>
<property name="label" translatable="yes">Status:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label68">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label" translatable="yes">UUID:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label43">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</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>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="overview-uuid">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</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>
<property name="width">1</property>
<property name="height">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>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="title-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label" translatable="yes">Title:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">3</property>
<property name="width">1</property>
<property name="height">1</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>
<property name="width">1</property>
<property name="height">1</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>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<child>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<object class="GtkLabel" id="overview-status-text">
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="label" translatable="yes">Shut down</property>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
</object>
<packing>
<property name="left_attach">1</property>
details: Fix status icon shrinking on state change. No idea why this is happening or what is causing it, but forcing the icon width fixes things...
2014-01-12 14:25:09 -05:00
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">1</property>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
</packing>
</child>
<child>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<object class="GtkImage" id="overview-status-icon">
<property name="width_request">22</property>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<property name="visible">True</property>
details: Fix status icon shrinking on state change. No idea why this is happening or what is causing it, but forcing the icon width fixes things...
2014-01-12 14:25:09 -05:00
<property name="can_focus">False</property>
<property name="xalign">0</property>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="stock">gtk-missing-image</property>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
</object>
<packing>
details: Fix status icon shrinking on state change. No idea why this is happening or what is causing it, but forcing the icon width fixes things...
2014-01-12 14:25:09 -05:00
<property name="left_attach">0</property>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="top_attach">0</property>
details: Fix status icon shrinking on state change. No idea why this is happening or what is causing it, but forcing the icon width fixes things...
2014-01-12 14:25:09 -05:00
<property name="width">1</property>
<property name="height">1</property>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01: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 19:53:57 +01:00
</child>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">2</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label24">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="yalign">0</property>
<property name="label" translatable="yes">Description:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">4</property>
<property name="width">1</property>
<property name="height">1</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>
virt-manager: add UI elements for domain title in the details window Commit b79ba8382e2205c416d7c4836ac9ee08c72e2c56 in libvirt adds a <title> attribute to the domain XML, that is used by the user to identify more easily the VM. This feature is not supported by all HVs. This patch allows to see and modify the title from the details window. Something similar was requested here: https://bugzilla.redhat.com/show_bug.cgi?id=798949 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-24 13:02:27 +02:00
<child>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<object class="GtkTextView" id="overview-description">
virt-manager: add UI elements for domain title in the details window Commit b79ba8382e2205c416d7c4836ac9ee08c72e2c56 in libvirt adds a <title> attribute to the domain XML, that is used by the user to identify more easily the VM. This feature is not supported by all HVs. This patch allows to see and modify the title from the details window. Something similar was requested here: https://bugzilla.redhat.com/show_bug.cgi?id=798949 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-24 13:02:27 +02:00
<property name="visible">True</property>
<property name="can_focus">True</property>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="hexpand">True</property>
<property name="wrap_mode">word</property>
virt-manager: add UI elements for domain title in the details window Commit b79ba8382e2205c416d7c4836ac9ee08c72e2c56 in libvirt adds a <title> attribute to the domain XML, that is used by the user to identify more easily the VM. This feature is not supported by all HVs. This patch allows to see and modify the title from the details window. Something similar was requested here: https://bugzilla.redhat.com/show_bug.cgi?id=798949 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-24 13:02:27 +02:00
</object>
</child>
</object>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">4</property>
<property name="width">1</property>
<property name="height">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 19:53:57 +01: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-01 17:26:46 -05:00
</object>
Add basic operating system inspection data to the VMM details page. This adds hostname, product name, and list of applications.
2011-07-18 19:53:57 +01: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-01 17:26:46 -05:00
</object>
Add basic operating system inspection data to the VMM details page. This adds hostname, product name, and list of applications.
2011-07-18 19:53:57 +01:00
</child>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05: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>
</object>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkFrame" id="frame7">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
List HV, Arch, Emulator in VM->Details->Overview
2009-05-12 13:09:08 -04:00
<child>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<object class="GtkAlignment" id="alignment6">
List HV, Arch, Emulator in VM->Details->Overview
2009-05-12 13:09:08 -04:00
<property name="visible">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="can_focus">False</property>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
List HV, Arch, Emulator in VM->Details->Overview
2009-05-12 13:09:08 -04:00
<child>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<object class="GtkGrid" id="table1">
List HV, Arch, Emulator in VM->Details->Overview
2009-05-12 13:09:08 -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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05: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="xalign">1</property>
<property name="label" translatable="yes">Hypervisor:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label12">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Architecture:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="overview-hv">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</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>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="overview-arch">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</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>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="overview-emulator">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label">foo</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">2</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label13">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Emulator:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="overview-machine-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</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>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
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 14:35:36 -04:00
<child>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<object class="GtkComboBox" id="machine-type">
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 14: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<signal name="changed" handler="on_machine_type_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 10:18:47 -04:00
</object>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">3</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
Make properties in the details dialog selectable
2009-02-28 17:28:00 -05: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-01 17:26:46 -05:00
</object>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05:00
</object>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05:00
</child>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<child type="label">
<object class="GtkLabel" id="frame">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&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>
</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="box12">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="valign">start</property>
<property name="orientation">vertical</property>
<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>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05:00
<child>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<object class="GtkFrame" id="details-inspection-os">
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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 10:18:47 -04:00
<property name="can_focus">False</property>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<child>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<object class="GtkAlignment" id="alignment43">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01: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 10:18:47 -04:00
<child>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<object class="GtkTable" 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 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<property name="border_width">3</property>
<property name="n_rows">2</property>
<property name="n_columns">2</property>
<property name="column_spacing">6</property>
<property name="row_spacing">6</property>
<child>
<object class="GtkLabel" id="label71">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Hostname:</property>
</object>
<packing>
<property name="x_options">GTK_FILL</property>
<property name="y_options">GTK_FILL</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label72">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Product name:</property>
</object>
<packing>
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options">GTK_FILL</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="inspection-hostname">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label">foo</property>
<property name="selectable">True</property>
</object>
<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>
</child>
<child>
<object class="GtkLabel" id="inspection-product-name">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label">foo</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options">GTK_FILL</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 10:18:47 -04:00
</object>
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 10:45:44 -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-01 17:26:46 -05:00
</object>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
</child>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<child type="label">
<object class="GtkLabel" id="label70">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;Operating System&lt;/b&gt;</property>
<property name="use_markup">True</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-01 17:26:46 -05:00
</object>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">0</property>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01: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 10:18:47 -04:00
</child>
<child>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<object class="GtkExpander" id="details-inspection-apps">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<property name="can_focus">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<child>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<object class="GtkAlignment" id="alignment44">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">21</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<child>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<object class="GtkScrolledWindow" id="scrolledwindow6">
<property name="height_request">150</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<property name="shadow_type">etched-in</property>
<child>
<object class="GtkTreeView" id="inspection-apps">
<property name="visible">True</property>
<property name="can_focus">True</property>
<child internal-child="selection">
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<object class="GtkTreeSelection" id="treeview-selection"/>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
</child>
</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 10:18:47 -04:00
</child>
</object>
</child>
</object>
</child>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<child type="label">
<object class="GtkLabel" id="label73">
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<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>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">1</property>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
</packing>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkGrid" id="details-overview-error-box">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="valign">end</property>
<property name="orientation">vertical</property>
<property name="column_spacing">6</property>
<child>
<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 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<property name="halign">start</property>
<property name="yalign">0</property>
<property name="stock">gtk-dialog-warning</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="details-overview-error">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="xalign">0</property>
<property name="yalign">0</property>
<property name="label" translatable="yes">Error message bar</property>
<property name="max_width_chars">80</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</child>
</object>
<packing>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<property name="expand">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="fill">True</property>
details: show warning when guest inspection fails If libguestfs fails to inspect the guest then show a warning. Now the "Operating System" and "Applications" frames are visible only when the guest inspection is available. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=755869 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-11-25 16:10:03 +01:00
<property name="position">1</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
</object>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<packing>
<property name="position">1</property>
<property name="tab_fill">False</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 10:18:47 -04:00
</child>
<child type="tab">
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<object class="GtkLabel" id="label14">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="label">inspect</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">1</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
<object class="GtkBox" id="box2">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
<property name="orientation">vertical</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<child>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
<object class="GtkVBox" id="vbox5">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
<property name="spacing">12</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-16 16:05:55 -05:00
<child>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
<object class="GtkFrame" id="frame24">
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-16 16:05:55 -05: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 10:18:47 -04:00
<property name="can_focus">False</property>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</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-16 16:05:55 -05:00
<child>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
<object class="GtkAlignment" id="alignment50">
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-16 16:05:55 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
<property name="left_padding">12</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<child>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
<object class="GtkBox" id="box7">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
<property name="orientation">vertical</property>
<property name="spacing">3</property>
<child>
<object class="GtkAlignment" id="overview-cpu-usage-align">
<property name="height_request">75</property>
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<placeholder/>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="overview-cpu-usage-text">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label">18%</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
</child>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label45">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;CPU usage&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="frame3">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<child>
<object class="GtkAlignment" id="alignment4">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="left_padding">12</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<child>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
<object class="GtkBox" id="box6">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
<property name="orientation">vertical</property>
<property name="spacing">3</property>
<child>
<object class="GtkAlignment" id="overview-memory-usage-align">
<property name="height_request">75</property>
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<placeholder/>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="overview-memory-usage-text">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label">30 MB of 128 MB</property>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
</child>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label51">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;Memory usage&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">1</property>
</packing>
</child>
<child>
<object class="GtkFrame" id="frame22">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<child>
<object class="GtkAlignment" id="alignment48">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="left_padding">12</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<child>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
<object class="GtkBox" id="box5">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
<property name="orientation">vertical</property>
<property name="spacing">3</property>
<child>
<object class="GtkAlignment" id="overview-disk-usage-align">
<property name="height_request">75</property>
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<placeholder/>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="overview-disk-usage-text">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">0 KBytes/s 0 KBytes/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>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
</child>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label91">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&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>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<child>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
<object class="GtkBox" id="box8">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
<property name="orientation">vertical</property>
<property name="spacing">3</property>
<child>
<object class="GtkAlignment" id="overview-network-traffic-align">
<property name="height_request">75</property>
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<placeholder/>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="overview-network-traffic-text">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label">0 KBytes/s 0 KBytes/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>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
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-16 16:05:55 -05: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-01 17:26:46 -05:00
</object>
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-16 16:05:55 -05:00
</child>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
<child type="label">
<object class="GtkLabel" id="label92">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;Network I/O&lt;/b&gt;</property>
<property name="use_markup">True</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-01 17:26:46 -05:00
</object>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">3</property>
</packing>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</child>
</object>
<packing>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
<property name="expand">False</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">2</property>
Fix host/details graphs to not over expand
2013-09-27 14:17:57 -04:00
<property name="tab_fill">False</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label7">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">stat</property>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">2</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkVBox" id="vbox14">
<property name="visible">True</property>
<property name="can_focus">False</property>
details: Remove runtime vcpu pinning list I don't think anyone depended on this, and it's overkill for virt-manager.
2014-01-26 14:14:44 -05:00
<property name="valign">start</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="spacing">12</property>
<child>
<object class="GtkFrame" id="CPUs">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
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-16 16:05:55 -05: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 10:18:47 -04:00
<object class="GtkAlignment" id="alignment11">
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-16 16:05:55 -05: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 10:18:47 -04:00
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">12</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-16 16:05:55 -05: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 10:18:47 -04:00
<object class="GtkHBox" id="hbox5">
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-16 16:05:55 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="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-16 16:05:55 -05: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 10:18:47 -04:00
<object class="GtkTable" id="table30">
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-16 16:05:55 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="border_width">3</property>
<property name="n_rows">3</property>
<property name="n_columns">2</property>
<property name="column_spacing">12</property>
<property name="row_spacing">6</property>
<child>
<object class="GtkLabel" id="state-host-cpus">
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-16 16:05:55 -05: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 10:18:47 -04:00
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label">8</property>
<property name="selectable">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-01 17:26:46 -05:00
</object>
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-16 16:05:55 -05: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 10:18:47 -04:00
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
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-16 16:05:55 -05:00
</packing>
</child>
<child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<object class="GtkLabel" id="label334">
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-16 16:05:55 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="xalign">1</property>
<property name="label" translatable="yes">Logical host CPUs:</property>
</object>
<packing>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkLabel" id="label335">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Maximum allocation:</property>
</object>
<packing>
<property name="top_attach">2</property>
<property name="bottom_attach">3</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkLabel" id="label333">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Current a_llocation:</property>
<property name="use_underline">True</property>
</object>
<packing>
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkSpinButton" id="config-maxvcpus">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
<property name="adjustment">adjustment6</property>
<signal name="changed" handler="on_config_maxvcpus_changed" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="top_attach">2</property>
<property name="bottom_attach">3</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options">GTK_FILL</property>
</packing>
</child>
<child>
<object class="GtkSpinButton" id="config-vcpus">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
<property name="adjustment">adjustment7</property>
<property name="climb_rate">1</property>
<property name="numeric">True</property>
<property name="update_policy">if-valid</property>
details: Remove UI for security, apic, acpi, clock 99% of users never need to tweak them, and now that we have virt-xml, most of what they could want to do is a simple CLI oneliner.
2014-01-26 13:43:53 -05:00
<signal name="changed" handler="on_config_vcpus_changed" swapped="no"/>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<child internal-child="accessible">
<object class="AtkObject" id="config-vcpus-atkobject">
<property name="AtkObject::accessible-name" translatable="yes">Virtual CPU Select</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-01 17:26:46 -05:00
</object>
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-16 16:05:55 -05: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 10:18:47 -04:00
</object>
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkHBox" id="config-vcpus-warn-box">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">6</property>
<child>
<object class="GtkImage" id="image9">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="stock">gtk-dialog-warning</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-01 17:26:46 -05:00
</object>
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-16 16:05:55 -05:00
<packing>
Fix up a ton of UI regressions from gtk3 conversion
2013-01-12 16:13:53 -05:00
<property name="expand">False</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="fill">False</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label28">
<property name="width_request">300</property>
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label" translatable="yes">&lt;small&gt;Overcommitting vCPUs can hurt performance&lt;/small&gt;</property>
<property name="use_markup">True</property>
<property name="wrap">True</property>
<property name="max_width_chars">32</property>
</object>
<packing>
<property name="expand">True</property>
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-01 17:26:46 -05:00
<property name="fill">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-16 16:05:55 -05:00
<property name="position">1</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-01 17:26:46 -05: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 10:18:47 -04:00
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">1</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-16 16:05:55 -05: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-01 17:26:46 -05:00
</object>
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-16 16:05:55 -05: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-01 17:26:46 -05:00
</object>
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-16 16:05:55 -05: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 10:18:47 -04:00
<child type="label">
<object class="GtkLabel" id="label100">
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<property name="visible">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<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="GtkExpander" id="expander5">
<property name="visible">True</property>
<property name="can_focus">True</property>
<child>
<object class="GtkAlignment" id="alignment31">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="left_padding">21</property>
<property name="right_padding">12</property>
<child>
details: Reword the CPU model UI a bit more - Add options in the model drop down for clear, hvdefault, and app default - Make 'copy host' a check box, when enabled it hides the model dropdown - Detect if the VM CPU is a copy of the host CPU - Undocumented bit that allows passing in host-model/host-passthrough to the model field for people that really want those settings.
2014-01-31 13:40:09 -05:00
<object class="GtkGrid" id="table15">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: Reword the CPU model UI a bit more - Add options in the model drop down for clear, hvdefault, and app default - Make 'copy host' a check box, when enabled it hides the model dropdown - Detect if the VM CPU is a copy of the host CPU - Undocumented bit that allows passing in host-model/host-passthrough to the model field for people that really want those settings.
2014-01-31 13:40:09 -05:00
<property name="halign">start</property>
<property name="valign">start</property>
<property name="row_spacing">3</property>
<property name="column_spacing">12</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<child>
details: Reword the CPU model UI a bit more - Add options in the model drop down for clear, hvdefault, and app default - Make 'copy host' a check box, when enabled it hides the model dropdown - Detect if the VM CPU is a copy of the host CPU - Undocumented bit that allows passing in host-model/host-passthrough to the model field for people that really want those settings.
2014-01-31 13:40:09 -05:00
<object class="GtkLabel" id="label52">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: Reword the CPU model UI a bit more - Add options in the model drop down for clear, hvdefault, and app default - Make 'copy host' a check box, when enabled it hides the model dropdown - Detect if the VM CPU is a copy of the host CPU - Undocumented bit that allows passing in host-model/host-passthrough to the model field for people that really want those settings.
2014-01-31 13:40:09 -05:00
<property name="xalign">0</property>
<property name="label" translatable="yes">Model:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkCheckButton" id="cpu-copy-host">
<property name="label" translatable="yes">Copy host CPU configuration</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
<property name="xalign">0</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>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkComboBox" id="cpu-model">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="has_entry">True</property>
<signal name="changed" handler="on_cpu_model_changed" swapped="no"/>
<child internal-child="entry">
<object class="GtkEntry" id="combobox-entry33">
<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 10:18:47 -04:00
</object>
</child>
</object>
<packing>
details: Reword the CPU model UI a bit more - Add options in the model drop down for clear, hvdefault, and app default - Make 'copy host' a check box, when enabled it hides the model dropdown - Detect if the VM CPU is a copy of the host CPU - Undocumented bit that allows passing in host-model/host-passthrough to the model field for people that really want those settings.
2014-01-31 13:40:09 -05:00
<property name="left_attach">1</property>
<property name="top_attach">1</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
</object>
</child>
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label49">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;Configuration&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>
details: enforce relationship between cpu topology and maxvcpus (bz 708892)
2014-02-01 09:14:55 -05:00
<object class="GtkExpander" id="cpu-topology-expander">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<child>
<object class="GtkAlignment" id="alignment39">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="left_padding">23</property>
<property name="right_padding">12</property>
<child>
<object class="GtkVBox" id="vbox15">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">4</property>
<child>
<object class="GtkCheckButton" id="cpu-topology-enable">
<property name="label" translatable="yes">Manually set CPU topology</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
<property name="xalign">0.5</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>
<child>
<object class="GtkHBox" id="hbox26">
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<object class="GtkTable" id="cpu-topology-table">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="n_rows">3</property>
<property name="n_columns">2</property>
<property name="column_spacing">12</property>
<property name="row_spacing">4</property>
<child>
<object class="GtkLabel" id="label59">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label" translatable="yes">Threads:</property>
</object>
<packing>
<property name="top_attach">2</property>
<property name="bottom_attach">3</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options">GTK_FILL</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label58">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label" translatable="yes">Cores:</property>
</object>
<packing>
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options">GTK_FILL</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label57">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label" translatable="yes">Sockets:</property>
</object>
details: Multiple boot device support Allows viewing, adding, removing, and reordering the boot device list.
2010-02-24 20:37:41 -05:00
<packing>
<property name="x_options">GTK_FILL</property>
<property name="y_options">GTK_FILL</property>
</packing>
</child>
<child>
details: enforce relationship between cpu topology and maxvcpus (bz 708892)
2014-02-01 09:14:55 -05:00
<object class="GtkSpinButton" id="cpu-sockets">
details: Multiple boot device support Allows viewing, adding, removing, and reordering the boot device list.
2010-02-24 20:37:41 -05:00
<property name="visible">True</property>
details: enforce relationship between cpu topology and maxvcpus (bz 708892)
2014-02-01 09:14:55 -05:00
<property name="can_focus">True</property>
<property name="halign">start</property>
<property name="hexpand">False</property>
<property name="invisible_char">●</property>
<property name="adjustment">adjustment3</property>
<signal name="changed" handler="on_cpu_sockets_changed" swapped="no"/>
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-01 17:26:46 -05:00
</object>
details: Multiple boot device support Allows viewing, adding, removing, and reordering the boot device list.
2010-02-24 20:37:41 -05:00
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
</packing>
</child>
<child>
details: enforce relationship between cpu topology and maxvcpus (bz 708892)
2014-02-01 09:14:55 -05:00
<object class="GtkSpinButton" id="cpu-cores">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<property name="visible">True</property>
details: enforce relationship between cpu topology and maxvcpus (bz 708892)
2014-02-01 09:14:55 -05:00
<property name="can_focus">True</property>
<property name="halign">start</property>
<property name="hexpand">False</property>
<property name="invisible_char">●</property>
<property name="adjustment">adjustment4</property>
<signal name="changed" handler="on_cpu_cores_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-01 17:26:46 -05:00
</object>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
</packing>
</child>
<child>
details: enforce relationship between cpu topology and maxvcpus (bz 708892)
2014-02-01 09:14:55 -05:00
<object class="GtkSpinButton" id="cpu-threads">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
details: enforce relationship between cpu topology and maxvcpus (bz 708892)
2014-02-01 09:14:55 -05:00
<property name="can_focus">True</property>
<property name="halign">start</property>
<property name="invisible_char">●</property>
<property name="adjustment">adjustment5</property>
<signal name="changed" handler="on_cpu_threads_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 10:18:47 -04:00
</object>
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
details: enforce relationship between cpu topology and maxvcpus (bz 708892)
2014-02-01 09:14:55 -05:00
<property name="top_attach">2</property>
<property name="bottom_attach">3</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
</packing>
details: Multiple boot device support Allows viewing, adding, removing, and reordering the boot device list.
2010-02-24 20:37:41 -05: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-01 17:26:46 -05:00
</object>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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 10:18:47 -04: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-01 17:26:46 -05:00
<property name="fill">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="position">0</property>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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-01 17:26:46 -05:00
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05: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 10:18:47 -04:00
</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;Topology&lt;/b&gt;</property>
<property name="use_markup">True</property>
</object>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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-01 17:26:46 -05:00
</object>
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 10:45:44 -04:00
<packing>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="expand">False</property>
<property name="fill">True</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<property name="position">2</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 10:45:44 -04:00
</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 14:35:36 -04:00
</child>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
<object class="GtkExpander" id="expander3">
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 14:35:36 -04:00
<property name="visible">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="can_focus">True</property>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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 10:18:47 -04:00
<object class="GtkAlignment" id="alignment16">
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="bottom_padding">12</property>
<property name="left_padding">21</property>
<property name="right_padding">12</property>
Save glade files with glade-3
2008-10-31 10:18:55 -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 10:18:47 -04:00
<object class="GtkVBox" id="vbox10">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="spacing">12</property>
Support viewing and removing VM 'video' devices.
2009-07-09 14:35:55 -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 10:18:47 -04:00
<object class="GtkTable" id="table9">
Support viewing and removing VM 'video' devices.
2009-07-09 14: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="n_rows">2</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<property name="n_columns">2</property>
<property name="column_spacing">6</property>
<property name="row_spacing">6</property>
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05: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 10:18:47 -04:00
<object class="GtkLabel" id="label336">
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05:00
<property name="xalign">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 10:18:47 -04:00
<property name="label" translatable="yes">Default _pinning:</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<property name="use_underline">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="mnemonic_widget">config-vcpupin</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-01 17:26:46 -05:00
</object>
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05:00
<packing>
<property name="x_options">GTK_FILL</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="y_options">GTK_FILL</property>
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05:00
</packing>
</child>
<child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<object class="GtkAlignment" id="alignment24">
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: Remove runtime vcpu pinning list I don't think anyone depended on this, and it's overkill for virt-manager.
2014-01-26 14:14:44 -05:00
<property name="hexpand">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 10:18:47 -04:00
<child>
<placeholder/>
</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-01 17:26:46 -05:00
</object>
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05: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 10:18:47 -04:00
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05:00
<property name="x_options">GTK_FILL</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="y_options">GTK_FILL</property>
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05:00
</packing>
</child>
<child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<object class="GtkHBox" id="hbox16">
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="spacing">6</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
<object class="GtkEntry" id="config-vcpupin">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
details: Remove UI for security, apic, acpi, clock 99% of users never need to tweak them, and now that we have virt-xml, most of what they could want to do is a simple CLI oneliner.
2014-01-26 13:43:53 -05:00
<signal name="changed" handler="on_config_vcpupin_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-01 17:26:46 -05:00
<child internal-child="accessible">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<object class="AtkObject" id="config-vcpupin-atkobject">
<property name="AtkObject::accessible-name" translatable="yes">Virtual CPU Affinity Select</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-01 17:26:46 -05:00
</object>
</child>
</object>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<packing>
Fix up a ton of UI regressions from gtk3 conversion
2013-01-12 16:13:53 -05: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-01 17:26:46 -05:00
<property name="fill">True</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<property name="position">0</property>
</packing>
</child>
<child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<object class="GtkLabel" id="label23">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="label">&lt;span size='small'&gt;(ex: 0,1,3-5,7)&lt;/span&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-01 17:26:46 -05:00
</object>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
<property name="expand">False</property>
Fix up a ton of UI regressions from gtk3 conversion
2013-01-12 16:13:53 -05:00
<property name="fill">True</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<property name="position">1</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-01 17:26:46 -05:00
</object>
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05:00
<packing>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<property name="left_attach">1</property>
<property name="right_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 10:18:47 -04:00
<property name="x_options">GTK_FILL</property>
<property name="y_options">GTK_FILL</property>
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05:00
</packing>
</child>
<child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<object class="GtkHBox" id="hbox9">
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<property name="spacing">3</property>
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05: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 10:18:47 -04:00
<object class="GtkButton" id="config-vcpupin-generate">
<property name="label" translatable="yes">Generate from host _NUMA configuration</property>
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05:00
<property name="visible">True</property>
<property name="can_focus">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="receives_default">True</property>
<property name="use_underline">True</property>
<signal name="clicked" handler="on_config_vcpupin_generate_clicked" 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-01 17:26:46 -05:00
</object>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<packing>
Fix up a ton of UI regressions from gtk3 conversion
2013-01-12 16:13:53 -05: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-01 17:26:46 -05:00
<property name="fill">True</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<property name="position">0</property>
</packing>
</child>
<child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<object class="GtkAlignment" id="alignment25">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<child>
<object class="GtkImage" id="config-vcpupin-generate-err">
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="stock">gtk-dialog-warning</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-01 17:26:46 -05:00
</object>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<packing>
Fix up a ton of UI regressions from gtk3 conversion
2013-01-12 16:13:53 -05:00
<property name="expand">True</property>
<property name="fill">True</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<property name="position">1</property>
</packing>
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05: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-01 17:26:46 -05:00
</object>
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05:00
<packing>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<property name="left_attach">1</property>
<property name="right_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 10:18:47 -04:00
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05:00
<property name="x_options">GTK_FILL</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="y_options">GTK_FILL</property>
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkVBox" id="vbox11">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">6</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-11 16:40:24 -05: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-01 17:26:46 -05:00
</object>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
</child>
<child type="label">
<object class="GtkLabel" id="label9">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;Pinning&lt;/b&gt;</property>
<property name="use_markup">True</property>
</object>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05:00
</object>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
<property name="expand">False</property>
<property name="fill">True</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<property name="position">3</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 10:18:47 -04:00
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">3</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label53">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">cpu</property>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">3</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkVBox" id="vbox7">
<property name="visible">True</property>
<property name="can_focus">False</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
<object class="GtkFrame" id="frame5">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
<object class="GtkAlignment" id="alignment23">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
<object class="GtkTable" id="table6">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="border_width">3</property>
<property name="n_rows">3</property>
<property name="n_columns">2</property>
<property name="column_spacing">6</property>
<property name="row_spacing">6</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
<object class="GtkLabel" id="label60">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="xalign">1</property>
<property name="label" translatable="yes">Current a_llocation:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">config-memory</property>
</object>
<packing>
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkLabel" id="label307">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Ma_ximum allocation:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">config-maxmem</property>
</object>
<packing>
<property name="top_attach">2</property>
<property name="bottom_attach">3</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkLabel" id="label61">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Total host memory:</property>
</object>
<packing>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkLabel" id="state-host-memory">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label">2 GB</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkHBox" id="hbox46">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">3</property>
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05: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 10:18:47 -04:00
<object class="GtkSpinButton" id="config-memory">
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05:00
<property name="visible">True</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<property name="can_focus">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="invisible_char">●</property>
<property name="adjustment">adjustment2</property>
<property name="climb_rate">2</property>
<property name="numeric">True</property>
<property name="update_policy">if-valid</property>
details: Remove UI for security, apic, acpi, clock 99% of users never need to tweak them, and now that we have virt-xml, most of what they could want to do is a simple CLI oneliner.
2014-01-26 13:43:53 -05:00
<signal name="changed" handler="on_config_memory_changed" swapped="no"/>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<child internal-child="accessible">
<object class="AtkObject" id="config-memory-atkobject">
<property name="AtkObject::accessible-name" translatable="yes">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="xalign">0</property>
<property name="label" translatable="yes">MB</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-01 17:26:46 -05: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 10:18:47 -04:00
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
details: disk: Slim down information output Also, use checkboxes for readonly + shareable in preparation for making them editable.
2009-11-04 15:41:18 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
<property name="y_options"/>
</packing>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
<child>
<object class="GtkHBox" id="hbox47">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="spacing">3</property>
<child>
<object class="GtkSpinButton" id="config-maxmem">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
<property name="adjustment">adjustment1</property>
<property name="climb_rate">2</property>
<property name="numeric">True</property>
<property name="update_policy">if-valid</property>
details: Remove UI for security, apic, acpi, clock 99% of users never need to tweak them, and now that we have virt-xml, most of what they could want to do is a simple CLI oneliner.
2014-01-26 13:43:53 -05:00
<signal name="changed" handler="on_config_maxmem_changed" swapped="no"/>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<child internal-child="accessible">
<object class="AtkObject" id="config-maxmem-atkobject">
<property name="AtkObject::accessible-name" translatable="yes">Max 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="label346">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label" translatable="yes">MB</property>
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">1</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-01 17:26:46 -05: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 10:18:47 -04:00
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="top_attach">2</property>
<property name="bottom_attach">3</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
details: Show disk size if available
2010-03-03 18:43:48 -05: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-01 17:26:46 -05:00
</object>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label101">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&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>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">4</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label54">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">mem</property>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">4</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="tab_fill">False</property>
</packing>
</child>
<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-09 16:21:26 -05:00
<object class="GtkGrid" id="vbox4">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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-09 16:21:26 -05:00
<property name="row_spacing">24</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<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-09 16:21:26 -05:00
<object class="GtkFrame" id="frame4">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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-09 16:21:26 -05:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<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-09 16:21:26 -05:00
<object class="GtkAlignment" id="alignment2">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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-09 16:21:26 -05: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 10:18:47 -04:00
<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-09 16:21:26 -05:00
<object class="GtkCheckButton" id="config-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="use_underline">True</property>
<property name="xalign">0.5</property>
<property name="draw_indicator">True</property>
<signal name="toggled" handler="on_config_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>
<property name="width">1</property>
<property name="height">1</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="GtkHBox" id="boot-init-path-box">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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-09 16:21:26 -05:00
<property name="spacing">12</property>
<child>
<object class="GtkLabel" id="label69">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">Init path:</property>
</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 10:18:47 -04:00
<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-09 16:21:26 -05:00
<object class="GtkEntry" id="boot-init-path">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">True</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-09 16:21:26 -05:00
<property name="invisible_char">●</property>
<property name="width_chars">25</property>
<signal name="changed" handler="on_boot_init_path_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 10:18:47 -04:00
</object>
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-09 16:21:26 -05: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 10:18:47 -04:00
</child>
</object>
</child>
</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-09 16:21:26 -05:00
<child type="label">
<object class="GtkLabel" id="labelll">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;Container init&lt;/b&gt;</property>
<property name="use_markup">True</property>
</object>
</child>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">3</property>
<property name="width">1</property>
<property name="height">1</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 10:18:47 -04:00
<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-09 16:21:26 -05: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 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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-09 16:21:26 -05:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<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-09 16:21:26 -05:00
<object class="GtkBox" id="box1">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</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-09 16:21:26 -05:00
<property name="orientation">vertical</property>
<property name="spacing">6</property>
<child>
<object class="GtkCheckButton" id="boot-kernel-enable">
<property name="label" translatable="yes">Enable direct kernel boot</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
<property name="xalign">0</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>
Enable viewing and changing disk cache mode
2010-05-20 08:34:32 -04:00
<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-09 16:21:26 -05:00
<object class="GtkBox" id="boot-kernel-box">
Enable viewing and changing disk cache mode
2010-05-20 08:34:32 -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-01 17:26:46 -05:00
<property name="can_focus">False</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-09 16:21:26 -05:00
<property name="spacing">6</property>
Enable viewing and changing disk cache mode
2010-05-20 08:34:32 -04:00
<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-09 16:21:26 -05:00
<object class="GtkTable" id="table13">
Enable viewing and changing disk cache mode
2010-05-20 08:34:32 -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-01 17:26:46 -05:00
<property name="can_focus">False</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-09 16:21:26 -05:00
<property name="n_rows">4</property>
<property name="n_columns">2</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 10:18:47 -04:00
<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-09 16:21:26 -05:00
<object class="GtkLabel" id="label38">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</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-09 16:21:26 -05:00
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="ypad">8</property>
<property name="label" translatable="yes">Kernel path:</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
<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-09 16:21:26 -05:00
<property name="x_options">GTK_FILL</property>
<property name="y_options">GTK_FILL</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05:00
<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-09 16:21:26 -05:00
<object class="GtkLabel" id="label39">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="ypad">8</property>
<property name="label" translatable="yes">Initrd path:</property>
</object>
<packing>
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options">GTK_FILL</property>
</packing>
</child>
<child>
<object class="GtkBox" id="box3">
details: Enable setting boot menu flag
2010-12-11 22:00:52 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: Enable setting boot menu flag
2010-12-11 22:00:52 -05:00
<property name="spacing">6</property>
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05:00
<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-09 16:21:26 -05:00
<object class="GtkEntry" id="boot-initrd">
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05:00
<property name="visible">True</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-09 16:21:26 -05:00
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
<signal name="changed" handler="on_boot_initrd_changed" swapped="no"/>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<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-09 16:21:26 -05:00
<object class="GtkButton" id="boot-initrd-browse">
<property name="label" translatable="yes">Browse</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</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-09 16:21:26 -05:00
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<signal name="clicked" handler="on_boot_initrd_browse_clicked" swapped="no"/>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
</child>
</object>
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkBox" id="box4">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">6</property>
<child>
<object class="GtkEntry" id="boot-kernel">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
<signal name="changed" handler="on_boot_kernel_changed" swapped="no"/>
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-01 17:26:46 -05:00
</object>
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05: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 10:18:47 -04: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-01 17:26:46 -05:00
<property name="fill">True</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-09 16:21:26 -05:00
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkButton" id="boot-kernel-browse">
<property name="label" translatable="yes">Browse</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<signal name="clicked" handler="on_boot_kernel_browse_clicked" swapped="no"/>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
details: Enable setting boot menu flag
2010-12-11 22:00:52 -05:00
<property name="position">1</property>
Allow specifying disk storage format in details and addhardware
2010-12-10 19:20:14 -05: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-01 17:26:46 -05: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 10:18:47 -04: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-09 16:21:26 -05:00
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="y_options"/>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
details: Allow changing disk bus This will enable users to actually do a windows virtio install.
2010-12-10 20:33:41 -05: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 10:18:47 -04:00
<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-09 16:21:26 -05:00
<object class="GtkLabel" id="label40">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="ypad">8</property>
<property name="label" translatable="yes">Kernel args:</property>
</object>
<packing>
<property name="top_attach">3</property>
<property name="bottom_attach">4</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options">GTK_FILL</property>
</packing>
</child>
<child>
<object class="GtkEntry" id="boot-kernel-args">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">True</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-09 16:21:26 -05:00
<property name="invisible_char">●</property>
<property name="width_chars">40</property>
<signal name="changed" handler="on_boot_kernel_args_changed" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="top_attach">3</property>
<property name="bottom_attach">4</property>
<property name="y_options">GTK_FILL</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="boot-dtb-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="xalign">0</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-09 16:21:26 -05:00
<property name="ypad">8</property>
<property name="label" translatable="yes">DTB Path:</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
<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-09 16:21:26 -05:00
<property name="top_attach">2</property>
<property name="bottom_attach">3</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options">GTK_FILL</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
details: Allow setting direct kernel/initrd boot
2010-12-11 23:00:19 -05:00
<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-09 16:21:26 -05:00
<object class="GtkBox" id="boot-dtb-box">
details: Allow setting direct kernel/initrd boot
2010-12-11 23:00:19 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: Wire up DTB support Only show it for supported archs (arm, microblaze, ppc). Take this opportunity to tweak the kernel/initrd UI a bit
2013-08-18 12:25:20 -04:00
<property name="spacing">6</property>
details: Allow viewing and editting container <init>
2011-05-26 12:38:48 -04:00
<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-09 16:21:26 -05:00
<object class="GtkEntry" id="boot-dtb">
details: Allow viewing and editting container <init>
2011-05-26 12:38:48 -04:00
<property name="visible">True</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-09 16:21:26 -05:00
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
<signal name="changed" handler="on_boot_dtb_changed" swapped="no"/>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
<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-09 16:21:26 -05:00
<property name="expand">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<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-09 16:21:26 -05:00
<object class="GtkButton" id="boot-dtb-browse">
<property name="label" translatable="yes">Browse</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</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-09 16:21:26 -05:00
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<signal name="clicked" handler="on_boot_dtb_browse_clicked" 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-01 17:26:46 -05:00
</object>
details: Allow viewing and editting container <init>
2011-05-26 12:38:48 -04: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-09 16:21:26 -05:00
<property name="expand">False</property>
details: Wire up DTB support Only show it for supported archs (arm, microblaze, ppc). Take this opportunity to tweak the kernel/initrd UI a bit
2013-08-18 12:25:20 -04:00
<property name="fill">True</property>
<property name="position">1</property>
details: Allow setting direct kernel/initrd boot
2010-12-11 23:00:19 -05: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-01 17:26:46 -05: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 10:18:47 -04: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-09 16:21:26 -05:00
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="top_attach">2</property>
<property name="bottom_attach">3</property>
<property name="y_options"/>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
details: Allow setting direct kernel/initrd boot
2010-12-11 23:00:19 -05: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-01 17:26:46 -05:00
</object>
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-09 16:21:26 -05:00
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkAlignment" id="alignment12">
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<placeholder/>
</child>
</object>
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
details: Allow setting direct kernel/initrd boot
2010-12-11 23:00:19 -05: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 10:18:47 -04:00
</object>
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-09 16:21:26 -05:00
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
details: Allow setting direct kernel/initrd boot
2010-12-11 23:00:19 -05: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-01 17:26:46 -05:00
</object>
details: Allow viewing and editting container <init>
2011-05-26 12:38:48 -04:00
</child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</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-09 16:21:26 -05:00
<child type="label">
<object class="GtkLabel" id="label37">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;Direct kernel boot&lt;/b&gt;</property>
<property name="use_markup">True</property>
</object>
</child>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
<property name="width">1</property>
<property name="height">1</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 10:18:47 -04:00
<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-09 16:21:26 -05: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 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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-09 16:21:26 -05:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
details: Allow viewing and editting container <init>
2011-05-26 12:38:48 -04:00
<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-09 16:21:26 -05:00
<object class="GtkVBox" id="bootvbox">
details: Allow viewing and editting container <init>
2011-05-26 12:38:48 -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-01 17:26:46 -05:00
<property name="can_focus">False</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-09 16:21:26 -05:00
<property name="spacing">6</property>
details: Allow setting direct kernel/initrd boot
2010-12-11 23:00:19 -05:00
<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-09 16:21:26 -05:00
<object class="GtkCheckButton" id="boot-menu">
<property name="label" translatable="yes">Enable boot me_nu</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
<property name="use_underline">True</property>
<property name="xalign">0</property>
<property name="draw_indicator">True</property>
<signal name="toggled" handler="on_boot_menu_changed" swapped="no"/>
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkGrid" id="table2">
details: Allow setting direct kernel/initrd boot
2010-12-11 23:00:19 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</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-09 16:21:26 -05:00
<property name="halign">start</property>
<property name="hexpand">False</property>
<property name="row_spacing">6</property>
<property name="column_spacing">6</property>
<child>
<object class="GtkScrolledWindow" id="scrolledwindow3">
<property name="width_request">125</property>
<property name="height_request">125</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="hscrollbar_policy">never</property>
<property name="shadow_type">in</property>
<child>
<object class="GtkTreeView" id="config-boot-list">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="headers_visible">False</property>
<child internal-child="selection">
<object class="GtkTreeSelection" id="treeview-selection4">
<signal name="changed" handler="on_config_boot_list_changed" swapped="no"/>
</object>
</child>
</object>
</child>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
details: Allow viewing and editting container <init>
2011-05-26 12:38:48 -04:00
<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-09 16:21:26 -05:00
<object class="GtkBox" id="box13">
details: Allow viewing and editting container <init>
2011-05-26 12:38:48 -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-01 17:26:46 -05:00
<property name="can_focus">False</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-09 16:21:26 -05:00
<property name="orientation">vertical</property>
<property name="spacing">6</property>
details: Allow viewing and editting container <init>
2011-05-26 12:38:48 -04:00
<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-09 16:21:26 -05:00
<object class="GtkButton" id="config-boot-moveup">
details: Allow viewing and editting container <init>
2011-05-26 12:38:48 -04:00
<property name="visible">True</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-09 16:21:26 -05: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_config_boot_moveup_clicked" swapped="no"/>
<child>
<object class="GtkImage" id="image7">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="stock">gtk-go-up</property>
</object>
</child>
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-01 17:26:46 -05: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 10:18:47 -04:00
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<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-09 16:21:26 -05:00
<object class="GtkButton" id="config-boot-movedown">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</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-09 16:21:26 -05:00
<property name="sensitive">False</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="can_focus">True</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-09 16:21:26 -05:00
<property name="receives_default">True</property>
<property name="valign">start</property>
<property name="vexpand">False</property>
<signal name="clicked" handler="on_config_boot_movedown_clicked" swapped="no"/>
<child>
<object class="GtkImage" id="image8">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="stock">gtk-go-down</property>
</object>
</child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
details: Allow viewing and editting container <init>
2011-05-26 12:38:48 -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-01 17:26:46 -05:00
</object>
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-09 16:21:26 -05:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
details: Allow viewing and editting container <init>
2011-05-26 12:38:48 -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-01 17:26:46 -05:00
</object>
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-09 16:21:26 -05:00
<packing>
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">1</property>
</packing>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10: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-01 17:26:46 -05:00
</object>
details: Allow setting direct kernel/initrd boot
2010-12-11 23:00:19 -05: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-01 17:26:46 -05:00
</object>
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-09 16:21:26 -05:00
</child>
<child type="label">
<object class="GtkLabel" id="label1">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;Boot device order&lt;/b&gt;</property>
<property name="use_markup">True</property>
</object>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05:00
</object>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-09 16:21:26 -05:00
<property name="left_attach">0</property>
<property name="top_attach">1</property>
<property name="width">1</property>
<property name="height">1</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">5</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="boot-options-lbl">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">boot</property>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">5</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkVBox" id="vbox55">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">12</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
<object class="GtkFrame" id="frame10">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
<object class="GtkAlignment" id="alignment149">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
<object class="GtkVBox" id="vbox13">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="spacing">12</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<child>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<object class="GtkGrid" id="table32">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="border_width">3</property>
<property name="row_spacing">4</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="column_spacing">8</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<child>
<object class="GtkLabel" id="permissions-label">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="xalign">1</property>
<property name="label" translatable="yes">R_eadonly:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">disk-readonly</property>
</object>
<packing>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="left_attach">0</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="top_attach">3</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="label3">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Sharea_ble:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">disk-shareable</property>
</object>
<packing>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="left_attach">0</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="top_attach">4</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
<object class="GtkCheckButton" id="disk-readonly">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
<property name="xalign">0.5</property>
<property name="draw_indicator">True</property>
<signal name="toggled" handler="on_disk_readonly_changed" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">3</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
<object class="GtkCheckButton" id="disk-shareable">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
virt-manager: Add checkbox controlling disk 'removable' flag (crobinso: Fix to use grid rework)
2013-10-04 03:39:01 +02:00
<property name="xalign">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 10:18:47 -04:00
<property name="draw_indicator">True</property>
<signal name="toggled" handler="on_disk_shareable_changed" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">4</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
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 12:21:35 -04:00
<object class="GtkLabel" id="label4">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</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 12:21:35 -04:00
<property name="label" translatable="yes">Storage size:</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
<packing>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="left_attach">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 12:21:35 -04:00
<property name="top_attach">2</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
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 12:21:35 -04:00
<object class="GtkLabel" id="disk-size">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">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 12:21:35 -04:00
<property name="label">size</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
<packing>
<property name="left_attach">1</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 12:21:35 -04:00
<property name="top_attach">2</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
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 12:21:35 -04:00
<object class="GtkLabel" id="label392">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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 12:21:35 -04:00
<property name="xalign">1</property>
<property name="label" translatable="yes">Source path:</property>
<property name="use_underline">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
<packing>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="left_attach">0</property>
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
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 12:21:35 -04:00
<object class="GtkLabel" id="disk-target-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</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>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="width">1</property>
<property name="height">1</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 12:21:35 -04:00
</packing>
</child>
<child>
<object class="GtkBox" id="box9">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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 12:21:35 -04:00
<property name="spacing">6</property>
<child>
<object class="GtkLabel" id="disk-source-path">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label">path</property>
<property name="selectable">True</property>
<property name="ellipsize">start</property>
</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-11 16:40:24 -05: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 10:18:47 -04:00
<object class="GtkButton" id="config-cdrom-connect">
<property name="label">gtk-connect</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
<property name="can_focus">True</property>
<property name="can_default">True</property>
<property name="receives_default">True</property>
<property name="has_tooltip">True</property>
<property name="tooltip_text" translatable="yes">Connect or disconnect media</property>
<property name="use_stock">True</property>
<signal name="clicked" handler="on_config_cdrom_connect_clicked" 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-01 17:26:46 -05:00
</object>
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 12:21:35 -04: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-11 16:40:24 -05: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 10:18:47 -04:00
</object>
<packing>
<property name="left_attach">1</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label375">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Device type:</property>
<property name="use_underline">True</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
virt-manager: Add checkbox controlling disk 'removable' flag (crobinso: Fix to use grid rework)
2013-10-04 03:39:01 +02:00
<child>
<object class="GtkLabel" id="label46">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Removab_le:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">disk-removable</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">5</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkCheckButton" id="disk-removable">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
<property name="use_stock">True</property>
<property name="xalign">0</property>
<property name="draw_indicator">True</property>
<signal name="toggled" handler="on_disk_removable_changed" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">5</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</object>
<packing>
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
</packing>
</child>
<child>
<object class="GtkExpander" id="expander4">
<property name="visible">True</property>
<property name="can_focus">True</property>
<child>
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 12:21:35 -04:00
<object class="GtkBox" id="box10">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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 12:21:35 -04:00
<property name="orientation">vertical</property>
<property name="spacing">6</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<child>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<object class="GtkGrid" id="table11">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
<property name="can_focus">False</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 12:21:35 -04:00
<property name="row_spacing">3</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="column_spacing">8</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<child>
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 12:21:35 -04:00
<object class="GtkLabel" id="label30">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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 12:21:35 -04:00
<property name="xalign">1</property>
<property name="label" translatable="yes">Storage forma_t:</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 10:18:47 -04:00
</object>
<packing>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="left_attach">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 12:21:35 -04:00
<property name="top_attach">2</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
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 12:21:35 -04:00
<object class="GtkLabel" id="label32">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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 12:21:35 -04:00
<property name="xalign">1</property>
<property name="label" translatable="yes">Disk b_us:</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 10:18:47 -04:00
</object>
<packing>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="left_attach">0</property>
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
<object class="GtkEntry" id="disk-serial">
details: Allow changing disk bus This will enable users to actually do a windows virtio install.
2010-12-10 20:33:41 -05:00
<property name="visible">True</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<property name="can_focus">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="invisible_char">●</property>
<property name="width_chars">20</property>
<signal name="changed" handler="on_disk_serial_changed" swapped="no"/>
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-01 17:26:46 -05: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 10:18:47 -04:00
<packing>
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 12:21:35 -04:00
<property name="left_attach">1</property>
<property name="top_attach">1</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
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 12:21:35 -04:00
<object class="GtkComboBox" id="disk-format">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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 12:21:35 -04:00
<property name="has_entry">True</property>
<signal name="changed" handler="on_disk_format_changed" swapped="no"/>
<child internal-child="entry">
<object class="GtkEntry" id="combobox-entry9">
<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 10:18:47 -04:00
</child>
</object>
<packing>
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 12:21:35 -04:00
<property name="left_attach">1</property>
<property name="top_attach">2</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="width">1</property>
<property name="height">1</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 12:21:35 -04:00
</packing>
</child>
<child>
<object class="GtkComboBox" id="disk-bus">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="has_entry">True</property>
<signal name="changed" handler="on_disk_bus_combo_changed" swapped="no"/>
<child internal-child="entry">
<object class="GtkEntry" id="combobox-entry">
<property name="can_focus">True</property>
</object>
</child>
</object>
<packing>
<property name="left_attach">1</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label6">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Serial num_ber:</property>
<property name="use_underline">True</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05:00
</object>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<packing>
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 12:21:35 -04:00
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">0</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
</packing>
</child>
<child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<object class="GtkExpander" id="expander8">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
<property name="can_focus">True</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<child>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<object class="GtkGrid" id="table19">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="row_spacing">3</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="column_spacing">8</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<child>
<object class="GtkLabel" id="label123">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Cac_he mode:</property>
<property name="use_underline">True</property>
</object>
<packing>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="left_attach">0</property>
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">1</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
</packing>
</child>
<child>
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 12:21:35 -04:00
<object class="GtkComboBox" id="disk-cache">
details: Allow changing disk bus This will enable users to actually do a windows virtio install.
2010-12-10 20:33:41 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</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 12:21:35 -04:00
<property name="has_entry">True</property>
<signal name="changed" handler="on_disk_cache_combo_changed" swapped="no"/>
<child internal-child="entry">
<object class="GtkEntry" id="combobox-entry3">
<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-01 17:26:46 -05:00
</object>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
</child>
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 12:21:35 -04:00
</object>
<packing>
<property name="left_attach">1</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">1</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 12:21:35 -04:00
</packing>
</child>
<child>
<object class="GtkComboBox" id="disk-io">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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 12:21:35 -04:00
<property name="has_entry">True</property>
<signal name="changed" handler="on_disk_io_combo_changed" swapped="no"/>
<child internal-child="entry">
<object class="GtkEntry" id="combobox-entry4">
<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 10:18:47 -04:00
</object>
</child>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label79">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">_IO mode:</property>
<property name="use_underline">True</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
<property name="width">1</property>
<property name="height">1</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
</packing>
details: Allow changing disk bus This will enable users to actually do a windows virtio install.
2010-12-10 20:33:41 -05: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-01 17:26:46 -05:00
</object>
details: Allow viewing and changing disk serial num
2011-07-13 13:16:19 -04:00
</child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<child type="label">
<object class="GtkLabel" id="label78">
details: Allow viewing and changing disk serial num
2011-07-13 13:16:19 -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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="label" translatable="yes">_Performance options</property>
details: Allow viewing and changing disk serial num
2011-07-13 13:16:19 -04:00
<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-01 17:26:46 -05:00
</object>
details: Allow changing disk IO mode
2011-07-23 20:41:35 -04:00
</child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
<packing>
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 12:21:35 -04:00
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">1</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
<child>
<object class="GtkExpander" id="iotune-expander">
<property name="visible">True</property>
<property name="can_focus">True</property>
details: Allow changing disk IO mode
2011-07-23 20:41:35 -04:00
<child>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<object class="GtkGrid" id="table20">
details: Allow changing disk IO mode
2011-07-23 20:41:35 -04:00
<property name="visible">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="can_focus">False</property>
<property name="halign">start</property>
<property name="row_spacing">3</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="column_spacing">8</property>
details: Allow changing disk IO mode
2011-07-23 20:41:35 -04:00
<child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<object class="GtkLabel" id="label80">
details: Allow changing disk IO mode
2011-07-23 20:41:35 -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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: Allow changing disk IO mode
2011-07-23 20:41:35 -04:00
<property name="xalign">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 10:18:47 -04:00
<property name="label" translatable="yes">Read:</property>
details: Allow changing disk IO mode
2011-07-23 20:41:35 -04:00
<property name="use_underline">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
<packing>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="left_attach">0</property>
details: Allow changing disk IO mode
2011-07-23 20:41:35 -04:00
<property name="top_attach">1</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="label84">
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="xpad">2</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 10:18:47 -04:00
</object>
<packing>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="left_attach">1</property>
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="label86">
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: Fix some spacing on the disk page
2013-04-16 18:41:20 -04:00
<property name="xalign">0</property>
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
<property name="label" translatable="yes">KBytes/Sec</property>
<property name="use_underline">True</property>
<property name="max_width_chars">20</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
<packing>
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
<property name="left_attach">1</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="label87">
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: Fix some spacing on the disk page
2013-04-16 18:41:20 -04:00
<property name="xalign">0</property>
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
<property name="label" translatable="yes">IOPS/Sec</property>
<property name="use_underline">True</property>
<property name="max_width_chars">20</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
<packing>
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
<property name="left_attach">2</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
<object class="GtkSpinButton" id="disk-iotune-rbs">
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
<property name="width_chars">16</property>
<property name="adjustment">adjustment8</property>
<property name="climb_rate">1</property>
<property name="numeric">True</property>
<property name="update_policy">if-valid</property>
<signal name="changed" handler="on_disk_iotune_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 10:18:47 -04:00
</object>
<packing>
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
<property name="left_attach">1</property>
<property name="top_attach">1</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
<object class="GtkSpinButton" id="disk-iotune-ris">
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
<property name="width_chars">16</property>
<property name="adjustment">adjustment9</property>
<property name="climb_rate">1</property>
<property name="numeric">True</property>
<property name="update_policy">if-valid</property>
<signal name="changed" handler="on_disk_iotune_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 10:18:47 -04:00
</object>
<packing>
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
<property name="left_attach">2</property>
<property name="top_attach">1</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
<object class="GtkSpinButton" id="disk-iotune-wbs">
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
<property name="width_chars">16</property>
<property name="adjustment">adjustment10</property>
<property name="climb_rate">1</property>
<property name="numeric">True</property>
<property name="update_policy">if-valid</property>
<signal name="changed" handler="on_disk_iotune_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 10:18:47 -04:00
</object>
<packing>
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
<property name="left_attach">1</property>
<property name="top_attach">2</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
<object class="GtkSpinButton" id="disk-iotune-wis">
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
<property name="width_chars">16</property>
<property name="adjustment">adjustment11</property>
<property name="climb_rate">1</property>
<property name="numeric">True</property>
<property name="update_policy">if-valid</property>
<signal name="changed" handler="on_disk_iotune_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 10:18:47 -04:00
</object>
<packing>
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
<property name="left_attach">2</property>
<property name="top_attach">2</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
<object class="GtkSpinButton" id="disk-iotune-tbs">
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
<property name="width_chars">16</property>
<property name="adjustment">adjustment12</property>
<property name="climb_rate">1</property>
<property name="numeric">True</property>
<property name="update_policy">if-valid</property>
<signal name="changed" handler="on_disk_iotune_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 10:18:47 -04:00
</object>
<packing>
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
<property name="left_attach">1</property>
<property name="top_attach">3</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
<object class="GtkSpinButton" id="disk-iotune-tis">
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="invisible_char">●</property>
<property name="width_chars">16</property>
<property name="adjustment">adjustment13</property>
<property name="climb_rate">1</property>
<property name="numeric">True</property>
<property name="update_policy">if-valid</property>
<signal name="changed" handler="on_disk_iotune_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 10:18:47 -04:00
</object>
<packing>
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
<property name="left_attach">2</property>
<property name="top_attach">3</property>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
</child>
details: Convert disk UI from table to grid
2013-10-04 08:01:18 -04:00
<child>
<object class="GtkLabel" id="label85">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Total:</property>
<property name="use_underline">True</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">3</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label82">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Write:</property>
<property name="use_underline">True</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<placeholder/>
</child>
virt-manager: add support for iotune (crobinso: Add David to AUTHORS, pylint cleanups, enable for test driver)
2013-02-17 08:40:37 -05:00
</object>
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 16:33:40 -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 10:18:47 -04:00
<child type="label">
<object class="GtkLabel" id="label83">
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 16:33:40 -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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="label" translatable="yes">IO _Tuning</property>
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 16:33:40 -04:00
<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-01 17:26:46 -05:00
</object>
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 16:33:40 -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-01 17:26:46 -05:00
</object>
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 16:33:40 -04:00
<packing>
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 12:21:35 -04:00
<property name="expand">False</property>
<property name="fill">True</property>
<property name="position">2</property>
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 16:33:40 -04: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-01 17:26:46 -05:00
</object>
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 16:33:40 -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 10:18:47 -04:00
<child type="label">
<object class="GtkLabel" id="label31">
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 13:08:15 +02: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="label" translatable="yes">Advanced _options</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<property name="use_underline">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="mnemonic_widget">expander4</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-01 17:26:46 -05:00
</object>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05: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 10:18:47 -04: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-11 16:40:24 -05: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-01 17:26:46 -05:00
</object>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
</child>
<child type="label">
<object class="GtkLabel" id="label376">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;Virtual Disk&lt;/b&gt;</property>
<property name="use_markup">True</property>
</object>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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-01 17:26:46 -05:00
</object>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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 10:18:47 -04:00
<property name="expand">False</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 12:21:35 -04:00
<property name="fill">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="position">0</property>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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 10:18:47 -04:00
<child>
<object class="GtkHButtonBox" id="hbuttonbox9">
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="spacing">5</property>
<property name="layout_style">end</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-01 17:26:46 -05:00
</object>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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 10:18:47 -04:00
<property name="expand">False</property>
<property name="fill">False</property>
<property name="pack_type">end</property>
<property name="position">1</property>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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 10:18:47 -04:00
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">6</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label55">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">dsk</property>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">6</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkVBox" id="vbox54">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">12</property>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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 10:18:47 -04:00
<object class="GtkFrame" id="frame9">
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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 10:18:47 -04:00
<object class="GtkAlignment" id="alignment137">
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<child>
addhw: Use gtkgrid for network UI
2013-09-09 11:37:32 -04:00
<object class="GtkGrid" id="table31">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="border_width">3</property>
addhw: Use gtkgrid for network UI
2013-09-09 11:37:32 -04: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 10:18:47 -04:00
<child>
<object class="GtkLabel" id="network-mac-address">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
addhw: Use gtkgrid for network UI
2013-09-09 11:37:32 -04:00
<property name="label">mac</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</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-27 16:58:45 -05:00
<property name="top_attach">2</property>
addhw: Use gtkgrid for network UI
2013-09-09 11:37:32 -04:00
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label509">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
addhw: Use gtkgrid for network UI
2013-09-09 11:37:32 -04:00
<property name="xalign">1</property>
<property name="yalign">0.47999998927116394</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-27 16:58:45 -05:00
<property name="label" translatable="yes">Device mode_l:</property>
addhw: Use gtkgrid for network UI
2013-09-09 11:37:32 -04:00
<property name="use_underline">True</property>
</object>
<packing>
<property name="left_attach">0</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-27 16:58:45 -05:00
<property name="top_attach">1</property>
addhw: Use gtkgrid for network UI
2013-09-09 11:37:32 -04:00
<property name="width">1</property>
<property name="height">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="xalign">1</property>
<property name="label" translatable="yes">MAC address:</property>
<property name="use_underline">True</property>
</object>
<packing>
<property name="left_attach">0</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-27 16:58:45 -05:00
<property name="top_attach">2</property>
addhw: Use gtkgrid for network UI
2013-09-09 11:37:32 -04:00
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
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-27 16:58:45 -05:00
<object class="GtkComboBox" id="network-model">
addhw: Use gtkgrid for network UI
2013-09-09 11:37:32 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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-27 16:58:45 -05:00
<property name="halign">start</property>
<property name="hexpand">False</property>
<property name="has_entry">True</property>
<signal name="changed" handler="on_network_model_combo_changed" swapped="no"/>
<child internal-child="entry">
<object class="GtkEntry" id="combobox-entry7">
addhw: Use gtkgrid for network UI
2013-09-09 11:37:32 -04:00
<property name="can_focus">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
details: Allow easily changing between VNC and SPICE
2011-03-17 14:24: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-01 17:26:46 -05: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 10:18:47 -04:00
<packing>
<property name="left_attach">1</property>
addhw: Use gtkgrid for network UI
2013-09-09 11:37:32 -04:00
<property name="top_attach">1</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
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-27 16:58:45 -05: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 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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-27 16:58:45 -05:00
<property name="hexpand">False</property>
<property name="vexpand">False</property>
addhw: Use gtkgrid for network UI
2013-09-09 11:37:32 -04:00
<child>
<placeholder/>
</child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
<packing>
addhw: Use gtkgrid for network UI
2013-09-09 11:37:32 -04:00
<property name="left_attach">0</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-27 16:58:45 -05:00
<property name="top_attach">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 12:21:35 -04:00
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
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-27 16:58:45 -05:00
<object class="GtkAlignment" id="network-source-ui-align">
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 12:21:35 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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-27 16:58:45 -05:00
<property name="hexpand">False</property>
<property name="vexpand">False</property>
<child>
<placeholder/>
addhw: Use gtkgrid for network UI
2013-09-09 11:37:32 -04:00
</child>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
</object>
</child>
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label367">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;Virtual Network Interface&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>
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-27 16:58:45 -05:00
<object class="GtkAlignment" id="network-vport-align">
<property name="visible">True</property>
<property name="can_focus">False</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<child>
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-27 16:58:45 -05:00
<placeholder/>
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 14: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-01 17:26:46 -05: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 14:35:36 -04:00
<packing>
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-27 16:58:45 -05:00
<property name="expand">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="fill">True</property>
<property name="position">1</property>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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 10:18:47 -04:00
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">7</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label56">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">net</property>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">7</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkVBox" id="vbox56">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">12</property>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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 10:18:47 -04:00
<object class="GtkFrame" id="frame11">
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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 10:18:47 -04:00
<object class="GtkAlignment" id="alignment150">
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
List, display info about, and enable removing VM host devices.
2009-01-22 17:00:38 -05: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 10:18:47 -04:00
<object class="GtkTable" id="table33">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="border_width">3</property>
<property name="n_rows">2</property>
<property name="n_columns">2</property>
<property name="column_spacing">8</property>
<property name="row_spacing">4</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 14:35:36 -04:00
<child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<object class="GtkLabel" id="label402">
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 14: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="xalign">1</property>
<property name="label" translatable="yes">Type:</property>
<property name="use_underline">True</property>
</object>
<packing>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkLabel" id="label405">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Mode:</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-01 17:26:46 -05: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 10:18:47 -04:00
<packing>
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkLabel" id="input-dev-mode">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label">label401</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkLabel" id="input-dev-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label">label403</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="y_options"/>
</packing>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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-01 17:26:46 -05:00
</object>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
</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 Pointer&lt;/b&gt;</property>
<property name="use_markup">True</property>
</object>
List, display info about, and enable removing VM host devices.
2009-01-22 17:00:38 -05: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-01 17:26:46 -05:00
</object>
List, display info about, and enable removing VM host devices.
2009-01-22 17:00:38 -05: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 10:18:47 -04:00
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">0</property>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05:00
</packing>
List, display info about, and enable removing VM host devices.
2009-01-22 17:00:38 -05: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 10:18:47 -04:00
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">8</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label401">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">inp</property>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">8</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkVBox" id="vbox57">
<property name="visible">True</property>
<property name="can_focus">False</property>
List, display info about, and enable removing VM host devices.
2009-01-22 17:00:38 -05: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 10:18:47 -04:00
<object class="GtkFrame" id="vnc-frame">
List, display info about, and enable removing VM host devices.
2009-01-22 17:00:38 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
List, display info about, and enable removing VM host devices.
2009-01-22 17:00:38 -05:00
<child>
Move shared graphics editing UI to gfxdetails.py Fixes a couple UI bugs: https://bugzilla.redhat.com/show_bug.cgi?id=696217 https://bugzilla.redhat.com/show_bug.cgi?id=875403
2014-01-28 18:44:40 -05:00
<object class="GtkAlignment" id="graphics-align">
List, display info about, and enable removing VM host devices.
2009-01-22 17:00:38 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
List, display info about, and enable removing VM host devices.
2009-01-22 17:00:38 -05:00
<child>
Move shared graphics editing UI to gfxdetails.py Fixes a couple UI bugs: https://bugzilla.redhat.com/show_bug.cgi?id=696217 https://bugzilla.redhat.com/show_bug.cgi?id=875403
2014-01-28 18:44:40 -05:00
<placeholder/>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</child>
</object>
</child>
<child type="label">
<object class="GtkLabel" id="graphics-title">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">&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>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">9</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label500">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">gfx</property>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">9</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkVBox" id="vbox58">
<property name="visible">True</property>
<property name="can_focus">False</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="GtkTable" id="table36">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="border_width">3</property>
<property name="n_columns">2</property>
<property name="column_spacing">8</property>
<property name="row_spacing">4</property>
<child>
<object class="GtkLabel" id="label452">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label" translatable="yes">Device m_odel:</property>
<property name="use_underline">True</property>
</object>
<packing>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
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 12:21:35 -04:00
<object class="GtkComboBox" id="sound-model">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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 12:21:35 -04:00
<property name="has_entry">True</property>
<signal name="changed" handler="on_sound_model_combo_changed" swapped="no"/>
<child internal-child="entry">
<object class="GtkEntry" id="combobox-entry12">
<property name="can_focus">True</property>
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-01 17:26:46 -05:00
</object>
details: show char device target name
2011-04-05 01:35:33 +02: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-01 17:26:46 -05: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 10:18:47 -04:00
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="x_options">GTK_FILL</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 12:21:35 -04:00
<property name="y_options">GTK_FILL</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
</object>
</child>
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label451">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;Sound Device&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>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">10</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label440">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">snd</property>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">10</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkVBox" id="vbox59">
<property name="visible">True</property>
<property name="can_focus">False</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>
<child>
<object class="GtkAlignment" id="alignment160">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<child>
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 12:21:35 -04:00
<object class="GtkGrid" id="table37">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="border_width">3</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 12:21:35 -04:00
<property name="row_spacing">4</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="column_spacing">8</property>
<child>
<object class="GtkLabel" id="char-dev-type-label">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Device type:</property>
</object>
<packing>
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 12:21:35 -04:00
<property name="left_attach">0</property>
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="char-dev-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label" translatable="yes">label506</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</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 12:21:35 -04:00
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="char-source-path">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</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>
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 12:21:35 -04:00
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
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 12:21:35 -04:00
<object class="GtkLabel" id="char-bind-host">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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 12:21:35 -04:00
<property name="xalign">0</property>
<property name="label">label</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
<packing>
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 12:21:35 -04:00
<property name="left_attach">1</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="top_attach">3</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 12:21:35 -04:00
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="char-target-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label">label</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">4</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="char-target-name">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</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>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
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 12:21:35 -04:00
<object class="GtkLabel" id="char-source-host">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label">label</property>
</object>
<packing>
<property name="left_attach">1</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 12:21:35 -04:00
<property name="top_attach">2</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
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 12:21:35 -04:00
<object class="GtkLabel" id="char-source-host-label">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</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 12:21:35 -04:00
<property name="label" translatable="yes">Source host:</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
<packing>
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 12:21:35 -04:00
<property name="left_attach">0</property>
<property name="top_attach">2</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
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 12:21:35 -04:00
<object class="GtkLabel" id="char-bind-host-label">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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 12:21:35 -04:00
<property name="xalign">1</property>
<property name="label" translatable="yes">Bind host:</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
<packing>
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 12:21:35 -04:00
<property name="left_attach">0</property>
<property name="top_attach">3</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
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 12:21:35 -04:00
<object class="GtkLabel" id="char-target-type-label">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</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 12:21:35 -04:00
<property name="label" translatable="yes">Target type:</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
<packing>
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 12:21:35 -04:00
<property name="left_attach">0</property>
<property name="top_attach">4</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
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 12:21:35 -04:00
<object class="GtkLabel" id="char-target-name-label">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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 12:21:35 -04:00
<property name="xalign">1</property>
<property name="label" translatable="yes">Target name:</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
<packing>
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 12:21:35 -04:00
<property name="left_attach">0</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="top_attach">5</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 12:21:35 -04:00
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05:00
</child>
Support viewing and removing VM 'video' devices.
2009-07-09 14:35:55 -04:00
<child>
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 12:21:35 -04:00
<object class="GtkLabel" id="char-source-path-label">
Support viewing and removing VM 'video' devices.
2009-07-09 14: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="xalign">1</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 12:21:35 -04:00
<property name="label" translatable="yes">Source path:</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
<packing>
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 12:21:35 -04:00
<property name="left_attach">0</property>
<property name="top_attach">1</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</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 14: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-01 17:26:46 -05:00
</object>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
</child>
<child type="label">
<object class="GtkLabel" id="char-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;insert type&lt;/b&gt;</property>
<property name="use_markup">True</property>
</object>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05:00
</object>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">11</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label501">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">chr</property>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">11</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkVBox" id="vbox8">
<property name="visible">True</property>
<property name="can_focus">False</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
<object class="GtkFrame" id="frame6">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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 10:18:47 -04:00
<object class="GtkAlignment" id="alignment22">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05:00
<child>
Expose hostdev rombar in UI and cli (bz 768857)
2014-02-10 14:24:22 -05:00
<object class="GtkGrid" id="table50">
details: Centralize most hardware page spacing
2010-12-11 16:40:24 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Expose hostdev rombar in UI and cli (bz 768857)
2014-02-10 14:24:22 -05:00
<property name="row_spacing">6</property>
<property name="column_spacing">6</property>
details: Allow changing video model of an existing device.
2009-11-05 14:59:11 -05: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 10:18:47 -04:00
<object class="GtkLabel" id="label15">
details: Allow changing video model of an existing device.
2009-11-05 14:59:11 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="xalign">0</property>
<property name="label" translatable="yes">Device:</property>
</object>
<packing>
Expose hostdev rombar in UI and cli (bz 768857)
2014-02-10 14:24:22 -05:00
<property name="left_attach">0</property>
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="hostdev-source">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label">label</property>
<property name="selectable">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-01 17:26:46 -05: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 10:18:47 -04:00
<packing>
<property name="left_attach">1</property>
Expose hostdev rombar in UI and cli (bz 768857)
2014-02-10 14:24:22 -05:00
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label5">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</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>
<property name="width">1</property>
<property name="height">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="xalign">0</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>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
details: Allow changing video model of an existing device.
2009-11-05 14:59:11 -05: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-01 17:26:46 -05: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 14: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-01 17:26:46 -05: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 10:18:47 -04:00
</child>
<child type="label">
<object class="GtkLabel" id="hostdev-title">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">&lt;b&gt;Physical Host Device&lt;/b&gt;</property>
<property name="use_markup">True</property>
</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 14: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-01 17:26:46 -05:00
</object>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05: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 10:18:47 -04:00
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05:00
</packing>
Save glade files with glade-3
2008-10-31 10:18:55 -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 10:18:47 -04:00
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">12</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label16">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">phy</property>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">12</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkVBox" id="vbox9">
<property name="visible">True</property>
<property name="can_focus">False</property>
watchdog support: Add, remove, edit in place, and enumerate existing devs
2010-03-24 00:22:17 -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 10:18:47 -04:00
<object class="GtkFrame" id="frame8">
watchdog support: Add, remove, edit in place, and enumerate existing devs
2010-03-24 00:22:17 -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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
watchdog support: Add, remove, edit in place, and enumerate existing devs
2010-03-24 00:22:17 -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 10:18:47 -04:00
<object class="GtkAlignment" id="alignment30">
watchdog support: Add, remove, edit in place, and enumerate existing devs
2010-03-24 00:22:17 -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-01 17:26:46 -05: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 10:18:47 -04: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 00:22:17 -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 10:18:47 -04:00
<object class="GtkTable" id="table4">
watchdog support: Add, remove, edit in place, and enumerate existing devs
2010-03-24 00:22:17 -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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="n_columns">2</property>
<property name="column_spacing">8</property>
<property name="row_spacing">4</property>
watchdog support: Add, remove, edit in place, and enumerate existing devs
2010-03-24 00:22:17 -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 10:18:47 -04:00
<object class="GtkLabel" id="video-heads">
watchdog support: Add, remove, edit in place, and enumerate existing devs
2010-03-24 00:22:17 -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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="xalign">0</property>
<property name="label">label</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="top_attach">2</property>
<property name="bottom_attach">3</property>
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 12:21:35 -04:00
<property name="x_options">GTK_FILL</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkLabel" id="video-ram">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label">label</property>
<property name="selectable">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
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 12:21:35 -04:00
<property name="x_options">GTK_FILL</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkLabel" id="label17">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">RAM:</property>
</object>
<packing>
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkLabel" id="label18">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">M_odel:</property>
<property name="use_underline">True</property>
</object>
<packing>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkLabel" id="label25">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Heads:</property>
</object>
<packing>
<property name="top_attach">2</property>
<property name="bottom_attach">3</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options">GTK_FILL</property>
</packing>
</child>
<child>
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 12:21:35 -04:00
<object class="GtkComboBox" id="video-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 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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 12:21:35 -04:00
<property name="has_entry">True</property>
<signal name="changed" handler="on_video_model_combo_changed" swapped="no"/>
<child internal-child="entry">
<object class="GtkEntry" id="combobox-entry13">
<property name="can_focus">True</property>
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-01 17:26:46 -05:00
</object>
watchdog support: Add, remove, edit in place, and enumerate existing devs
2010-03-24 00:22:17 -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-01 17:26:46 -05: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 10:18:47 -04:00
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="x_options">GTK_FILL</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 12:21:35 -04:00
<property name="y_options">GTK_FILL</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
watchdog support: Add, remove, edit in place, and enumerate existing devs
2010-03-24 00:22:17 -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-01 17:26:46 -05:00
</object>
watchdog support: Add, remove, edit in place, and enumerate existing devs
2010-03-24 00:22:17 -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-01 17:26:46 -05: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 10:18:47 -04:00
</child>
<child type="label">
<object class="GtkLabel" id="hostdev-title1">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;Video&lt;/b&gt;</property>
<property name="use_markup">True</property>
</object>
watchdog support: Add, remove, edit in place, and enumerate existing devs
2010-03-24 00:22:17 -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-01 17:26:46 -05:00
</object>
watchdog support: Add, remove, edit in place, and enumerate existing devs
2010-03-24 00:22:17 -04:00
<packing>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
watchdog support: Add, remove, edit in place, and enumerate existing devs
2010-03-24 00:22:17 -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 10:18:47 -04:00
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">13</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label26">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">vid</property>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">13</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkVBox" id="vbox12">
<property name="visible">True</property>
<property name="can_focus">False</property>
details: Allow viewing/removing controller devices
2010-12-16 12:41:47 -05: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 10:18:47 -04:00
<object class="GtkFrame" id="frame15">
details: Allow viewing/removing controller devices
2010-12-16 12:41:47 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: Allow viewing/removing controller devices
2010-12-16 12:41:47 -05:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<object class="GtkAlignment" id="alignment34">
details: Allow viewing/removing controller devices
2010-12-16 12:41:47 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: Allow viewing/removing controller devices
2010-12-16 12:41:47 -05:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<object class="GtkTable" id="table8">
details: Allow viewing/removing controller devices
2010-12-16 12:41:47 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
virt-manager: Add controller model in details
2011-09-02 03:23:26 +02:00
<property name="n_rows">2</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-01 17:26:46 -05:00
<property name="n_columns">2</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="column_spacing">8</property>
<property name="row_spacing">4</property>
details: Allow viewing/removing controller devices
2010-12-16 12:41:47 -05: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 10:18:47 -04:00
<object class="GtkLabel" id="label27">
details: Allow viewing/removing controller devices
2010-12-16 12:41:47 -05: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
Fix up a ton of UI regressions from gtk3 conversion
2013-01-12 16:13:53 -05:00
<property name="xalign">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 10:18:47 -04:00
<property name="label" translatable="yes">A_ction:</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-01 17:26:46 -05:00
</object>
details: Allow viewing/removing controller devices
2010-12-16 12:41:47 -05: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 10:18:47 -04:00
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
details: Allow viewing/removing controller devices
2010-12-16 12:41:47 -05:00
<property name="x_options">GTK_FILL</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="y_options"/>
details: Allow viewing/removing controller devices
2010-12-16 12:41:47 -05:00
</packing>
</child>
<child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<object class="GtkLabel" id="label35">
details: Allow viewing/removing controller devices
2010-12-16 12:41:47 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="xalign">1</property>
<property name="label" translatable="yes">M_odel:</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-01 17:26:46 -05:00
</object>
details: Allow viewing/removing controller devices
2010-12-16 12:41:47 -05:00
<packing>
<property name="x_options">GTK_FILL</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="y_options"/>
details: Allow viewing/removing controller devices
2010-12-16 12:41:47 -05:00
</packing>
</child>
virt-manager: Add controller model in details
2011-09-02 03:23:26 +02:00
<child>
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 12:21:35 -04:00
<object class="GtkComboBox" id="watchdog-action">
virt-manager: Add controller model in details
2011-09-02 03:23:26 +02: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-01 17:26:46 -05:00
<property name="can_focus">False</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 12:21:35 -04:00
<property name="has_entry">True</property>
<signal name="changed" handler="on_watchdog_action_combo_changed" swapped="no"/>
<child internal-child="entry">
<object class="GtkEntry" id="combobox-entry14">
<property name="can_focus">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04: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-01 17:26:46 -05:00
</object>
virt-manager: Add controller model in details
2011-09-02 03:23:26 +02: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 10:18:47 -04:00
<property name="left_attach">1</property>
<property name="right_attach">2</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 12:21:35 -04:00
<property name="top_attach">1</property>
<property name="bottom_attach">2</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-01 17:26:46 -05:00
<property name="x_options">GTK_FILL</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 12:21:35 -04:00
<property name="y_options">GTK_FILL</property>
virt-manager: Add controller model in details
2011-09-02 03:23:26 +02:00
</packing>
</child>
<child>
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 12:21:35 -04:00
<object class="GtkComboBox" id="watchdog-model">
virt-manager: Add controller model in details
2011-09-02 03:23:26 +02: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-01 17:26:46 -05:00
<property name="can_focus">False</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 12:21:35 -04:00
<property name="has_entry">True</property>
<signal name="changed" handler="on_watchdog_model_combo_changed" swapped="no"/>
<child internal-child="entry">
<object class="GtkEntry" id="combobox-entry15">
<property name="can_focus">True</property>
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-01 17:26:46 -05:00
</object>
virt-manager: allow switching between USB1/piix3 and USB2/ich9 controller crobinso: Fix some small pylint
2011-09-23 17:14:15 +02: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-01 17:26:46 -05:00
</object>
virt-manager: Add controller model in details
2011-09-02 03:23:26 +02: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>
</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-01 17:26:46 -05:00
</object>
details: Allow viewing/removing controller devices
2010-12-16 12:41:47 -05: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-01 17:26:46 -05:00
</object>
details: Allow viewing/removing controller devices
2010-12-16 12:41:47 -05: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 10:18:47 -04:00
<child type="label">
<object class="GtkLabel" id="hostdev-title2">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">&lt;b&gt;Watchdog&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>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">14</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label36">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">wdog</property>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">14</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkFrame" id="frame12">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<child>
<object class="GtkAlignment" id="alignment35">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<child>
virt-manager: Add USB3 convenience option to the controller UI and a --controller usb3 option to virt-install
2013-10-03 16:34:28 -04:00
<object class="GtkGrid" id="table14">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="row_spacing">6</property>
virt-manager: Add USB3 convenience option to the controller UI and a --controller usb3 option to virt-install
2013-10-03 16:34:28 -04:00
<property name="column_spacing">6</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<child>
<object class="GtkLabel" id="label48">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Type:</property>
</object>
<packing>
virt-manager: Add USB3 convenience option to the controller UI and a --controller usb3 option to virt-install
2013-10-03 16:34:28 -04:00
<property name="left_attach">0</property>
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
<object class="GtkLabel" id="controller-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label">foo</property>
</object>
<packing>
<property name="left_attach">1</property>
virt-manager: Add USB3 convenience option to the controller UI and a --controller usb3 option to virt-install
2013-10-03 16:34:28 -04:00
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
<child>
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 12:21:35 -04:00
<object class="GtkComboBox" id="controller-model">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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 12:21:35 -04:00
<property name="has_entry">True</property>
<signal name="changed" handler="on_controller_model_combo_changed" swapped="no"/>
<child internal-child="entry">
<object class="GtkEntry" id="combobox-entry16">
<property name="can_focus">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
</child>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
virt-manager: Add USB3 convenience option to the controller UI and a --controller usb3 option to virt-install
2013-10-03 16:34:28 -04:00
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="mlabel48">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">Model:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
<property name="width">1</property>
<property name="height">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 10:18:47 -04:00
</packing>
</child>
</object>
</child>
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label42">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;Controller&lt;/b&gt;</property>
<property name="use_markup">True</property>
</object>
</child>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">15</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label47">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">ctrl</property>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">15</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkFrame" id="frame16">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<child>
Use vmmFSDetails in details dialog to allow editing filesystem devices
2014-01-21 10:05:31 +01:00
<object class="GtkAlignment" id="fs-alignment">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<child>
Use vmmFSDetails in details dialog to allow editing filesystem devices
2014-01-21 10:05:31 +01:00
<placeholder/>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10: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-01 17:26:46 -05:00
</object>
details: Allow viewing/removing controller devices
2010-12-16 12:41:47 -05: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 10:18:47 -04:00
<child type="label">
<object class="GtkLabel" id="label41">
details: Allow viewing/removing controller devices
2010-12-16 12:41:47 -05: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="label" translatable="yes">&lt;b&gt;Filesystem&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-01 17:26:46 -05:00
</object>
details: Allow viewing/removing controller devices
2010-12-16 12:41:47 -05: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 10:18:47 -04:00
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">16</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label63">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">fs</property>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">16</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkVBox" id="vbox16">
<property name="visible">True</property>
<property name="can_focus">False</property>
details: List guest <filesystem> devices
2011-05-19 15:18:33 -04:00
<child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<object class="GtkFrame" id="frame18">
details: List guest <filesystem> devices
2011-05-19 15:18:33 -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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: List guest <filesystem> devices
2011-05-19 15:18:33 -04:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<object class="GtkAlignment" id="alignment46">
details: List guest <filesystem> devices
2011-05-19 15:18:33 -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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: List guest <filesystem> devices
2011-05-19 15:18:33 -04:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<object class="GtkTable" id="table18">
details: List guest <filesystem> devices
2011-05-19 15:18:33 -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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="border_width">3</property>
details: List guest <filesystem> devices
2011-05-19 15:18:33 -04:00
<property name="n_columns">2</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="column_spacing">8</property>
<property name="row_spacing">4</property>
details: List guest <filesystem> devices
2011-05-19 15:18:33 -04:00
<child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<object class="GtkLabel" id="label74">
details: List guest <filesystem> devices
2011-05-19 15:18:33 -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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: List guest <filesystem> devices
2011-05-19 15:18:33 -04:00
<property name="xalign">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 10:18:47 -04:00
<property name="label" translatable="yes">M_ode:</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-01 17:26:46 -05:00
</object>
details: List guest <filesystem> devices
2011-05-19 15:18:33 -04:00
<packing>
<property name="x_options">GTK_FILL</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="y_options"/>
details: List guest <filesystem> devices
2011-05-19 15:18:33 -04:00
</packing>
</child>
<child>
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 12:21:35 -04:00
<object class="GtkComboBox" id="smartcard-mode">
details: List guest <filesystem> devices
2011-05-19 15:18:33 -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-01 17:26:46 -05:00
<property name="can_focus">False</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 12:21:35 -04:00
<property name="has_entry">True</property>
<signal name="changed" handler="on_smartcard_mode_combo_changed" swapped="no"/>
<child internal-child="entry">
<object class="GtkEntry" id="combobox-entry17">
<property name="can_focus">True</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04: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-01 17:26:46 -05:00
</object>
details: List guest <filesystem> devices
2011-05-19 15:18:33 -04:00
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="x_options">GTK_FILL</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 12:21:35 -04:00
<property name="y_options">GTK_FILL</property>
details: List guest <filesystem> devices
2011-05-19 15:18:33 -04: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-01 17:26:46 -05:00
</object>
details: List guest <filesystem> devices
2011-05-19 15:18:33 -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-01 17:26:46 -05:00
</object>
details: List guest <filesystem> devices
2011-05-19 15:18:33 -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-01 17:26:46 -05:00
<child type="label">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<object class="GtkLabel" id="label75">
details: List guest <filesystem> devices
2011-05-19 15:18:33 -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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="label" translatable="yes">&lt;b&gt;Smartcard Device&lt;/b&gt;</property>
details: List guest <filesystem> devices
2011-05-19 15:18:33 -04:00
<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-01 17:26:46 -05:00
</object>
details: List guest <filesystem> devices
2011-05-19 15:18:33 -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-01 17:26:46 -05:00
</object>
details: List guest <filesystem> devices
2011-05-19 15:18:33 -04:00
<packing>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
details: List guest <filesystem> devices
2011-05-19 15:18:33 -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 10:18:47 -04:00
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">17</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label76">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">sc</property>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">17</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkFrame" id="frame19">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
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 17:42:03 +02: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 10:18:47 -04:00
<object class="GtkAlignment" id="alignment161">
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 17:42:03 +02: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-01 17:26:46 -05: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 10:18:47 -04: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 17:42:03 +02: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 10:18:47 -04:00
<object class="GtkTable" id="table51">
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 17:42:03 +02: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="border_width">3</property>
<property name="n_rows">2</property>
<property name="n_columns">2</property>
<property name="column_spacing">8</property>
<property name="row_spacing">4</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 17:42:03 +02: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 10:18:47 -04:00
<object class="GtkLabel" id="label516">
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 17:42:03 +02: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="xalign">0</property>
<property name="label" translatable="yes">T_ype:</property>
<property name="use_underline">True</property>
</object>
<packing>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
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 12:21:35 -04:00
<object class="GtkLabel" id="label519">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</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 12:21:35 -04:00
<property name="xalign">0</property>
<property name="label" translatable="yes">Address:</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-01 17:26:46 -05: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 10:18:47 -04:00
<packing>
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 12:21:35 -04:00
<property name="top_attach">1</property>
<property name="bottom_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 10:18:47 -04:00
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
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 17:42:03 +02: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 10:18:47 -04:00
<child>
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 12:21:35 -04:00
<object class="GtkLabel" id="redir-address">
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 17:42:03 +02: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="xalign">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 12:21:35 -04:00
<property name="label" translatable="yes">foo:12</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-01 17:26:46 -05: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 10:18:47 -04:00
<packing>
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 12:21:35 -04:00
<property name="left_attach">1</property>
<property name="right_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 10:18:47 -04:00
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
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 12:21:35 -04:00
<object class="GtkLabel" id="redir-type">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">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 12:21:35 -04:00
<property name="label">redir type</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</object>
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="x_options">GTK_FILL</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 12:21:35 -04:00
<property name="y_options">GTK_FILL</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
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 17:42:03 +02: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-01 17:26:46 -05: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 17:42:03 +02: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-01 17:26:46 -05: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 17:42:03 +02: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 10:18:47 -04:00
<child type="label">
<object class="GtkLabel" id="redir-title">
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 17:42:03 +02: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="label" translatable="yes">&lt;b&gt;Redirected 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-01 17:26:46 -05:00
</object>
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02: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 10:18:47 -04:00
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">18</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label515">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">rd</property>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">18</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkVBox" id="vbox17">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="spacing">12</property>
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02: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 10:18:47 -04:00
<object class="GtkFrame" id="frame20">
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02:00
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<object class="GtkAlignment" id="alignment47">
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02:00
<property name="top_padding">3</property>
<property name="left_padding">12</property>
<child>
details: Make TPM UI use a grid
2013-09-23 18:43:50 -04:00
<object class="GtkGrid" id="table200">
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
<property name="border_width">3</property>
<property name="row_spacing">4</property>
details: Make TPM UI use a grid
2013-09-23 18:43:50 -04:00
<property name="column_spacing">8</property>
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02: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 10:18:47 -04:00
<object class="GtkLabel" id="tpm-dev-type">
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
<property name="xalign">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 10:18:47 -04:00
<property name="label">tpm-dev-type</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-01 17:26:46 -05:00
</object>
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02: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 10:18:47 -04:00
<property name="left_attach">1</property>
details: Make TPM UI use a grid
2013-09-23 18:43:50 -04:00
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">1</property>
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02:00
</packing>
</child>
<child>
details: Make TPM UI use a grid
2013-09-23 18:43:50 -04:00
<object class="GtkLabel" id="tpm-device-path">
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: Make TPM UI use a grid
2013-09-23 18:43:50 -04:00
<property name="xalign">0</property>
<property name="label">tpm-device-path</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-01 17:26:46 -05:00
</object>
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02:00
<packing>
details: Make TPM UI use a grid
2013-09-23 18:43:50 -04:00
<property name="left_attach">1</property>
<property name="top_attach">1</property>
<property name="width">1</property>
<property name="height">1</property>
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02:00
</packing>
</child>
<child>
details: Make TPM UI use a grid
2013-09-23 18:43:50 -04:00
<object class="GtkLabel" id="label183">
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="xalign">1</property>
details: Make TPM UI use a grid
2013-09-23 18:43:50 -04:00
<property name="label" translatable="yes">T_ype:</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-01 17:26:46 -05:00
</object>
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02:00
<packing>
details: Make TPM UI use a grid
2013-09-23 18:43:50 -04:00
<property name="left_attach">0</property>
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">1</property>
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02:00
</packing>
</child>
<child>
details: Make TPM UI use a grid
2013-09-23 18:43:50 -04:00
<object class="GtkLabel" id="tpm-device-path-label">
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: Make TPM UI use a grid
2013-09-23 18:43:50 -04:00
<property name="xalign">1</property>
<property name="label" translatable="yes">Path:</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-01 17:26:46 -05:00
</object>
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02:00
<packing>
details: Make TPM UI use a grid
2013-09-23 18:43:50 -04:00
<property name="left_attach">0</property>
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02:00
<property name="top_attach">1</property>
details: Make TPM UI use a grid
2013-09-23 18:43:50 -04:00
<property name="width">1</property>
<property name="height">1</property>
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02: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-01 17:26:46 -05:00
</object>
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02: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-01 17:26:46 -05:00
</object>
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02: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-01 17:26:46 -05:00
<child type="label">
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<object class="GtkLabel" id="label180">
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02: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-01 17:26:46 -05: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 10:18:47 -04:00
<property name="label" translatable="yes">&lt;b&gt;TPM Device&lt;/b&gt;</property>
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02:00
<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-01 17:26:46 -05:00
</object>
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02: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-01 17:26:46 -05:00
</object>
virt-manager: Add redirected devices details
2011-09-02 03:23:27 +02: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 10:18:47 -04:00
<property name="expand">True</property>
<property name="fill">True</property>
<property name="position">0</property>
Minor TPM UI fixups
2013-06-26 20:05:32 -04: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-01 17:26:46 -05: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 10:18:47 -04:00
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">19</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label182">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">tpm</property>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">19</property>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<property name="tab_fill">False</property>
</packing>
watchdog support: Add, remove, edit in place, and enumerate existing devs
2010-03-24 00:22:17 -04:00
</child>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
<child>
<object class="GtkFrame" id="frame21">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<child>
<object class="GtkAlignment" id="alignment28">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="left_padding">12</property>
<child>
<object class="GtkGrid" id="table16">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="border_width">3</property>
<property name="row_spacing">4</property>
<property name="column_spacing">8</property>
<child>
<object class="GtkLabel" id="rng-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label">rng-type</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label90">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</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>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="rng-device">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label">rng-device</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="rng-label1">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Device:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<object class="GtkLabel" id="rng-label4">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Backend type:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">2</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="rng-backend-type">
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<property name="label">rng-backend-type</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">2</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<object class="GtkLabel" id="rng-label7">
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<property name="label" translatable="yes">Mode:</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
</object>
<packing>
<property name="left_attach">0</property>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<property name="top_attach">3</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<object class="GtkLabel" id="rng-mode">
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<property name="label">rng-mode</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">3</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<object class="GtkLabel" id="rng-label2">
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<property name="label" translatable="yes">Host:</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
</object>
<packing>
<property name="left_attach">0</property>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<property name="top_attach">4</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<object class="GtkLabel" id="rng-connect-host">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label">rng-connect-host</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">4</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="rng-label3">
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<property name="label" translatable="yes">Service:</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
</object>
<packing>
<property name="left_attach">0</property>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<property name="top_attach">5</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<object class="GtkLabel" id="rng-connect-service">
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<property name="label">rng-connect-service</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
</object>
<packing>
<property name="left_attach">1</property>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<property name="top_attach">5</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<object class="GtkLabel" id="rng-label8">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Bind Host:</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">6</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="rng-bind-host">
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<property name="label">rng-bind-host</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">6</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<object class="GtkLabel" id="rng-label9">
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<property name="label" translatable="yes">Bind Service:</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
</object>
<packing>
<property name="left_attach">0</property>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<property name="top_attach">7</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<object class="GtkLabel" id="rng-bind-service">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label">rng-bind-service</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">7</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="rng-label6">
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<property name="label" translatable="yes">Rate (period):</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
</object>
<packing>
<property name="left_attach">0</property>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<property name="top_attach">8</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<object class="GtkLabel" id="rng-rate-period">
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<property name="label">rng-rate-period</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
</object>
<packing>
<property name="left_attach">1</property>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<property name="top_attach">8</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="rng-label5">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">1</property>
<property name="label" translatable="yes">Rate (bytes):</property>
</object>
<packing>
<property name="left_attach">0</property>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<property name="top_attach">9</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="rng-rate-bytes">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label">rng-rate-bytes</property>
</object>
<packing>
<property name="left_attach">1</property>
virt-manager: show correctly EGD RNG devices information Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-10-25 17:13:29 +02:00
<property name="top_attach">9</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
</object>
</child>
</object>
</child>
<child type="label">
<object class="GtkLabel" id="label89">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;Random Number Generator&lt;/b&gt;</property>
<property name="use_markup">True</property>
</object>
</child>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">20</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label81">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">rng</property>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">20</property>
virtManager: add GUI elements for showing RNG devices Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2013-09-23 15:39:56 +02:00
<property name="tab_fill">False</property>
</packing>
</child>
virt-manager: add support for showing panic notifier device Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-01-10 17:37:55 +08:00
<child>
<object class="GtkFrame" id="frame17">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label_xalign">0</property>
<property name="shadow_type">none</property>
<child>
details: Couple mini 'panic' UI cleanups
2014-01-11 15:08:00 -05:00
<object class="GtkAlignment" id="alignment10">
virt-manager: add support for showing panic notifier device Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-01-10 17:37:55 +08:00
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="left_padding">12</property>
<child>
details: Couple mini 'panic' UI cleanups
2014-01-11 15:08:00 -05:00
<object class="GtkGrid" id="table_panic">
virt-manager: add support for showing panic notifier device Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-01-10 17:37:55 +08:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: Couple mini 'panic' UI cleanups
2014-01-11 15:08:00 -05:00
<property name="row_spacing">4</property>
<property name="column_spacing">8</property>
virt-manager: add support for showing panic notifier device Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-01-10 17:37:55 +08:00
<child>
details: Couple mini 'panic' UI cleanups
2014-01-11 15:08:00 -05:00
<object class="GtkLabel" id="label95">
virt-manager: add support for showing panic notifier device Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-01-10 17:37:55 +08:00
<property name="visible">True</property>
<property name="can_focus">False</property>
details: Couple mini 'panic' UI cleanups
2014-01-11 15:08:00 -05:00
<property name="xalign">0</property>
<property name="ypad">3</property>
<property name="label" translatable="yes">Address T_ype:</property>
<property name="use_underline">True</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="label96">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label" translatable="yes">_IO Base:</property>
<property name="use_underline">True</property>
</object>
<packing>
<property name="left_attach">0</property>
<property name="top_attach">1</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="panic-type">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label" translatable="yes">panic-address-type</property>
virt-manager: add support for showing panic notifier device Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-01-10 17:37:55 +08:00
</object>
details: Couple mini 'panic' UI cleanups
2014-01-11 15:08:00 -05:00
<packing>
<property name="left_attach">1</property>
<property name="top_attach">0</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
</child>
<child>
<object class="GtkLabel" id="panic-iobase">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label" translatable="yes">panic-iobase</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="top_attach">1</property>
<property name="width">1</property>
<property name="height">1</property>
</packing>
virt-manager: add support for showing panic notifier device Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-01-10 17:37:55 +08:00
</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>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">21</property>
virt-manager: add support for showing panic notifier device Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-01-10 17:37:55 +08:00
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label93">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">panic</property>
</object>
<packing>
details: Move inspection info to its own page
2014-01-26 14:07:35 -05:00
<property name="position">21</property>
virt-manager: add support for showing panic notifier device Signed-off-by: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
2014-01-10 17:37:55 +08:00
<property name="tab_fill">False</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-01 17:26:46 -05:00
</object>
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 10:45:44 -04:00
<packing>
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-01 17:26:46 -05: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 10:45:44 -04:00
<property name="position">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 14:35:36 -04:00
</child>
<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-01 17:26:46 -05:00
<object class="GtkHButtonBox" id="hbuttonbox3">
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 14: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-01 17:26:46 -05:00
<property name="can_focus">False</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 14:35:36 -04:00
<property name="spacing">12</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 10:45:44 -04:00
<property name="layout_style">end</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 14: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-01 17:26:46 -05:00
<object class="GtkButton" id="config-remove">
details: Always have the apply button showing. Also, swap the order of remove and apply so remove is less likely to be pushed by accident.
2009-11-05 15:22:00 -05:00
<property name="label">gtk-remove</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 14:35:36 -04:00
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="can_default">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 10:45:44 -04:00
<property name="receives_default">False</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 14:35:36 -04:00
<property name="use_stock">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-01 17:26:46 -05:00
<signal name="clicked" handler="on_config_remove_clicked" swapped="no"/>
</object>
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 10:45:44 -04:00
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">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 14:35:36 -04:00
</child>
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 14:51:16 -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-01 17:26:46 -05:00
<object class="GtkButton" id="config-cancel">
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 14:51:16 -04:00
<property name="label">gtk-cancel</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<property name="use_stock">True</property>
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-01 17:26:46 -05:00
<signal name="clicked" handler="on_config_cancel_clicked" swapped="no"/>
</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 14:51:16 -04:00
<packing>
<property name="expand">False</property>
<property name="fill">False</property>
<property name="position">1</property>
</packing>
</child>
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 14: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-01 17:26:46 -05:00
<object class="GtkButton" id="config-apply">
details: Always have the apply button showing. Also, swap the order of remove and apply so remove is less likely to be pushed by accident.
2009-11-05 15:22:00 -05:00
<property name="label">gtk-apply</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 14:35:36 -04:00
<property name="visible">True</property>
details: Always have the apply button showing. Also, swap the order of remove and apply so remove is less likely to be pushed by accident.
2009-11-05 15:22:00 -05:00
<property name="sensitive">False</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 14:35:36 -04:00
<property name="can_focus">True</property>
<property name="can_default">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 10:45:44 -04:00
<property name="receives_default">False</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 14:35:36 -04:00
<property name="use_stock">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-01 17:26:46 -05:00
<signal name="clicked" handler="on_config_apply_clicked" swapped="no"/>
</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 14:35:36 -04:00
<packing>
<property name="expand">False</property>
<property name="fill">False</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 14:51:16 -04:00
<property name="position">2</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04: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-01 17:26:46 -05: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 14:35:36 -04:00
<packing>
<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-01 17:26:46 -05:00
<property name="fill">True</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 14:35:36 -04:00
<property name="position">1</property>
</packing>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05: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 14:35:36 -04:00
<packing>
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-01 17:26:46 -05:00
<property name="expand">True</property>
<property name="fill">True</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 14:35:36 -04:00
<property name="position">1</property>
</packing>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05:00
</object>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-01 17:40:38 -04:00
</child>
<child type="tab">
<object class="GtkLabel" id="label77">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">Details</property>
</object>
<packing>
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkNotebook" id="console-pages">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="show_border">False</property>
<signal name="switch-page" handler="on_console_pages_switch_page" after="yes" swapped="no"/>
<child>
<object class="GtkLabel" id="console-unavailable">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label" translatable="yes">&lt;b&gt;The console is currently unavailable&lt;/b&gt;</property>
<property name="use_markup">True</property>
<property name="justify">center</property>
<property name="wrap">True</property>
<property name="width_chars">40</property>
</object>
<packing>
<property name="tab_expand">True</property>
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label434">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">Unavailable</property>
</object>
<packing>
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkTable" id="console-auth">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="border_width">3</property>
<property name="n_rows">3</property>
<property name="n_columns">3</property>
<property name="column_spacing">3</property>
<property name="row_spacing">3</property>
<child>
<object class="GtkLabel" id="label-auth-password">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label" translatable="yes">_Password:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">console-auth-password</property>
</object>
<packing>
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkEntry" id="console-auth-password">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="visibility">False</property>
<signal name="activate" handler="on_console_auth_password_activate" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkCheckButton" id="console-auth-remember">
<property name="label" translatable="yes">_Save this password in your keyring</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
<property name="use_underline">True</property>
<property name="xalign">0.5</property>
<property name="yalign">0</property>
<property name="draw_indicator">True</property>
</object>
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="top_attach">2</property>
<property name="bottom_attach">3</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkLabel" id="label-auth-username">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="xalign">0</property>
<property name="label" translatable="yes">_Username:</property>
<property name="use_underline">True</property>
<property name="mnemonic_widget">console-auth-username</property>
</object>
<packing>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkEntry" id="console-auth-username">
<property name="visible">True</property>
<property name="can_focus">True</property>
<signal name="activate" handler="on_console_auth_password_activate" swapped="no"/>
</object>
<packing>
<property name="left_attach">1</property>
<property name="right_attach">2</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkButton" id="console-auth-login">
<property name="label" translatable="yes">_Login</property>
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">False</property>
ui: Set non-stock button images in glade, not explicitly in code
2013-09-22 12:18:49 -04:00
<property name="image">image70</property>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-01 17:40:38 -04:00
<property name="use_underline">True</property>
<signal name="clicked" handler="on_console_auth_login_clicked" swapped="no"/>
</object>
<packing>
<property name="left_attach">2</property>
<property name="right_attach">3</property>
<property name="top_attach">1</property>
<property name="bottom_attach">2</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options"/>
</packing>
</child>
<child>
<object class="GtkAlignment" id="alignment17">
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<placeholder/>
</child>
</object>
<packing>
<property name="top_attach">2</property>
<property name="bottom_attach">3</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options">GTK_FILL</property>
</packing>
</child>
<child>
<object class="GtkAlignment" id="alignment18">
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<placeholder/>
</child>
</object>
<packing>
<property name="left_attach">2</property>
<property name="right_attach">3</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options">GTK_FILL</property>
</packing>
</child>
<child>
<object class="GtkAlignment" id="alignment19">
<property name="visible">True</property>
<property name="can_focus">False</property>
<child>
<placeholder/>
</child>
</object>
<packing>
<property name="left_attach">2</property>
<property name="right_attach">3</property>
<property name="top_attach">2</property>
<property name="bottom_attach">3</property>
<property name="x_options">GTK_FILL</property>
<property name="y_options">GTK_FILL</property>
</packing>
</child>
</object>
<packing>
<property name="position">1</property>
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label438">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">Auth</property>
</object>
<packing>
<property name="position">1</property>
<property name="tab_fill">False</property>
</packing>
</child>
<child>
<object class="GtkScrolledWindow" id="console-gfx-scroll">
<property name="visible">True</property>
<property name="can_focus">True</property>
<child>
<object class="GtkViewport" id="console-gfx-viewport">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="resize_mode">queue</property>
<property name="shadow_type">none</property>
<child>
<placeholder/>
</child>
</object>
</child>
</object>
<packing>
<property name="position">2</property>
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label439">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">Graphics</property>
</object>
<packing>
<property name="position">2</property>
<property name="tab_fill">False</property>
</packing>
</child>
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<packing>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05:00
<property name="position">1</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04: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-01 17:26:46 -05:00
<child type="tab">
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-01 17:40:38 -04:00
<object class="GtkLabel" id="label420">
Save glade files with glade-3
2008-10-31 10:18: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-01 17:26:46 -05:00
<property name="can_focus">False</property>
details: Track serial pages as console tabs A bit cleaner conceptually, and shrinks the ever growing details.py
2013-09-01 17:40:38 -04:00
<property name="label">Console</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-01 17:26:46 -05:00
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<packing>
Break out VM->Overview into two 'Details' list entries: Overview and Performance.
2009-02-09 14:55:18 -05:00
<property name="position">1</property>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<property name="tab_fill">False</property>
</packing>
</child>
Initial snapshot support This adds initial UI for managing snapshots: list, run/revert, delete, add, and redefining (for changing <description>) supported, but currently only for internal snapshots. The UI is mostly in its final form except for some bells and whistles. The real remaining question is what do we want to advertise and support. Internal (qcow2) snapshots are by far the simplest to manage, very mature, and already have the semantics we want. However most recent libvirt and qemu work has been to facilitate external snapshots, which are more extensible and can be performed live, and with qemu-ga coordination for extra safety. However they make things much harder for virt-manager at the moment. Until we have a plan, this work should be considered experimental and not be relied upon.
2013-08-02 10:18:47 -04:00
<child>
<object class="GtkBox" id="snapshot-placeholder">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="orientation">vertical</property>
<child>
<placeholder/>
</child>
</object>
<packing>
<property name="position">2</property>
</packing>
</child>
<child type="tab">
<object class="GtkLabel" id="label88">
<property name="visible">True</property>
<property name="can_focus">False</property>
<property name="label">Snapshots</property>
</object>
<packing>
<property name="position">2</property>
<property name="tab_fill">False</property>
</packing>
</child>
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-01 17:26:46 -05:00
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -04:00
<packing>
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-01 17:26:46 -05:00
<property name="expand">True</property>
<property name="fill">True</property>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05:00
</object>
Save glade files with glade-3
2008-10-31 10:18:55 -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-01 17:26:46 -05:00
</object>
</interface>
Reference in New Issue Copy Permalink