Commit b82bf86f authored by Guido Günther's avatar Guido Günther

New upstream version 1.0.1

parent 4fa03ba6
Virtual Machine Manager News
============================
Release 1.0.1 (March 22, 2014)
------------------------------
- virt-install/virt-xml: New --memorybacking option (Chen Hanxiao)
- virt-install/virt-xml: New --memtune option (Chen Hanxiao)
- virt-manager: UI for LXC <idmap> (Chen Hanxiao)
- virt-manager: gsettings key to disable keygrab (Kjö Hansi Glaz)
- virt-manager: Show domain state reason in the UI (Giuseppe Scrivano)
- Fix a number of bugs found since the 1.0.0 release
Release 1.0.0 (February 14, 2014)
---------------------------------
- virt-manager: Snapshot support
- New tool virt-xml: Edit libvirt XML in one shot from the command line
- Improved defaults: qcow2, USB2, host CPU model, guest agent channel,
...
- Introspect command line options like --disk=? or --network=help
- The virt-image tool will be removed before the next release, speak up
if you have a good reason not to remove it.
- virt-manager: Support arm vexpress VM creation
- virt-manager: Add guest memory usage graphs (Thorsten Behrens)
- virt-manager: UI for editing <filesystem> devices (Cédric Bosdonnat)
- Spice USB redirection support (Guannan Ren)
- <tpm> UI and command line support (Stefan Berger)
- <rng> UI and command line support (Giuseppe Scrivano)
- <panic> UI and command line support (Chen Hanxiao)
- <blkiotune> command line support (Chen Hanxiao)
- virt-manager: support for glusterfs storage pools (Giuseppe Scrivano)
- cli: New options --memory, --features, --clock, --metadata, --pm
- Greatly improve app responsiveness when connecting to remote hosts
- Lots of UI cleanup and improvements
Release 0.10.0 (June 19, 2013)
------------------------------
- Merged code with python-virtinst. virtinst is no longer public
......
Metadata-Version: 1.0
Name: virt-manager
Version: 0.10.0
Version: 1.0.1
Summary: UNKNOWN
Home-page: http://virt-manager.org
Author: Cole Robinson
......
No preview for this file type
......@@ -111,16 +111,20 @@
<schema id="org.virt-manager.virt-manager.stats" path="/org/virt-manager/virt-manager/stats/">
<key name="update-interval" type="i">
<default>1</default>
<default>3</default>
<summary>The statistics update interval</summary>
<description>The statistics update interval in seconds</description>
</key>
<key name="enable-cpu-poll" type="b">
<default>true</default>
<summary>Poll VM CPU stats</summary>
<description>Whether or not the app will poll VM CPU statistics</description>
</key>
<key name="enable-disk-poll" type="b">
<default>false</default>
<summary>Poll disk i/o stats</summary>
<description>Whether or not the app will poll VM disk i/o statistics</description>
</key>
<key name="enable-net-poll" type="b">
<default>false</default>
......@@ -128,7 +132,7 @@
<description>Whether or not the app will poll VM network i/o statistics</description>
</key>
<key name="enable-memory-poll" type="b">
<default>true</default>
<default>false</default>
<summary>Poll memory stats</summary>
<description>Whether or not the app will poll VM memory statistics</description>
</key>
......@@ -184,6 +188,13 @@
<description>Grab keyboard sequence for the graphical console</description>
</key>
<!--This key is not intended to be exposed in the UI yet-->
<key name="grab-keyboard" type="b">
<default>true</default>
<summary>Enable grab keyboard when active and focused</summary>
<description>Enable grab keyboard when active and focused</description>
</key>
<key name="auto-redirect" type="b">
<default>true</default>
<summary>Enable SPICE Auto USB redirection in console window</summary>
......@@ -229,7 +240,7 @@
<key name="cpu-default" type="s">
<default>'default'</default>
<summary>CPU setting to use for new VMs</summary>
<description>CPU setting to use for new VMs. Limited to VMs matching the host architecture. Possible values: default (virt-manager default), hv-default (qemu's default), host-cpu-model (just the model, not the additional features), host-model (libvirt's host-model setting).</description>
<description>CPU setting to use for new VMs. Limited to VMs matching the host architecture. Possible values: default (virt-manager default), hv-default (qemu's default), host-model-only (just the model, not the additional features), host-model (libvirt's host-model setting).</description>
</key>
</schema>
......
......@@ -2,36 +2,29 @@
=head1 NAME
virt-convert - convert virtual machines between formats
virt-convert - convert ovf/vmx to native libvirt guests
=head1 SYNOPSIS
B<virt-convert> [OPTION]... INPUT.VMX|INPUT-DIR [OUTPUT.XML|OUTPUT-DIR]
B<virt-convert> INPUT.vmx|INPUT.ovf|INPUT-DIR|INPUT.zip [OPTIONS]
=head1 DESCRIPTION
B<virt-convert> is a command line tool for converting virtual machines
from one format to another. Pass in either a VM definition file (such
as VMWare vmx format) or a directory containing a VM. By default, a new
VM definition file, and converted disk images, will be placed in a new
output directory.
B<virt-convert> is a command line tool for converting VMX of OVF virtual
machines to native libvirt XML. Disk format conversion can also be done
at the same time.
If an output directory is specified, it will be created if necessary,
and the output VM definition placed within, along with any disk images
as needed.
The simplest invocation is simply: virt-convert INPUT. INPUT might be
a .vmx or .ovf file, a directory containing a .vmx or .ovf file (and
likely 1 or more disk images), or an appliance archive like .zip, .tar.gz,
or .ova. virt-convert will try to do the right thing in each case.
If an output VM definition file is specified, it will be created
alongside any disks in the same directory.
By default, the virt-convert will convert all encountered disk images
to 'raw' format, sending the output to a new directory location. So the
original disk images are _not_ altered in place.
=head1 OPTIONS
Any of the options can be omitted, in which case B<virt-convert> will
use defaults when required. An input VM definition or containing directory
must be provided. By default, an output directory is generated based upon
the name of the VM. The default input format is VMWare vmx, and the
default output format is a libvirt "image" XML definition
(see L<virt-image(5)>).
=over 4
=item -h, --help
......@@ -42,68 +35,50 @@ Show the help message and exit
Show program's version number and exit
=item --connect=URI
Connect to a non-default hypervisor. See L<virt-install(1)> for details
=back
=head2 Conversion Options
=over 2
=item -i format
=item -i/--input-format FORMAT
Input format. Currently, C<vmx>, C<virt-image>, and C<ovf> are supported.
Input format. This should be auto-detected, but can be forced if necessary. Currently C<vmx> and C<ovf> are supported.
=item -o format
=item -D/--disk-format DISK-FORMAT
Output format. Currently, C<vmx> and C<virt-image> are supported.
Output disk format. The default is 'raw', so any encountered disk images will be converted to 'raw' format using L<qemu-img(1)>. Pass C<none> if no conversion should be performed: in this case the images will just be copied to the specified --destination.
=item -D format
=item --destination DIRECTORY
Output disk format, or C<none> if no conversion should be performed. See
L<qemu-img(1)>.
The directory to send converted/copied disk images. If not specified, the hypervisor default is used, typically /var/lib/libvirt/images.
=back
=head2 Virtualization Type options
Options to override the default virtualization type choices.
=over 2
=item -v, --hvm Create a fully virtualized guest image
Convert machine to a hvm/qemu based image (this is the default if paravirt
is not specified)
=item -p, --paravirt Create a paravirtualized guest image
Convert machine to a paravirt xen based image
=back
=head2 General Options
General configuration parameters that apply to all types of guest installs.
=head2 Miscellaneous Options
=over 2
=item -a ARCH, --arch=ARCH
=item --noautoconsole
Architecture of the virtual machine (i686, x86_64, ppc). Defaults to
that of the host machine.
Don't automatically try to connect to the guest console. The default behaviour
is to launch L<virt-viewer(1)> to display the graphical console, or to run the
C<virsh> C<console> command to display the text console. Use of this parameter
will disable this behaviour.
=item --os-variant=OS_VARIANT
=item --print-xml
Optimize the guest configuration for a specific operating system (ex.
'fedora18', 'rhel7', 'winxp'). While not requires, specifying this
options is HIGHLY RECOMMENDED, as it can greatly increase performance
by specifying virtio among other guest tweaks.
See L<virt-install(1)> for valid values.
Print the generated libvirt XML, but do not perform any disk conversions or
install/start the guest. This option implies --dry-run.
=back
=head2 Miscellaneous Options
=item --dry-run
=over 2
Proceed through the conversion process, but don't convert disks or actually
write any converted files.
=item -q, --quiet
......@@ -113,22 +88,21 @@ Avoid verbose output.
Print debugging information
=item --dry-run
Proceed through the conversion process, but don't convert disks or actually
write any converted files.
=back
=head1 EXAMPLES
Convert a paravirt guest from C<image.vmx>:
Run a fedora18 OVA archive:
# virt-convert fedora18.ova
Run an extracted zip archive containing a centos6 .vmx and .vmdk file, converting the images to qcow2 format
# virt-convert --arch=i686 --paravirt image.vmx
# virt-convert centos6/ --disk-format qcow2
Convert a 64-bit hvm guest:
Convert the specified .vmx file. Any references disk images must be in the same directory. Don't change the disk format. Move the disk images to /tmp
# virt-convert --arch=x86_64 vmx-appliance/ hvm-appliance/
# virt-convert foo.vmx --disk-format none --destination /tmp
=head1 BUGS
......@@ -143,7 +117,7 @@ There is NO WARRANTY, to the extent permitted by law.
=head1 SEE ALSO
L<virt-image(5)>, the project website C<http://virt-manager.org>
L<virt-install(1)>, the project website C<http://virt-manager.org>
=cut
......@@ -10,6 +10,10 @@ B<virt-image> [OPTION]... IMAGE.XML
=head1 DESCRIPTION
WARNING: B<virt-image> is planned for removal in the near future. If you are depending on this tool, please contact the developers at virt-tools-list@redhat.com
B<virt-image> is a command line tool for creating virtual machines from an
XML image descriptor C<IMAGE.XML> (L<virt-image(5)>). Most attributes of
the virtual machine are taken from the XML descriptor (e.g., where the
......
......@@ -100,6 +100,12 @@ like 'maxmemory' and 'hugepages'. This deprecates the -r/--ram option.
Use --memory=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsMemoryAllocation>
=item --memorybacking OPT1=yes|no[,OPT2=yes|no][...]
This option will influence how virtual memory pages are backed by host pages.
Use --memorybacking=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsMemoryBacking>
=item --arch=ARCH
Request a non-native CPU architecture for the guest virtual machine.
......@@ -151,12 +157,30 @@ mode.
Use --numatune=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsNUMATuning>
=item --memtune=SOFT_LIMIT,[hard_limit=HARD_LIMIT,swap_hard_limit=SW_HARD_LIMIT,min_guarantee=MIN_GUARANTEE]
Tune memory policy for the domain process. Example invocations
--memtune 1000
--memtune hard_limit=100,soft_limit=60,swap_hard_limit=150,min_guarantee=80
Use --memtune=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsMemoryTuning>
=item --blkiotune=WEIGHT,[device_path=DEVICE_PATH,device_weight=DEVICE_WEIGHT]
Tune blkio policy for the domain process. Example invocations
--blkiotune 100
--blkiotune weight=100,device_path=/dev/sdc,device_weight=200
Use --blkiotune=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsBlockTuning>
=item --cpu MODEL[,+feature][,-feature][,match=MATCH][,vendor=VENDOR]
Configure the CPU model and CPU features exposed to the guest. The only
required value is MODEL, which is a valid CPU model as known to libvirt.
libvirt's feature policy values force, require, optional, disable, or forbid,
Libvirt's feature policy values force, require, optional, disable, or forbid,
or with the shorthand '+feature' and '-feature', which equal 'force=feature'
and 'disable=feature' respectively
......@@ -433,6 +457,20 @@ will default to /bin/sh.
Use --boot=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsOS>
=item --idmap=IDMAPOPTS
If the guest configuration declares a UID or GID mapping,
the 'user' namespace will be enabled to apply these.
A suitably configured UID/GID mapping is a pre-requisite to
make containers secure, in the absence of sVirt confinement.
--idmap can be specified to enable user namespace for LXC containers
Example:
--idmap uid_start=0,uid_target=1000,uid_count=10,gid_start=0,gid_target=1000,gid_count=10
Use --idmap=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsOSContainer>
=back
......@@ -450,9 +488,13 @@ general format of a disk string is
--disk opt1=val1,opt2=val2,...
To specify media, the command can either be:
The simplest invocation to create a new 10G disk image and associated disk device:
--disk size=10
virt-install will generate a path name, and place it in the default image location for the hypervisor. To specify media, the command can either be:
--disk /some/storage/path,opt1=val1
--disk /some/storage/path[,opt1=val1]...
or explicitly specify one of the following arguments:
......@@ -461,14 +503,11 @@ or explicitly specify one of the following arguments:
=item B<path>
A path to some storage media to use, existing or not. Existing media can be
a file or block device. If installing on a remote host, the existing media
must be shared as a libvirt storage volume.
a file or block device.
Specifying a non-existent path implies attempting to create the new storage,
and will require specifying a 'size' value. If the base directory of the path
is a libvirt storage pool on the host, the new storage will be created as a
libvirt storage volume. For remote hosts, the base directory is required to be
a storage pool if using this method.
and will require specifying a 'size' value. Even for remote hosts, virt-install
will try to use libvirt storage APIs to automatically create the given path.
=item B<pool>
......@@ -539,16 +578,11 @@ read and write caching.
=item B<format>
Image format to be used if creating managed storage. For file volumes, this
can be 'raw', 'qcow2', 'vmdk', etc. See format types in
L<http://libvirt.org/storage.html> for possible values. This is often
mapped to the B<driver_type> value as well.
Disk image format. For file volumes, this can be 'raw', 'qcow2', 'vmdk', etc. See format types in L<http://libvirt.org/storage.html> for possible values. This is often mapped to the B<driver_type> value as well.
With libvirt 0.8.3 and later, this option should be specified if reusing
an existing disk image, since libvirt does not autodetect storage format
as it is a potential security issue. For example, if reusing an existing
qcow2 image, you will want to specify format=qcow2, otherwise the hypervisor
may not be able to read your disk image.
If not specified when creating file images, this will default to 'qcow2'.
If creating storage, this will be the format of the new image. If using an existing image, this overrides libvirt's format auto-detection.
=item B<driver_name>
......@@ -759,12 +793,6 @@ actual VNC display allocated can be obtained using the C<vncdisplay>
command to C<virsh> (or L<virt-viewer(1)> can be used which handles this
detail for the use).
sdl
Setup a virtual console in the guest and display an SDL window in the
host to render the output. If the SDL window is closed the guest may
be unconditionally terminated.
spice
Export the guest's console using the Spice protocol. Spice allows advanced
......@@ -824,7 +852,7 @@ This deprecates the following options: --vnc, --vncport, --vnclisten, -k/--keyma
=item --noautoconsole
Don't automatically try to connect to the guest console. The default behaviour
is to launch a VNC client to display the graphical console, or to run the
is to launch L<virt-viewer(1)> to display the graphical console, or to run the
C<virsh> C<console> command to display the text console. Use of this parameter
will disable this behaviour.
......@@ -954,16 +982,16 @@ PCI device (via lspci).
Use --host-device=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsHostDev>
=item --soundhw MODEL
=item --sound MODEL
Attach a virtual audio device to the guest. MODEL specifies the emulated
sound card model. Possible values are ich6, ac97, es1370, sb16, pcspk,
or default. 'default' will try to pick the best model that the specified
OS supports.
This deprecates the old boolean --sound option.
This deprecates the old --soundhw option.
Use --soundhw=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsSound>
Use --sound=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsSound>
=item --watchdog MODEL[,action=ACTION]
......@@ -1406,17 +1434,17 @@ C<~/.cache/virt-manager/virt-install.log> even if this parameter is omitted.
=head1 EXAMPLES
Install a Fedora 13 KVM guest with virtio accelerated disk/network,
creating a new 8GB storage file, installing from media in the hosts
CDROM drive, auto launching a graphical VNC viewer
Install a Fedora 20 KVM guest with virtio accelerated disk/network,
creating a new 10GB qcow2 file, installing from media in the hosts
CDROM drive. This will use Spice graphics by default, and launch autolaunch
a graphical client.
# virt-install \
--connect qemu:///system \
--virt-type kvm \
--name demo \
--memory 500 \
--disk path=/var/lib/libvirt/images/demo.img,size=8 \
--graphics vnc \
--disk size=10 \
--cdrom /dev/cdrom \
--os-variant fedora13
......@@ -1433,20 +1461,6 @@ booting from PXE, using VNC server/viewer
--graphics vnc \
--os-variant fedora9
Install a guest with a real partition, with the default QEMU hypervisor for
a different architecture using SDL graphics, using a remote kernel and initrd
pair:
# virt-install \
--connect qemu:///system \
--name demo \
--memory 500 \
--disk path=/dev/hdc \
--network bridge=eth1 \
--arch ppc64 \
--graphics sdl \
--location http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os/
Run a Live CD image under Xen fullyvirt, in diskless environment
# virt-install \
......
......@@ -37,7 +37,7 @@ Show the help message and exit
Show program's version number and exit
=item --connect=URI
=item -c URI, --connect=URI
Connect to a non-default hypervisor. See L<virt-install(1)> for details
......@@ -110,7 +110,7 @@ Remove the second disk device
Remove all network devices
=item --remove-device --soundhw pcspk
=item --remove-device --sound pcspk
Remove all sound devices with model='pcspk'
......@@ -206,7 +206,7 @@ Before defining or updating the domain, show the generated XML diff and interact
=item --host-device
=item --soundhw
=item --sound
=item --watchdog
......@@ -228,7 +228,7 @@ These options alter the XML for a single class of XML elements. More complete do
Generally these options map pretty straightforwardly to the libvirt XML, documented at L<http://libvirt.org/formatdomain.html>
Option strings are in the format of: --option opt=val,opt2=val2,... example: --disk path=/tmp/foo,shareable=on. Propertys can be unsed with '--option opt=,', so to clear a disks cache setting you could use '--disk cache=,'
Option strings are in the format of: --option opt=val,opt2=val2,... example: --disk path=/tmp/foo,shareable=on. Properties can be used with '--option opt=,', so to clear a disks cache setting you could use '--disk cache=,'
Every XML option has a special value 'clearxml=yes'. When combined with --edit, it will completely blank out the XML block being edited before applying the requested changes. This allows completely rebuilding an XML block. See EXAMPLES for some usage.
......@@ -278,7 +278,7 @@ Clear the previous <cpu> definition of domain 'winxp', change it to 'host-model'
Change the second sound card to model=ich6 on 'fedora19', but only output the diff:
# virt-xml fedora19 --edit 2 --soundhw model=ich6 --print-diff
# virt-xml fedora19 --edit 2 --sound model=ich6 --print-diff
Update the every graphics device password to 'foo' of the running VM 'rhel6':
......
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.