diff options
Diffstat (limited to 'help/virt-manager/C')
18 files changed, 0 insertions, 1817 deletions
diff --git a/help/virt-manager/C/Makefile.am b/help/virt-manager/C/Makefile.am deleted file mode 100644 index f512ca93..00000000 --- a/help/virt-manager/C/Makefile.am +++ /dev/null @@ -1,7 +0,0 @@ -figdir = figures -docname = virt-manager -lang = C -omffile = virt-manager-C.omf -entities = fdl-appendix.xml legal.xml -include $(top_srcdir)/xmldocs.make -dist-hook: app-dist-hook diff --git a/help/virt-manager/C/fdl-appendix.xml b/help/virt-manager/C/fdl-appendix.xml deleted file mode 100644 index 1b46fb77..00000000 --- a/help/virt-manager/C/fdl-appendix.xml +++ /dev/null @@ -1,667 +0,0 @@ -<!-- - The GNU Free Documentation License 1.1 in DocBook - Markup by Eric Baudais <baudais@okstate.edu> - Maintained by the GNOME Documentation Project - http://developer.gnome.org/projects/gdp - Version: 1.0.1 - Last Modified: Nov 16, 2000 ---> - -<appendix id="fdl"> - <appendixinfo> - <releaseinfo> - Version 1.1, March 2000 - </releaseinfo> - <copyright> - <year>2000</year><holder>Free Software Foundation, Inc.</holder> - </copyright> - <legalnotice id="fdl-legalnotice"> - <para> - <address>Free Software Foundation, Inc. <street>59 Temple Place, - Suite 330</street>, <city>Boston</city>, <state>MA</state> - <postcode>02111-1307</postcode> <country>USA</country></address> - Everyone is permitted to copy and distribute verbatim copies of this - license document, but changing it is not allowed. - </para> - </legalnotice> - </appendixinfo> - <title>GNU Free Documentation License</title> - - <sect1 id="fdl-preamble"> - <title>0. PREAMBLE</title> - <para> - The purpose of this License is to make a manual, textbook, or - other written document <quote>free</quote> in the sense of - freedom: to assure everyone the effective freedom to copy and - redistribute it, with or without modifying it, either - commercially or noncommercially. Secondarily, this License - preserves for the author and publisher a way to get credit for - their work, while not being considered responsible for - modifications made by others. - </para> - - <para> - This License is a kind of <quote>copyleft</quote>, which means - that derivative works of the document must themselves be free in - the same sense. It complements the GNU General Public License, - which is a copyleft license designed for free software. - </para> - - <para> - We have designed this License in order to use it for manuals for - free software, because free software needs free documentation: a - free program should come with manuals providing the same - freedoms that the software does. But this License is not limited - to software manuals; it can be used for any textual work, - regardless of subject matter or whether it is published as a - printed book. We recommend this License principally for works - whose purpose is instruction or reference. - </para> - </sect1> - <sect1 id="fdl-section1"> - <title>1. APPLICABILITY AND DEFINITIONS</title> - <para id="fdl-document"> - This License applies to any manual or other work that contains a - notice placed by the copyright holder saying it can be - distributed under the terms of this License. The - <quote>Document</quote>, below, refers to any such manual or - work. Any member of the public is a licensee, and is addressed - as <quote>you</quote>. - </para> - - <para id="fdl-modified"> - A <quote>Modified Version</quote> of the Document means any work - containing the Document or a portion of it, either copied - verbatim, or with modifications and/or translated into another - language. - </para> - - <para id="fdl-secondary"> - A <quote>Secondary Section</quote> is a named appendix or a - front-matter section of the <link - linkend="fdl-document">Document</link> that deals exclusively - with the relationship of the publishers or authors of the - Document to the Document's overall subject (or to related - matters) and contains nothing that could fall directly within - that overall subject. (For example, if the Document is in part a - textbook of mathematics, a Secondary Section may not explain any - mathematics.) The relationship could be a matter of historical - connection with the subject or with related matters, or of - legal, commercial, philosophical, ethical or political position - regarding them. - </para> - - <para id="fdl-invariant"> - The <quote>Invariant Sections</quote> are certain <link - linkend="fdl-secondary"> Secondary Sections</link> whose titles - are designated, as being those of Invariant Sections, in the - notice that says that the <link - linkend="fdl-document">Document</link> is released under this - License. - </para> - - <para id="fdl-cover-texts"> - The <quote>Cover Texts</quote> are certain short passages of - text that are listed, as Front-Cover Texts or Back-Cover Texts, - in the notice that says that the <link - linkend="fdl-document">Document</link> is released under this - License. - </para> - - <para id="fdl-transparent"> - A <quote>Transparent</quote> copy of the <link - linkend="fdl-document"> Document</link> means a machine-readable - copy, represented in a format whose specification is available - to the general public, whose contents can be viewed and edited - directly and straightforwardly with generic text editors or (for - images composed of pixels) generic paint programs or (for - drawings) some widely available drawing editor, and that is - suitable for input to text formatters or for automatic - translation to a variety of formats suitable for input to text - formatters. A copy made in an otherwise Transparent file format - whose markup has been designed to thwart or discourage - subsequent modification by readers is not Transparent. A copy - that is not <quote>Transparent</quote> is called - <quote>Opaque</quote>. - </para> - - <para> - Examples of suitable formats for Transparent copies include - plain ASCII without markup, Texinfo input format, LaTeX input - format, SGML or XML using a publicly available DTD, and - standard-conforming simple HTML designed for human - modification. Opaque formats include PostScript, PDF, - proprietary formats that can be read and edited only by - proprietary word processors, SGML or XML for which the DTD - and/or processing tools are not generally available, and the - machine-generated HTML produced by some word processors for - output purposes only. - </para> - - <para id="fdl-title-page"> - The <quote>Title Page</quote> means, for a printed book, the - title page itself, plus such following pages as are needed to - hold, legibly, the material this License requires to appear in - the title page. For works in formats which do not have any title - page as such, <quote>Title Page</quote> means the text near the - most prominent appearance of the work's title, preceding the - beginning of the body of the text. - </para> - </sect1> - - <sect1 id="fdl-section2"> - <title>2. VERBATIM COPYING</title> - <para> - You may copy and distribute the <link - linkend="fdl-document">Document</link> in any medium, either - commercially or noncommercially, provided that this License, the - copyright notices, and the license notice saying this License - applies to the Document are reproduced in all copies, and that - you add no other conditions whatsoever to those of this - License. You may not use technical measures to obstruct or - control the reading or further copying of the copies you make or - distribute. However, you may accept compensation in exchange for - copies. If you distribute a large enough number of copies you - must also follow the conditions in <link - linkend="fdl-section3">section 3</link>. - </para> - - <para> - You may also lend copies, under the same conditions stated - above, and you may publicly display copies. - </para> - </sect1> - - <sect1 id="fdl-section3"> - <title>3. COPYING IN QUANTITY</title> - <para> - If you publish printed copies of the <link - linkend="fdl-document">Document</link> numbering more than 100, - and the Document's license notice requires <link - linkend="fdl-cover-texts">Cover Texts</link>, you must enclose - the copies in covers that carry, clearly and legibly, all these - Cover Texts: Front-Cover Texts on the front cover, and - Back-Cover Texts on the back cover. Both covers must also - clearly and legibly identify you as the publisher of these - copies. The front cover must present the full title with all - words of the title equally prominent and visible. You may add - other material on the covers in addition. Copying with changes - limited to the covers, as long as they preserve the title of the - <link linkend="fdl-document">Document</link> and satisfy these - conditions, can be treated as verbatim copying in other - respects. - </para> - - <para> - If the required texts for either cover are too voluminous to fit - legibly, you should put the first ones listed (as many as fit - reasonably) on the actual cover, and continue the rest onto - adjacent pages. - </para> - - <para> - If you publish or distribute <link - linkend="fdl-transparent">Opaque</link> copies of the <link - linkend="fdl-document">Document</link> numbering more than 100, - you must either include a machine-readable <link - linkend="fdl-transparent">Transparent</link> copy along with - each Opaque copy, or state in or with each Opaque copy a - publicly-accessible computer-network location containing a - complete Transparent copy of the Document, free of added - material, which the general network-using public has access to - download anonymously at no charge using public-standard network - protocols. If you use the latter option, you must take - reasonably prudent steps, when you begin distribution of Opaque - copies in quantity, to ensure that this Transparent copy will - remain thus accessible at the stated location until at least one - year after the last time you distribute an Opaque copy (directly - or through your agents or retailers) of that edition to the - public. - </para> - - <para> - It is requested, but not required, that you contact the authors - of the <link linkend="fdl-document">Document</link> well before - redistributing any large number of copies, to give them a chance - to provide you with an updated version of the Document. - </para> - </sect1> - - <sect1 id="fdl-section4"> - <title>4. MODIFICATIONS</title> - <para> - You may copy and distribute a <link - linkend="fdl-modified">Modified Version</link> of the <link - linkend="fdl-document">Document</link> under the conditions of - sections <link linkend="fdl-section2">2</link> and <link - linkend="fdl-section3">3</link> above, provided that you release - the Modified Version under precisely this License, with the - Modified Version filling the role of the Document, thus - licensing distribution and modification of the Modified Version - to whoever possesses a copy of it. In addition, you must do - these things in the Modified Version: - </para> - - <itemizedlist mark="opencircle"> - <listitem> - <formalpara> - <title>A</title> - <para> - Use in the <link linkend="fdl-title-page">Title - Page</link> (and on the covers, if any) a title distinct - from that of the <link - linkend="fdl-document">Document</link>, and from those of - previous versions (which should, if there were any, be - listed in the History section of the Document). You may - use the same title as a previous version if the original - publisher of that version gives permission. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>B</title> - <para> - List on the <link linkend="fdl-title-page">Title - Page</link>, as authors, one or more persons or entities - responsible for authorship of the modifications in the - <link linkend="fdl-modified">Modified Version</link>, - together with at least five of the principal authors of - the <link linkend="fdl-document">Document</link> (all of - its principal authors, if it has less than five). - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>C</title> - <para> - State on the <link linkend="fdl-title-page">Title - Page</link> the name of the publisher of the <link - linkend="fdl-modified">Modified Version</link>, as the - publisher. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>D</title> - <para> - Preserve all the copyright notices of the <link - linkend="fdl-document">Document</link>. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>E</title> - <para> - Add an appropriate copyright notice for your modifications - adjacent to the other copyright notices. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>F</title> - <para> - Include, immediately after the copyright notices, a - license notice giving the public permission to use the - <link linkend="fdl-modified">Modified Version</link> under - the terms of this License, in the form shown in the - Addendum below. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>G</title> - <para> - Preserve in that license notice the full lists of <link - linkend="fdl-invariant"> Invariant Sections</link> and - required <link linkend="fdl-cover-texts">Cover - Texts</link> given in the <link - linkend="fdl-document">Document's</link> license notice. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>H</title> - <para> - Include an unaltered copy of this License. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>I</title> - <para> - Preserve the section entitled <quote>History</quote>, and - its title, and add to it an item stating at least the - title, year, new authors, and publisher of the <link - linkend="fdl-modified">Modified Version </link>as given on - the <link linkend="fdl-title-page">Title Page</link>. If - there is no section entitled <quote>History</quote> in the - <link linkend="fdl-document">Document</link>, create one - stating the title, year, authors, and publisher of the - Document as given on its Title Page, then add an item - describing the Modified Version as stated in the previous - sentence. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>J</title> - <para> - Preserve the network location, if any, given in the <link - linkend="fdl-document">Document</link> for public access - to a <link linkend="fdl-transparent">Transparent</link> - copy of the Document, and likewise the network locations - given in the Document for previous versions it was based - on. These may be placed in the <quote>History</quote> - section. You may omit a network location for a work that - was published at least four years before the Document - itself, or if the original publisher of the version it - refers to gives permission. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>K</title> - <para> - In any section entitled <quote>Acknowledgments</quote> or - <quote>Dedications</quote>, preserve the section's title, - and preserve in the section all the substance and tone of - each of the contributor acknowledgments and/or - dedications given therein. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>L</title> - <para> - Preserve all the <link linkend="fdl-invariant">Invariant - Sections</link> of the <link - linkend="fdl-document">Document</link>, unaltered in their - text and in their titles. Section numbers or the - equivalent are not considered part of the section titles. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>M</title> - <para> - Delete any section entitled - <quote>Endorsements</quote>. Such a section may not be - included in the <link linkend="fdl-modified">Modified - Version</link>. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>N</title> - <para> - Do not retitle any existing section as - <quote>Endorsements</quote> or to conflict in title with - any <link linkend="fdl-invariant">Invariant - Section</link>. - </para> - </formalpara> - </listitem> - </itemizedlist> - - <para> - If the <link linkend="fdl-modified">Modified Version</link> - includes new front-matter sections or appendices that qualify as - <link linkend="fdl-secondary">Secondary Sections</link> and - contain no material copied from the Document, you may at your - option designate some or all of these sections as invariant. To - do this, add their titles to the list of <link - linkend="fdl-invariant">Invariant Sections</link> in the - Modified Version's license notice. These titles must be - distinct from any other section titles. - </para> - - <para> - You may add a section entitled <quote>Endorsements</quote>, - provided it contains nothing but endorsements of your <link - linkend="fdl-modified">Modified Version</link> by various - parties--for example, statements of peer review or that the text - has been approved by an organization as the authoritative - definition of a standard. - </para> - - <para> - You may add a passage of up to five words as a <link - linkend="fdl-cover-texts">Front-Cover Text</link>, and a passage - of up to 25 words as a <link - linkend="fdl-cover-texts">Back-Cover Text</link>, to the end of - the list of <link linkend="fdl-cover-texts">Cover Texts</link> - in the <link linkend="fdl-modified">Modified Version</link>. - Only one passage of Front-Cover Text and one of Back-Cover Text - may be added by (or through arrangements made by) any one - entity. If the <link linkend="fdl-document">Document</link> - already includes a cover text for the same cover, previously - added by you or by arrangement made by the same entity you are - acting on behalf of, you may not add another; but you may - replace the old one, on explicit permission from the previous - publisher that added the old one. - </para> - - <para> - The author(s) and publisher(s) of the <link - linkend="fdl-document">Document</link> do not by this License - give permission to use their names for publicity for or to - assert or imply endorsement of any <link - linkend="fdl-modified">Modified Version </link>. - </para> - </sect1> - - <sect1 id="fdl-section5"> - <title>5. COMBINING DOCUMENTS</title> - <para> - You may combine the <link linkend="fdl-document">Document</link> - with other documents released under this License, under the - terms defined in <link linkend="fdl-section4">section 4</link> - above for modified versions, provided that you include in the - combination all of the <link linkend="fdl-invariant">Invariant - Sections</link> of all of the original documents, unmodified, - and list them all as Invariant Sections of your combined work in - its license notice. - </para> - - <para> - The combined work need only contain one copy of this License, - and multiple identical <link linkend="fdl-invariant">Invariant - Sections</link> may be replaced with a single copy. If there are - multiple Invariant Sections with the same name but different - contents, make the title of each such section unique by adding - at the end of it, in parentheses, the name of the original - author or publisher of that section if known, or else a unique - number. Make the same adjustment to the section titles in the - list of Invariant Sections in the license notice of the combined - work. - </para> - - <para> - In the combination, you must combine any sections entitled - <quote>History</quote> in the various original documents, - forming one section entitled <quote>History</quote>; likewise - combine any sections entitled <quote>Acknowledgments</quote>, - and any sections entitled <quote>Dedications</quote>. You must - delete all sections entitled <quote>Endorsements.</quote> - </para> - </sect1> - - <sect1 id="fdl-section6"> - <title>6. COLLECTIONS OF DOCUMENTS</title> - <para> - You may make a collection consisting of the <link - linkend="fdl-document">Document</link> and other documents - released under this License, and replace the individual copies - of this License in the various documents with a single copy that - is included in the collection, provided that you follow the - rules of this License for verbatim copying of each of the - documents in all other respects. - </para> - - <para> - You may extract a single document from such a collection, and - distribute it individually under this License, provided you - insert a copy of this License into the extracted document, and - follow this License in all other respects regarding verbatim - copying of that document. - </para> - </sect1> - - <sect1 id="fdl-section7"> - <title>7. AGGREGATION WITH INDEPENDENT WORKS</title> - <para> - A compilation of the <link - linkend="fdl-document">Document</link> or its derivatives with - other separate and independent documents or works, in or on a - volume of a storage or distribution medium, does not as a whole - count as a <link linkend="fdl-modified">Modified Version</link> - of the Document, provided no compilation copyright is claimed - for the compilation. Such a compilation is called an - <quote>aggregate</quote>, and this License does not apply to the - other self-contained works thus compiled with the Document , on - account of their being thus compiled, if they are not themselves - derivative works of the Document. If the <link - linkend="fdl-cover-texts">Cover Text</link> requirement of <link - linkend="fdl-section3">section 3</link> is applicable to these - copies of the Document, then if the Document is less than one - quarter of the entire aggregate, the Document's Cover Texts may - be placed on covers that surround only the Document within the - aggregate. Otherwise they must appear on covers around the whole - aggregate. - </para> - </sect1> - - <sect1 id="fdl-section8"> - <title>8. TRANSLATION</title> - <para> - Translation is considered a kind of modification, so you may - distribute translations of the <link - linkend="fdl-document">Document</link> under the terms of <link - linkend="fdl-section4">section 4</link>. Replacing <link - linkend="fdl-invariant"> Invariant Sections</link> with - translations requires special permission from their copyright - holders, but you may include translations of some or all - Invariant Sections in addition to the original versions of these - Invariant Sections. You may include a translation of this - License provided that you also include the original English - version of this License. In case of a disagreement between the - translation and the original English version of this License, - the original English version will prevail. - </para> - </sect1> - - <sect1 id="fdl-section9"> - <title>9. TERMINATION</title> - <para> - You may not copy, modify, sublicense, or distribute the <link - linkend="fdl-document">Document</link> except as expressly - provided for under this License. Any other attempt to copy, - modify, sublicense or distribute the Document is void, and will - automatically terminate your rights under this License. However, - parties who have received copies, or rights, from you under this - License will not have their licenses terminated so long as such - parties remain in full compliance. - </para> - </sect1> - - <sect1 id="fdl-section10"> - <title>10. FUTURE REVISIONS OF THIS LICENSE</title> - <para> - The <ulink type="http" - url="http://www.gnu.org/fsf/fsf.html">Free Software - Foundation</ulink> may publish new, revised versions of the GNU - Free Documentation License from time to time. Such new versions - will be similar in spirit to the present version, but may differ - in detail to address new problems or concerns. See <ulink - type="http" - url="http://www.gnu.org/copyleft">http://www.gnu.org/copyleft/</ulink>. - </para> - - <para> - Each version of the License is given a distinguishing version - number. If the <link linkend="fdl-document">Document</link> - specifies that a particular numbered version of this License - <quote>or any later version</quote> applies to it, you have the - option of following the terms and conditions either of that - specified version or of any later version that has been - published (not as a draft) by the Free Software Foundation. If - the Document does not specify a version number of this License, - you may choose any version ever published (not as a draft) by - the Free Software Foundation. - </para> - </sect1> - - <sect1 id="fdl-using"> - <title>Addendum</title> - <para> - To use this License in a document you have written, include a copy of - the License in the document and put the following copyright and - license notices just after the title page: - </para> - - <blockquote> - <para> - Copyright YEAR YOUR NAME. - </para> - <para> - Permission is granted to copy, distribute and/or modify this - document under the terms of the GNU Free Documentation - License, Version 1.1 or any later version published by the - Free Software Foundation; with the <link - linkend="fdl-invariant">Invariant Sections</link> being LIST - THEIR TITLES, with the <link - linkend="fdl-cover-texts">Front-Cover Texts</link> being LIST, - and with the <link linkend="fdl-cover-texts">Back-Cover - Texts</link> being LIST. A copy of the license is included in - the section entitled <quote>GNU Free Documentation - License</quote>. - </para> - </blockquote> - - <para> - If you have no <link linkend="fdl-invariant">Invariant - Sections</link>, write <quote>with no Invariant Sections</quote> - instead of saying which ones are invariant. If you have no - <link linkend="fdl-cover-texts">Front-Cover Texts</link>, write - <quote>no Front-Cover Texts</quote> instead of - <quote>Front-Cover Texts being LIST</quote>; likewise for <link - linkend="fdl-cover-texts">Back-Cover Texts</link>. - </para> - - <para> - If your document contains nontrivial examples of program code, - we recommend releasing these examples in parallel under your - choice of free software license, such as the <ulink type="http" - url="http://www.gnu.org/copyleft/gpl.html"> GNU General Public - License</ulink>, to permit their use in free software. - </para> - </sect1> -</appendix> - - diff --git a/help/virt-manager/C/figures/vm-assign-storage.png b/help/virt-manager/C/figures/vm-assign-storage.png Binary files differdeleted file mode 100755 index 7637327c..00000000 --- a/help/virt-manager/C/figures/vm-assign-storage.png +++ /dev/null diff --git a/help/virt-manager/C/figures/vm-connection-window.png b/help/virt-manager/C/figures/vm-connection-window.png Binary files differdeleted file mode 100755 index 749a1875..00000000 --- a/help/virt-manager/C/figures/vm-connection-window.png +++ /dev/null diff --git a/help/virt-manager/C/figures/vm-create-mem-cpu.png b/help/virt-manager/C/figures/vm-create-mem-cpu.png Binary files differdeleted file mode 100755 index 9dffd41c..00000000 --- a/help/virt-manager/C/figures/vm-create-mem-cpu.png +++ /dev/null diff --git a/help/virt-manager/C/figures/vm-details-hardware-disk.png b/help/virt-manager/C/figures/vm-details-hardware-disk.png Binary files differdeleted file mode 100755 index a1a0fc29..00000000 --- a/help/virt-manager/C/figures/vm-details-hardware-disk.png +++ /dev/null diff --git a/help/virt-manager/C/figures/vm-details-hardware-memory.png b/help/virt-manager/C/figures/vm-details-hardware-memory.png Binary files differdeleted file mode 100755 index cd508063..00000000 --- a/help/virt-manager/C/figures/vm-details-hardware-memory.png +++ /dev/null diff --git a/help/virt-manager/C/figures/vm-details-hardware-network.png b/help/virt-manager/C/figures/vm-details-hardware-network.png Binary files differdeleted file mode 100755 index a4158440..00000000 --- a/help/virt-manager/C/figures/vm-details-hardware-network.png +++ /dev/null diff --git a/help/virt-manager/C/figures/vm-details-hardware-vcpu.png b/help/virt-manager/C/figures/vm-details-hardware-vcpu.png Binary files differdeleted file mode 100755 index db08a93c..00000000 --- a/help/virt-manager/C/figures/vm-details-hardware-vcpu.png +++ /dev/null diff --git a/help/virt-manager/C/figures/vm-details-overview.png b/help/virt-manager/C/figures/vm-details-overview.png Binary files differdeleted file mode 100755 index fb11ce0a..00000000 --- a/help/virt-manager/C/figures/vm-details-overview.png +++ /dev/null diff --git a/help/virt-manager/C/figures/vm-full-virt-media.png b/help/virt-manager/C/figures/vm-full-virt-media.png Binary files differdeleted file mode 100755 index 8ba3321c..00000000 --- a/help/virt-manager/C/figures/vm-full-virt-media.png +++ /dev/null diff --git a/help/virt-manager/C/figures/vm-graphic-console.png b/help/virt-manager/C/figures/vm-graphic-console.png Binary files differdeleted file mode 100755 index 11ef34c7..00000000 --- a/help/virt-manager/C/figures/vm-graphic-console.png +++ /dev/null diff --git a/help/virt-manager/C/figures/vm-manager-window.png b/help/virt-manager/C/figures/vm-manager-window.png Binary files differdeleted file mode 100755 index 16ab33c8..00000000 --- a/help/virt-manager/C/figures/vm-manager-window.png +++ /dev/null diff --git a/help/virt-manager/C/figures/vm-paravirt-media.png b/help/virt-manager/C/figures/vm-paravirt-media.png Binary files differdeleted file mode 100755 index d551811d..00000000 --- a/help/virt-manager/C/figures/vm-paravirt-media.png +++ /dev/null diff --git a/help/virt-manager/C/figures/vm-preferences.png b/help/virt-manager/C/figures/vm-preferences.png Binary files differdeleted file mode 100755 index 6986111d..00000000 --- a/help/virt-manager/C/figures/vm-preferences.png +++ /dev/null diff --git a/help/virt-manager/C/legal.xml b/help/virt-manager/C/legal.xml deleted file mode 100644 index ac97e1de..00000000 --- a/help/virt-manager/C/legal.xml +++ /dev/null @@ -1,76 +0,0 @@ - <legalnotice id="legalnotice"> - <para> - Permission is granted to copy, distribute and/or modify this - document under the terms of the GNU Free Documentation - License (GFDL), Version 1.1 or any later version published - by the Free Software Foundation with no Invariant Sections, - no Front-Cover Texts, and no Back-Cover Texts. You can find - a copy of the GFDL at this <ulink type="help" - url="ghelp:fdl">link</ulink> or in the file COPYING-DOCS - distributed with this manual. - </para> - <para> This manual is part of a collection of GNOME manuals - distributed under the GFDL. If you want to distribute this - manual separately from the collection, you can do so by - adding a copy of the license to the manual, as described in - section 6 of the license. - </para> - - <para> - Many of the names used by companies to distinguish their - products and services are claimed as trademarks. Where those - names appear in any GNOME documentation, and the members of - the GNOME Documentation Project are made aware of those - trademarks, then the names are in capital letters or initial - capital letters. - </para> - - <para> - DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED - UNDER THE TERMS OF THE GNU FREE DOCUMENTATION LICENSE - WITH THE FURTHER UNDERSTANDING THAT: - - <orderedlist> - <listitem> - <para>DOCUMENT IS PROVIDED ON AN "AS IS" BASIS, - WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR - IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES - THAT THE DOCUMENT OR MODIFIED VERSION OF THE - DOCUMENT IS FREE OF DEFECTS MERCHANTABLE, FIT FOR - A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE - RISK AS TO THE QUALITY, ACCURACY, AND PERFORMANCE - OF THE DOCUMENT OR MODIFIED VERSION OF THE - DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR - MODIFIED VERSION PROVE DEFECTIVE IN ANY RESPECT, - YOU (NOT THE INITIAL WRITER, AUTHOR OR ANY - CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY - SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER - OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS - LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED - VERSION OF THE DOCUMENT IS AUTHORIZED HEREUNDER - EXCEPT UNDER THIS DISCLAIMER; AND - </para> - </listitem> - <listitem> - <para>UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL - THEORY, WHETHER IN TORT (INCLUDING NEGLIGENCE), - CONTRACT, OR OTHERWISE, SHALL THE AUTHOR, - INITIAL WRITER, ANY CONTRIBUTOR, OR ANY - DISTRIBUTOR OF THE DOCUMENT OR MODIFIED VERSION - OF THE DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH - PARTIES, BE LIABLE TO ANY PERSON FOR ANY - DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR - CONSEQUENTIAL DAMAGES OF ANY CHARACTER - INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS - OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR - MALFUNCTION, OR ANY AND ALL OTHER DAMAGES OR - LOSSES ARISING OUT OF OR RELATING TO USE OF THE - DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT, - EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF - THE POSSIBILITY OF SUCH DAMAGES. - </para> - </listitem> - </orderedlist> - </para> - </legalnotice> - diff --git a/help/virt-manager/C/virt-manager-C.omf b/help/virt-manager/C/virt-manager-C.omf deleted file mode 100644 index ed92f8f8..00000000 --- a/help/virt-manager/C/virt-manager-C.omf +++ /dev/null @@ -1,27 +0,0 @@ -<?xml version="1.0" standalone="no"?> -<omf> - <resource> - <creator> - hbrock@redhat.com (Hugh Brock) - </creator> - <title> - Virtual Machine Manager Manual - </title> - <date> - 2007-03-01 - </date> - <version identifier="0.0.1" date="2007-03-01" description="First Release"/> - <subject category="System"/> - <description> - This is the manual for the Virtual Machine Manager application. - </description> - <type> - manual - </type> - <format mime="text/xml" dtd="-//OASIS//DTD DocBook XML V4.1.2//EN"/> - <identifier url="file:///usr/share/gnome/help/virt-manager/C/virt-manager.xml"/> - <language code="C"/> - <relation seriesid="37dd0df4-cd98-11db-8f4f-fd6860e92e9b"/> - <rights type="GNU FDL" license.version="1.1" license="http://www.gnu.org/licenses/fdl.html" holder="Red Hat Inc., and Hugh Brock"/> - </resource> -</omf> diff --git a/help/virt-manager/C/virt-manager.xml b/help/virt-manager/C/virt-manager.xml deleted file mode 100644 index 50f64891..00000000 --- a/help/virt-manager/C/virt-manager.xml +++ /dev/null @@ -1,1040 +0,0 @@ -<?xml version="1.0"?> -<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" - "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [ - <!ENTITY appversion "0.3.0"> - <!ENTITY manrevision "0.1"> - <!ENTITY date "March 2007"> - <!ENTITY app "virt-manager"> -]> -<!-- - (Do not remove this comment block.) - Template Maintained by the GNOME Documentation Project: - http://developer.gnome.org/projects/gdp - Template version: 2.0 beta - Template last modified Feb 12, 2002 ---> - - -<!-- - (Do not remove this comment block.) - Version: 0.0.1 - Last modified: March 2, 2007 - Maintainers: - Hugh Brock <hbrock@redhat.com> - Dan Berrange <berrange@redhat.com> - Translators: - (translators put your name and email here) ---> - - - -<!-- =============Document Header ============================= --> -<article id="index" lang="en"> - <!-- please do not change the id; for translations, change lang to --> - <!-- appropriate code --> - - <articleinfo> - <title>Virtual Machine Manager Manual</title> - <copyright> - <year>2007</year> - <holder>Red Hat Inc., and Hugh Brock</holder> - </copyright> - - <!-- translators: uncomment this: - - <copyright> - <year>2000</year> - <holder>ME-THE-TRANSLATOR (Latin translation)</holder> - </copyright> - - --> - <!-- An address can be added to the publisher information. If a role is - not specified, the publisher/author is the same for all versions of the - document. --> - <publisher> - <publishername> Red Hat Inc. </publishername> - </publisher> - - <authorgroup> - <author> - <firstname>Hugh</firstname> - <surname>Brock</surname> - <affiliation> - <orgname>Red Hat Inc.</orgname> - <address> <email>hbrock@redhat.com</email> </address> - </affiliation> - </author> - <author> - <firstname>Daniel</firstname> - <surname>Berrange</surname> - <affiliation> - <orgname>Red Hat Inc.</orgname> - <address> <email>berrange@redhat.com</email> </address> - </affiliation> - </author> - <!-- This is appropriate place for other contributors: translators, - maintainers, etc. Commented out by default. - <othercredit role="translator"> - <firstname>Latin</firstname> - <surname>Translator 1</surname> - <affiliation> - <orgname>Latin Translation Team</orgname> - <address> <email>translator@gnome.org</email> </address> - </affiliation> - <contrib>Latin translation</contrib> - </othercredit> - --> - </authorgroup> - - <!-- The revision numbering system for GNOME manuals is as follows: --> - <!-- * the revision number consists of two components --> - <!-- * the first component of the revision number reflects the release version of the GNOME desktop. --> - <!-- * the second component of the revision number is a decimal unit that is incremented with each revision of the manual. --> - <!-- For example, if the GNOME desktop release is V2.x, the first version of the manual that --> - <!-- is written in that desktop timeframe is V2.0, the second version of the manual is V2.1, etc. --> - <!-- When the desktop release version changes to V3.x, the revision number of the manual changes --> - <!-- to V3.0, and so on. --> - - <revhistory> - <revision> - <revnumber>&app; Man=ual V&manrevision;</revnumber> - <date>&date;</date> - <revdescription> - <para role="author">Hugh Brock - <email>hbrock@redhat.com</email> - </para> - <para role="publisher">Red Hat Inc.</para> - </revdescription> - </revision> - </revhistory> - <releaseinfo>This manual describes how to manage virtual machines - with the Virtual Machine Manager program. - </releaseinfo> - <legalnotice> - <title>Feedback</title> - <para>To report a bug or make a suggestion regarding this package or - this manual, follow the directions at the - <ulink url="http://virt-manager.org" - type="http">virt-manager website</ulink>. - </para> - <!-- Translators may also add here feedback address for translations --> - </legalnotice> - </articleinfo> - - <!-- ============= Document Body ============================= --> - <!-- ============= Introduction ============================== --> - <sect1 id="virt-manager-intro"> - <title>Introduction</title> - - <sect2 id="virt-manager-about-vm"> - <title>About <application>&app;</application></title> - <indexterm> - <primary>virt-manager</primary> - <secondary>About</secondary> - </indexterm> - <para> - <application>&app;</application> is a GUI tool for managing virtual - machines (VMs). It helps you create, destroy, edit, monitor, save, restore, - pause, and use the console on virtual machines running on multiple - hypervisors (and, soon, multiple physical hosts). Because - <application>&app;</application> relies entirely on - <application>libvirt</application> (<ulink type="http" - url="http://libvirt.org">http://libvirt.org</ulink>), the platform- and - hypervisor-independent virtualization library, it is insulated from - hypervisor API changes and virtualization system changes. - </para> - <para> - <application>&app;</application> is released under the GNU General Public - License. Contributions of source code patches are welcome and encouraged - at <ulink type="http" - url="http://virt-manager.org">virt-manager.org</ulink>, where you will - also find plans for future development. - </para> - </sect2> - <sect2 id="virt-manager-about-doc"> - <title>About this Document</title> - <para> - This document is released under the Open Publication License v - 1.0. Corrections are welcome and encouraged at <ulink type="http" - url="http://virt-manager.org">virt-manager.org</ulink>. - </para> - </sect2> - </sect1> - - <sect1 id="virt-manager-getting-started"> - <title>Getting Started</title> - - <para> - This section describes the different ways to start - <application>&app;</application>, the command-line options that are - available, and the various options in the Connection window. - </para> - <sect2 id="virt-manager-starting"> - <title>Starting virt-manager</title> - <para>You can start - virt-manager from the Applications menu or from the command - line</para> - <variablelist> - <varlistentry> - From the <term><guimenu>Applications</guimenu> menu</term>: - <listitem> - <para>Choose <menuchoice><guisubmenu>System - Tools</guisubmenu><guimenuitem>Virtual Machine Manager</guimenuitem></menuchoice>. </para> - </listitem> - </varlistentry> - <varlistentry> - From the <term>command line</term>: - <listitem> - <para>Execute the following command: <command>virt-manager</command></para> - </listitem> - </varlistentry> - </variablelist> - </sect2> - - <sect2 id="virt-manager-conn-window"> - <title>The Connection Window</title> - <para>The connection window - lets you choose the type of hypervisor to connect to, and also - whether to connect locally or to a remote machine.</para> - <para>When you start <application>&app;</application>, the following window is displayed:</para> - - <figure id="virt-manager-FIG-connection-window"> - <title>Connection Window</title> - <screenshot> - <mediaobject> - <imageobject> - <imagedata fileref="figures/vm-connection-window.png" format="PNG"/> - </imageobject> - <textobject> <phrase>Shows &app; connection window.</phrase> - </textobject> - </mediaobject> - </screenshot> - </figure> - - <para>The Connection Window contains the following - elements: </para> - <variablelist> - <varlistentry> <term>Hypervisor pull-down</term> - <listitem> - <para>The Hypervisor pull-down lets you choose a supported hypervisor to - connect to. The hypervisor must be started before you can connect to it.</para> - </listitem> - </varlistentry> - <varlistentry> <term>"Host Type" radio buttons</term> - <listitem> - <para>The "Host Type" radio buttons let you choose whether to connect to - a hypervisor on the local physical host, or (soon) a hypervisor on a - remote physical host.</para> - </listitem> - <listitem> - <para>The "Host" box lets you enter the hostname of a remote host to - connect to.</para> - </listitem> - </varlistentry> - <varlistentry> <term>Read-only connection</term> - <listitem> - <para>Checking "Read-only connection" will allow you to - monitor a hypervisor's virtual machines, but not make any changes to - them. If you are running as an unprivileged user, you may only be able - to connect to certain hypervisors read-only.</para> - </listitem> - </varlistentry> - </variablelist> - </sect2> - <sect2 id="virt-manager-CLI-opts"> - <title>Command-line Options</title> - <para>If you run &app; from the command line, you can specify a hypervisor - URI to connect to, bypassing the Connection Window. You can also make - specific &app; windows appear using the command line, if you have already - established a connection to a hypervisor. The command line options are:</para> - <itemizedlist> - <listitem><para><command>-h, --help</command>: show command line help and exit</para> - </listitem> - <listitem> - <para><command>--profile=FILE</command>: Generate runtime performance profile stats</para> - </listitem> - <listitem> - <para><command>-c URI, --connect=URI</command>: Connect to hypervisor at - URI</para> - </listitem> - <listitem> - <para><command>--no-dbus</command>: Disable DBus service for controlling - UI</para> - </listitem> - <listitem> - <para><command>--show-domain-creator</command>: Create a new virtual - machine</para> - </listitem> - <listitem> - <para><command>--show-domain-editor=UUID</command>: Edit a domain - configuration</para> - </listitem> - <listitem> - <para><command>--show-domain-performance=UUID</command>: Show a domain - performance</para> - </listitem> - <listitem> - <para><command>--show-domain-console=UUID</command>: Show a domain - console</para> - </listitem> - <listitem> - <para><command>--show-host-summary</command>: Show a host summary</para> - </listitem> - </itemizedlist> - <note> - <title>Hypervisor URIs and the test hypervisor</title> <para>To connect to - a local Xen hypervisor, the URI is simply "xen" (the - default). To connect to a local QEMU session, the URI is - "qemu:///session". There is also a test hypervisor that is - handy if you are trying to test a new &app; feature you have added. Its - URI is "test:///default".</para> - </note> - </sect2> - </sect1> - - <sect1 id="virt-manager-mgr-window"> - <title>The Manager Window</title> - <para>The manager window gives you a quick snapshot of the virtual machines - that are available on your physical host. It displays both the virtual - machines that are actually running - on your physical host, and also the virtual machines for which it finds - config information even though they are not running. For running virtual - machines, the manager window displays the resources those running VMs are - consuming. The manager window is customizable as described below.</para> - - <figure id="virt-manager-FIG-mgr-window"> - <title>Manager Window</title> - <screenshot> - <mediaobject> - <imageobject> - <imagedata fileref="figures/vm-manager-window.png" format="PNG"/> - </imageobject> - <textobject> <phrase>Shows a typical Manager Window.</phrase> - </textobject> - </mediaobject> - </screenshot> - </figure> - - <sect2 id="virt-manager-vm-list"> - <title>The Virtual Machine List</title> - <para>The manager window is dominated by a list of the virtual machines on your - physical host. By default, the list has six columns of information:</para> - <variablelist> - <varlistentry><term>ID</term> - <listitem> - <para>The arbitrarily assigned ID number for the - virtual machine. Guaranteed unique only while a virtual machine is - running, and only to that particular host.</para> - </listitem> - </varlistentry> - <varlistentry><term>Name</term> - <listitem> - <para>The name of the virtual machine. Like the ID, guaranteed unique - only among running virtual machines on a particular host.</para> - </listitem> - </varlistentry> - <varlistentry><term>Status</term> - <listitem> - <para>The virtual machine's status. One of <guilabel>Running</guilabel>, - <guilabel>Paused</guilabel>, <guilabel>Shutdown</guilabel>, - <guilabel>Shutoff</guilabel>, or <guilabel>Crashed</guilabel>.</para> - </listitem> - </varlistentry> - <varlistentry><term>CPU Usage</term> - <listitem> - <para>The virtual machine's CPU usage, as a percentage of total CPU - usage and as a running graph.</para> - </listitem> - </varlistentry> - <varlistentry><term>VCPUs</term> - <listitem> - <para>The number of VCPUs currently assigned to the VM. This - allocation can be changed on the fly for paravirtualized - VMs.</para> - </listitem> - </varlistentry> - <varlistentry><term>Memory Usage</term> - <listitem> - <para>The amount of memory allocated to the virtual machine, and the percentage - of total physical RAM on the host that the virtual machine is actually - using (the percentage will be zero if the VM is not currently - running). Note: The amount of memory for a virtual machine is the - amount it is currently allocated, not the maximum it could be - allocated. See the help for the <xref linkend="virt-manager-details-window"/>. - </para> - </listitem> - </varlistentry> - </variablelist> - </sect2> - <sect2 id="virt-manager-file-menu"> - <title>File Menu Choices</title> - <para>The File menu in the Manager window gives you the following - options:</para> - <variablelist> - <varlistentry><term>New machine...</term> - <listitem><para>Starts the virtual machine creation wizard. Clicking the - <guibutton>New</guibutton> button at the bottom of the window has the - same effect.</para> - </listitem> - </varlistentry> - <varlistentry><term>Restore saved machine...</term> - <listitem><para>Restores a previously saved virtual machine. You must - choose the memory image of a previously saved virtual machine in the - dialog that will follow.</para> - </listitem> - </varlistentry> - <varlistentry><term>Open connection...</term> - <listitem><para>Brings up the connection window again. You can connect to - multiple hypervisors at the same time with - <application>&app;</application>. At this writing opening a new - connection brings up a new manager window; soon the manager window will - display multiple connections to multiple machines.</para> - </listitem> - </varlistentry> - <varlistentry><term>Close</term> - <listitem><para>Closes the Manager window. Any other - <application>&app;</application> windows you have open will remain open.</para> - </listitem> - </varlistentry> - <varlistentry><term>Quit</term> - <listitem><para>Closes the Manager window and any other open windows and - stops the application. Note that any virtual machines running on the - host will continue running regardless of whether - <application>&app;</application> is running or not. - </para> - </listitem> - </varlistentry> - </variablelist> - </sect2> - <sect2 id="virt-manager-edit-menu"> - <title>Edit Menu Choices</title> - <para>The choices on the <guimenu>Edit</guimenu> menu are for working with - a specific machine, or for changing <application>&app;</application> - preferences.</para> - <variablelist> - <varlistentry><term>Machine details...</term> - <listitem><para>Opens the Details window for the virtual machine you have - highlighted in the list.</para> - </listitem> - </varlistentry> - <varlistentry><term>Delete machine</term> - <listitem><para>Deletes the configuration of an inactive virtual machine you have - highlighted in the list. Note that this does not touch the virtual - machine's disk storage.</para> - </listitem> - </varlistentry> - <varlistentry><term>Preferences</term> - <listitem><para>Brings up the <xref linkend="virt-manager-pref-window"/></para> - </listitem> - </varlistentry> - </variablelist> - </sect2> - <sect2 id="virt-manager-view-menu"> - <title>View Menu Choices</title> - <para>The View Menu choices toggle on and off the virtual machine list - columns that are described above.</para> - </sect2> - </sect1> - - <sect1 id="virt-manager-details-window"> - <title>The Details Window</title> <para>On its Overview tab, the details - window gives you a large view of the CPU and memory usage of a virtual - machine. On a separate Hardware tab, it provides you with the details of the - virtual hardware assigned to the machine. With sufficient privileges, you - can add or remove CPUs, add or remove memory, and (soon) add and remove - block devices and network devices. Finally, menu items allow you to pause - and resume virtual machines, save a virtual machine to disk, and bring up - the serial or graphical console for a virtual machine.</para> - - <sect2 id="virt-manager-details-window-menu"> - <title>Details Window Menus</title> - <para>The menus in the Details window and the <link - linkend="virt-manager-console-window">Console window</link> are very - similar. The <guimenu>Virtual Machine</guimenu> menu gives you the - following options:</para> - <variablelist> - <varlistentry><term>Run</term> - <listitem><para><guisubmenu>Run</guisubmenu> starts the virtual machine, - if it isn't already running. The <guibutton>Run</guibutton> button on - the toolbar does the same thing.</para> - </listitem> - </varlistentry> - <varlistentry><term>Pause</term> - <listitem><para><guisubmenu>Pause</guisubmenu> freezes the virtual - machine, if it is running at the time. To unfreeze the machine, choose - <guisubmenu>Pause</guisubmenu> again. The <guibutton>Pause</guibutton> - button on the toolbar does the same thing.</para> - </listitem> - </varlistentry> - <varlistentry><term>Shutdown</term> - <listitem><para><guisubmenu>Shutdown</guisubmenu> shuts the machine - down, if it is running. For paravirtualized VMs, the hypervisor will - attempt to gracefully shut down the VM; for fully virtualized VMs, - <guisubmenu>Shutdown</guisubmenu> is equivalent to pulling the plug on - the machine. The <guibutton>Shutdown</guibutton> button on the toolbar - serves the same purpose.</para> - </listitem> - </varlistentry> - <varlistentry><term>Save</term> - <listitem><para><guisubmenu>Save</guisubmenu> saves the machine's memory - image to disk, shutting the machine down in the process. You can then - <guisubmenu>Restore</guisubmenu> the machine from the <link - linkend="virt-manager-mgr-window">Manager window</link> later. Note - that if you really wish to preserve a VM in its saved state, you will - also need a snapshot of the VM's disk image at the time you save - it. If you start a VM that you have saved and then later attempt to - restore the same VM using the same disk image, you will probably lose - data or worse.</para> - </listitem> - </varlistentry> - <varlistentry><term>Destroy</term> - <listitem><para><guisubmenu>Destroy</guisubmenu> is akin to pulling the - plug on a machine, even for paravirtualized VMs. You may experience - data loss, or worse. However, this command is useful if you have a wedged - paravirtualized VM that you need to get rid of altogether.</para> - </listitem> - </varlistentry> - </variablelist> - <para>The <guimenu>View</guimenu> menu gives you the following - options:</para> - <variablelist> - <varlistentry><term>Graphical Console</term> - <listitem><para>The <guisubmenu>Graphical Console</guisubmenu> item pops up the - graphical console for the VM, if one is available. The availability of a - graphical console depends on whether the VM was created with graphics - support available; if it was not, only the Serial Console will be - available.</para> - </listitem> - </varlistentry> - <varlistentry><term>Serial Console</term> - <listitem><para>The <guisubmenu>Serial Console</guisubmenu> item pops up - the serial console window for the VM. It may not be available if the - VM was created with graphics support available.</para> - </listitem> - </varlistentry> - <varlistentry><term>Toolbar</term> - <listitem><para>The <guisubmenu>Toolbar</guisubmenu> item hides or shows - the toolbar with Run/Pause/Shutdown buttons</para> - </listitem> - </varlistentry> - </variablelist> - </sect2> - - <sect2 id="virt-manager-details-window-vm-info"> - <title>Details Window Overview: Basic Details</title> - - <figure id="virt-manager-FIG-details-overview"> - <title>Details Window Overview</title> - <screenshot> - <mediaobject> - <imageobject> - <imagedata fileref="figures/vm-details-overview.png" format="PNG"/> - </imageobject> - <textobject> <phrase>Shows a typical Details Window Overview tab.</phrase> - </textobject> - </mediaobject> - </screenshot> - </figure> - - <para>At the top of the Overview tab you will find the name, the UUID, and - the status of the virtual machine you are examining. These are all - read-only fields; the UUID should not change over the lifetime of the - VM, and while the name of an inactive VM can change, there is no way to - change it using <application>&app;</application> at this time. - </para> - </sect2> - - <sect2 id="virt-manager-details-performance"> - <title>Details Window Overview: Performance Information</title> - <para>The details window also displays performance information, including - the percentage of the physical host's CPU that the virtual machine is - taking up, as well as the amount of physical RAM the virtual machine is using.</para> - </sect2> - - <sect2 id="virt-manager-details-hardware"> - <title>Details Window Hardware</title> - <para>The Details Window Hardware tab lets you view and, with appropriate - permissions, change the virtual hardware allocated to a virtual - machine. This includes the number of vcpus, the amount of memory, block - devices, and network devices.</para> - <note> - <title>Virtual machine changes: Sometimes they persist, sometimes they - don't</title> - <para>The Hardware tab lets you make changes to active (running) VMs, - and inactive VMs. Changes you make to inactive VMs are saved to the VM's - config file and will persist over time. Changes you make to active VMs, - by contrast, change the current settings for a VM, but will not be saved - to the VM's config file. If you shut down a VM and restart it, it will - restart with the last saved config.</para> - </note> - </sect2> - - <sect2 id="virt-manager-details-hardware-vcpus"> - <title>Details Window Hardware: VCPUs</title> - - <figure id="virt-manager-FIG-details-hardware-vcpu"> - <title>Details Window: VCPUs</title> - <screenshot> - <mediaobject> - <imageobject> - <imagedata fileref="figures/vm-details-hardware-vcpu.png" format="PNG"/> - </imageobject> - <textobject> <phrase>Shows the VCPU pane in the Details Window.</phrase> - </textobject> - </mediaobject> - </screenshot> - </figure> - - <para>Choosing the <guilabel>Processor</guilabel> item in the list on the - left of the Hardware tab brings up the <guilabel>Processor</guilabel> - pane. This pane shows you the number of VCPUs the VM is currently using, - as well as the number of physical cpus on the host, and the maximum number - of VCPUs you can assign to this VM. If you have adequate privileges, you - can set the number of VCPUs from one up to the maximum allowed.</para> - - <note> - <title>VCPUs and paravirtualized VMs</title> - <para>You can adjust the number of VCPUs for a running paravirtualized VM - between 1 and the maximum set in the config file. It is not yet possible to - adjust the number of VCPUs in a running, fully virtualized VM. The - same limitation applies to memory adjustments (see below).</para> - </note> - - <note> - <title>Maximum VCPUs and inactive VMs</title> - <para>If you are changing the VCPUs for a running VM, you are limited - to a range from 1 to the maximum number of VCPUs in the VM's config when - it was started. On the other hand, if you change the VCPUs for an - inactive VM, you are limited only to a range from 1 to the maximum number - of VCPUs your virtualization system will support (32, for - example). Unless you have very specific reasons for doing so, it's - probably not a good idea to set the maximum VCPUs larger than the number - of physical processors on the machine, but - <application>&app;</application> will let you, and the number you set - will be saved to the inactive VM's config as both the maximum number of VCPUs, and - the current number of VCPUs.</para> - </note> - </sect2> - - <sect2 id="virt-manager-details-hardware-memory"> - <title>Details Window Hardware: Memory</title> - - <figure id="virt-manager-FIG-details-hardware-memory"> - <title>Details Window: Memory</title> - <screenshot> - <mediaobject> - <imageobject> - <imagedata fileref="figures/vm-details-hardware-memory.png" format="PNG"/> - </imageobject> - <textobject> <phrase>Shows the Memory pane in the Details Window.</phrase> - </textobject> - </mediaobject> - </screenshot> - </figure> - - <para>Choosing the - <guilabel>Memory</guilabel> item on the list on the left of the Hardware - tab brings up the <guilabel>Memory</guilabel> pane. This pane shows you the - amount of memory your VM is currently allocated, the maximum it can be - allocated, and the amount of physical RAM on the machine. With adequate - privileges, you can adjust the amount of memory your running VM is - currently using, if your VM is <term>paravirtualized</term>. (It is not - currently possible to adjust the memory allocation of a running, fully - virtualized VM.) If your VM is not running, however, it is possible to - adjust both the startup memory allocation and the maximum memory - allocation.</para> - </sect2> - - <sect2 id="virt-manager-details-disk"> - <title>Details Window Hardware: Disk</title> - - <figure id="virt-manager-FIG-details-hardware-disk"> - <title>Details Window: Disk</title> - <screenshot> - <mediaobject> - <imageobject> - <imagedata fileref="figures/vm-details-hardware-disk.png" format="PNG"/> - </imageobject> - <textobject> <phrase>Shows the Disk pane in the Details Window.</phrase> - </textobject> - </mediaobject> - </screenshot> - </figure> - - <para>Choosing the <guilabel>Disk</guilabel> item on the list on the left - of the Hardware tab displays the <guilabel>Disk</guilabel> pane. This - displays all the virtual block devices your VM is aware of. In the future - this pane will offer UI for adding and removing virtual block devices for a - VM. - </para> - </sect2> - - <sect2 id="virt-manager-details-network"> - <title>Details Window Hardware: Network</title> - - <figure id="virt-manager-FIG-details-hardware-network"> - <title>Details Window: Network</title> - <screenshot> - <mediaobject> - <imageobject> - <imagedata fileref="figures/vm-details-hardware-network.png" format="PNG"/> - </imageobject> - <textobject> <phrase>Shows the Network pane in the Details Window.</phrase> - </textobject> - </mediaobject> - </screenshot> - </figure> - - <para>Choosing the <guilabel>Network</guilabel> item on the list on the - left of the Hardware tab displays the <guilabel>Network</guilabel> - pane. This displays all the virtual network devices your VM is aware - of. In the future this pane will offer UI for adding and removing virtual - block devices for a VM.</para> - </sect2> - </sect1> - - <sect1 id="virt-manager-console-window"> - <title>The Console Window</title> - <para>The Console window connects you to a VM's console, either in text mode - or graphically depending on how the VM was installed.</para> - - <figure id="virt-manager-FIG-console-window"> - <title>Graphical Console Window</title> - <screenshot> - <mediaobject> - <imageobject> - <imagedata fileref="figures/vm-graphic-console.png" format="PNG"/> - </imageobject> - <textobject> <phrase>Shows a graphical console window.</phrase> - </textobject> - </mediaobject> - </screenshot> - </figure> - - <sect2 id="virt-manager-console-menus"> - <title>Console Window Menus</title> - <para>The menus for the Console window are identical to those for the <link - linkend="virt-manager-details-window-menu">Details window</link>, with - the following exceptions:</para> - <itemizedlist> - <listitem><para>The <guimenu>Virtual Machine</guimenu> menu adds an item - <guimenuitem>Take Screenshot</guimenuitem> that lets you grab a - screenshot of the VM's console.</para> - </listitem> - <listitem><para>The <guimenu>View</guimenu> menu adds an item - <guimenuitem>Fullscreen</guimenuitem> that will enlarge the Console window - to take up an entire screen, if you are using the graphical - console.</para> - </listitem> - </itemizedlist> - </sect2> - <sect2 id="virt-manager-console-tips"> - <title>Console Window Tips</title> - <para>Some useful things to know about using the Console window:</para> - <itemizedlist> - <listitem> - <para>If you click your mouse anywhere in the graphical console window, - the window will "grab" it and pop up a warning informing you it has done - so. You can then use the mouse normally inside the console window. To - "break out" of the window, press the key combination - <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap> - </keycombo>.</para> - </listitem> - <listitem> - <para>As of now, it is not possible to change the size of the console - window. This capability depends on upstream work, although it should be - available in a future release.</para> - </listitem> - </itemizedlist> - </sect2> - </sect1> - - <sect1 id="virt-manager-preferences-window"> - <title>The Preferences Window</title> - <para>The Preferences window lets you customize certain of the application's - behaviors. You can choose how frequently VM statistics are updated in the - Manager and Details windows, choose the circumstances under which a console - automatically appears, and finally choose how the console grabs your - keyboard input.</para> - - <figure id="virt-manager-FIG-preferences-window"> - <title>Preferences Window</title> - <screenshot> - <mediaobject> - <imageobject> - <imagedata fileref="figures/vm-preferences.png" format="PNG"/> - </imageobject> - <textobject> <phrase>Shows a preferences window.</phrase> - </textobject> - </mediaobject> - </screenshot> - </figure> - - <sect2 id="virt-manager-pref-window-stats-refresh"> - <title>Preferences: Status Monitoring</title> - <para>Here you can set how often your VM status graphs update. If you have - a large number of VMs, you may want to consider increasing the interval in - between status updates.</para> - </sect2> - - <sect2 id="virt-manager-pref-window-consoles"> - <title>Preferences: Console Pop-up</title> <para>Here you can set the - circumstances where you want <application>&app;</application> to pop up a - Console window. The choices are:</para> - <variablelist> - <varlistentry><term>For all domains</term> - <listitem><para>Pop up a Console window whenever a VM starts, including when - <application>&app;</application> first starts up. This can be useful if - you need to be sure you see what is happening right when starting a VM, - but it's probably overkill for most situations.</para> - </listitem> - </varlistentry> - <varlistentry><term>For new domains</term> - <listitem><para>Pop up a Console window whenever a newly created domain - starts. This is the default behavior; the application pops up a Console - window for a newly created guest so that you can continue the guest - install.</para> - </listitem> - </varlistentry> - <varlistentry><term>Never</term> - <listitem><para>Never pop up a Console window automatically. With this - choice you will have to manually start a Console window for any domain - you want to connect to, by double-clicking on the domain in the <link - linkend="virt-manager-mgr-window">Manager window</link>.</para> - </listitem> - </varlistentry> - </variablelist> - </sect2> - - <sect2 id="virt-manager-pref-window-grab-kbd"> - <title>Preferences: Grab Keyboard</title> - <para>By default the Console window will grab input from your keyboard - whenever you position your mouse pointer over it. You may also choose - <guimenuitem>When fullscreen</guimenuitem> to grab keyboard input only - when the Console window is full screen, or - <guimenuitem>Never</guimenuitem>. - </para> - </sect2> - </sect1> - - <sect1 id="virt-manager-create-wizard"> - <title>The Create Wizard</title> - <para>The Create Wizard helps you gather the information necessary to create - new virtual machines. All the information in each screen is retained and can - be backed-up-to and modified until you click <guibutton>Finish</guibutton> - on the last screen.</para> - <sect2 id="virt-manager-system-name"> - <title>The System Name screen</title> - <para>Choose a name for your virtual system. The name must be non-blank, - alphanumeric (plus underscores), contain at least one letter, and be less - than 50 characters.</para> - </sect2> - - <sect2 id="virt-manager-virt-method"> - <title>The Virtualization Method screen</title> - <para>Choose a virtualization method for your new system. The choices - are:</para> - <variablelist> - <varlistentry><term>Paravirtualized</term> <listitem><para>A - paravirtualized system typically performs better than a fully virtualized - system because certain operations — disk and network access, for - example — have direct access to the hardware. However a - paravirtualized VM requires a specially modified kernel. If you - choose paravirtualized, you must make sure this specially modified kernel - is available for the operating system you wish to install.</para> - </listitem> - </varlistentry> - <varlistentry><term>Fully Virtualized</term> - <listitem> - <para>A fully virtualized system simulates all the hardware for the VM, - permitting no direct access. It allows for a greater range of operating - systems, but generally will not perform as well as a paravirtualized - system. Note that for some hypervisor types, full virtualization requires - hardware support. In addition if your hardware allows it, you can - enable hardware acceleration for your fully virtualized guest (this - item will be grayed out unless your hardware is acceleration-capable).</para> - </listitem> - </varlistentry> - </variablelist> - </sect2> - - <sect2 id="virt-manager-installation-media"> - <title>The Installation Media screens</title> - <para>The Installation Media screens let you specify where the physical or - virtual install media for your VM are located, so that the installer can - find them. There are two screens, one for each type of virtual - machine.</para> - <sect3 id="virt-manager-installation-media-paravirt"> - <title>Paravirtualized installation media</title> - <figure id="virt-manager-FIG-paravirt-media"> - <title>Choose Install Media for Paravirtualized VMs</title> - <screenshot> - <mediaobject> - <imageobject> - <imagedata fileref="figures/vm-paravirt-media.png" format="PNG"/> - </imageobject> - <textobject> <phrase>Shows the paravirtualized VM media choice window.</phrase> - </textobject> - </mediaobject> - </screenshot> - </figure> - <para>A paravirtualized VM requires an install tree that follows the - pattern of the Fedora install tree (e.g. <ulink type="http" - url="http://download.fedora.redhat.com/pub/fedora/linux/core/6/i386/os/"> - this tree</ulink>). The <guilabel>Install Media URL</guilabel> box lets - you enter a URL for a tree like this. When you then go to install the - guest, the installer will check to see if the URL you entered is - readable, and if so download the paravirtualized install kernel and - initrd that it will need to start the install. You can use the following - URL types:</para> - <variablelist> - <varlistentry><term>http:</term> - <listitem><para>e.g. <userinput>http://download.fedora.redhat.com/pub/fedora/linux/core/6/i386/os/</userinput></para> - </listitem> - </varlistentry> - <varlistentry><term>ftp:</term> - <listitem><para>e.g. <userinput>ftp://download.fedora.redhat.com/pub/fedora/linux/core/6/i386/os/</userinput></para> - </listitem> - </varlistentry> - <varlistentry><term>nfs:</term> - <listitem><para>e.g. <userinput>nfs:myfileserver:/images/linux/core/6/i386/os/</userinput></para> - </listitem> - </varlistentry> - <varlistentry><term>local file:</term> - <listitem><para>e.g. <userinput>/tmp/paravirttrees/fedora/os</userinput> - </para> - </listitem> - </varlistentry> - </variablelist> - <para>You can specify a kickstart URL for your paravirtualized VM in - exactly the same way as the install tree described - above. <application>&app;</application> will remember the last 5 URLs you - enter in these windows, so if you are installing multiple VMs you will - not have to type the URLs more than once. - </para> - </sect3> - <sect3 id="virt-manager-installation-media-full-virt"> - <title>Fully Virtualized Installation Media</title> - <figure id="virt-manager-FIG-full-virt-media"> - <title>Choose Install Media for Fully Virtualized VMs</title> - <screenshot> - <mediaobject> - <imageobject> - <imagedata fileref="figures/vm-full-virt-media.png" format="PNG"/> - </imageobject> - <textobject> <phrase>Shows the fully virtualized VM media choice window.</phrase> - </textobject> - </mediaobject> - </screenshot> - </figure> - <para>A fully virtualized VM requires the standard installation media that - the same non-virtualized OS would require: either an actual CD or DVD, or - a corresponding ISO image. On the Installation Media screen for a fully - virtualized VM, you can therefore choose the path to your CD or DVD from - the pull-down list, or you can enter or browse to the path of the ISO - image you have saved in your local filesystem.</para> - <para>For fully virtualized VMs, <application>&app;</application> also - asks for the operating system type and variant you are installing. The - installer uses this to set the <parameter>acpi</parameter> and - <parameter>apic</parameter> flags according to the OS type (other - parameters may be added to this list in the future).</para> - </sect3> - </sect2> - - <sect2 id="virt-manager-storage-space"> - <title>Assigning Storage Space</title> - <figure id="virt-manager-FIG-assign-storage"> - <title>Assign Storage</title> - <screenshot> - <mediaobject> - <imageobject> - <imagedata fileref="figures/vm-assign-storage.png" format="PNG"/> - </imageobject> - <textobject> <phrase>Shows the Assigning Storage window.</phrase> - </textobject> - </mediaobject> - </screenshot> - </figure> - - <para>Designate the primary storage device for your VM. You may choose an - existing physical or LVM partition in the <guilabel>Partition</guilabel> - box; or, you may choose to use a file on the local filesystem. If you - choose to use a file that does not already exist, you may specify the size - of the file in megabytes. If you choose an existing file, that file's size - will not change. If you use a file for your primary storage device, you - may also choose whether to allocate the entire file - at creation time, or whether to allow it to grow to its maximum over - time.</para> - <warning> - <title>Sparse files can be dangerous</title> - <para>You may be tempted not to allocate your entire file when your VM is - created; filling a 5- to 10-GB file with 0s can take quite a while, and - you will avoid this wait by not allocating the entire file and instead using a - "sparse" file. However, be aware that this will slow down your VM's disk - performance significantly, as the underlying OS must keep allocating more - storage space as your VM runs. In addition, if the disk your sparse file - is on runs out of space, your VM may crash and lose data. You may - therefore only want to use a sparse file when testing, where guest - creation speed could be at a premium.</para> - </warning> - </sect2> - - <sect2 id="virt-manager-memory-and-cpu"> - <title>Allocate Memory And CPU</title> - <figure id="virt-manager-FIG-mem-cpu"> - <title>Set Memory and CPU</title> - <screenshot> - <mediaobject> - <imageobject> - <imagedata fileref="figures/vm-create-mem-cpu.png" format="PNG"/> - </imageobject> - <textobject> <phrase>Shows the VM Memory and CPU choice window.</phrase> - </textobject> - </mediaobject> - </screenshot> - </figure> - <para>The <guilabel>Memory</guilabel> section of this screen lets you set - two parameters, <guilabel>VM Max Memory</guilabel> and <guilabel>VM - Startup Memory</guilabel>. These settings work as follows:</para> - <variablelist> - <varlistentry><term>VM Max Memory</term> <listitem><para><guilabel>VM Max - Memory</guilabel> sets the maximum memory your VM can have unless you - reboot it with a higher setting. For paravirtualized VMs, the maximum - memory is a boot-time kernel setting; for fully virtualized VMs, the - maximum memory appears to the VM to be the amount of physical memory - available.</para> - </listitem> - </varlistentry> - <varlistentry><term>VM Startup Memory</term> - <listitem><para>For paravirtualized VMs, <guilabel>VM Startup - Memory</guilabel> sets the amount of memory to start the VM with. The - VM's available memory can then be changed from <application>&app;</application> - while the VM is running. For fully virtualized guests, this setting has - no effect.</para> - </listitem> - </varlistentry> - </variablelist> - <para>The virtual CPU section of this screen lets you set the number of - vCPUs your VM starts up with. For paravirtualized guests, this number can - be changed while the guest is running (although never to more than the VM - started with). For fully virtualized guests, this number can only be - changed while the guest is not running.</para> - </sect2> - - <sect2 id="virt-manager-validation"> - <title>Validation</title> - <para>The Validation screen lets you verify the setup for your new - system. If you need to, you can back up and - make changes. Clicking "Finish" will begin creating your virtual - machine. If you have the <application>&app;</application> preferences set - to automatically open consoles, a <link - linkend="virt-manager-console-window">Console window</link> will pop up - as soon as the installer has downloaded the necessary images and booted - the VM's installer. - </para> - </sect2> - </sect1> - -</article> - - |
