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

Merge tag 'upstream/1.3.2' into debian/experimental

Upstream version 1.3.2

# gpg: Signature made Do 04 Feb 2016 11:17:49 CET
# gpg:                using RSA key 0x07B8B7B0EA98120B
# gpg: please do a --check-trustdb
# gpg: Good signature from "Guido Günther <agx@sigxcpu.org>" [ultimate]
# gpg:                 aka "Guido Günther <gg@godiug.net>" [ultimate]
# gpg:                 aka "Guido Günther <agx@debian.org>" [ultimate]
# Primary key fingerprint: D343 9DAA 19DC FACD AE87  9CF2 B999 CDB5 8C8D DBD2
#      Subkey fingerprint: BC7C D072 3875 EBAD 05DF  1CD9 07B8 B7B0 EA98 120B
parents 74c0ccef b6de3ae1
[main]
host = https://www.transifex.com
[virt-manager.virt-managerpot]
file_filter = po/<lang>.po
source_file = po/virt-manager.pot
source_lang = en
......@@ -42,23 +42,26 @@ entire glade file, you likely have a too old (or too new :) glade version.
==================
Patches should be developed against a git checkout and _not_ a source
release. The git repo is at
release. The git repo is at:
git://git.fedorahosted.org/git/virt-manager.git
For a web view, see:
https://git.fedorahosted.org/cgit/virt-manager.git/
https://github.com/virt-manager/virt-manager
Patches should be sent to the mailing list (see README for details). Using
git format-patch/send-email is preferred, but an attachment with
format-patch output is fine too.
Small patches are acceptable via github pull-request, but anything
non-trivial should be sent to the mailing list.
Translations
============
For translations, please sign up for transifex.com and contribute to the
virt-manager project, see:
Translations are handled at fedora.zanata.org. Please register for a Fedora
account and request access to a translation team, as described at:
http://fedoraproject.org/wiki/L10N/Translate_on_Zanata
And contribute to virt-manager at:
https://www.transifex.com/projects/p/virt-manager/
https://fedora.zanata.org/project/view/virt-manager/
......@@ -19,3 +19,25 @@ setup.py generally has all the build and install commands, for more info see:
python setup.py --help-commands
python setup.py install --help
http://docs.python.org/inst/standard-install.html
Pre-requisite software
======================
virt-manager was ported to GTK3 at the beginning of 2013. Older GTK3
or pygobject3 versions likely will not work for running virt-manager.
Earliest tested versions of major components:
python >= 2.6
gtk3 >= 3.6
libvirt-python >= 0.4.0
pygobject3 >= 3.4
libosinfo >= 0.2.10
A more detailed dependency list can be found in virt-manager.spec.in.
On Debian or Ubuntu based distributions, you need to install the
gobject-introspection bindings for some depedencies like libvirt-glib
and libosinfo. Look for package names that start with 'gir', for example
gir1.2-libosinfo-1.0
......@@ -2,9 +2,9 @@
include COPYING HACKING INSTALL NEWS README
include MANIFEST.in
include setup.py
include .tx/config
include virt-*
recursive-include data *
exclude data/gschemas.compiled
recursive-include man *
recursive-include po *
recursive-include tests *
......
Virtual Machine Manager News
============================
Release 1.3.2 (December 24, 2015)
---------------------------------
- Fix dependency issues with vte
Release 1.3.1 (December 06, 2015)
---------------------------------
- Fix command line API on RHEL7 pygobject
Release 1.3.0 (November 24, 2015)
---------------------------------
- Git hosting moved to http://github.com/virt-manager/virt-manager
- Switch translation infrastructure from transifex to fedora.zanata.org
- Add dogtail UI tests and infrastructure
- Improved support for s390x kvm (Kevin Zhao)
- virt-install and virt-manager now remove created disk images if VM
install startup fails
- Replace urlgrabber usage with requests and urllib2
- virt-install: add --network virtualport support for openvswitch
(Daniel P. Berrange)
- virt-install: support multiple --security labels
- virt-install: support --features kvm_hidden=on|off (Pavel Hrdina)
- virt-install: add --features pmu=on|off
- virt-install: add --features pvspinlock=on|off (Abhijeet Kasurde)
- virt-install: add --events on_lockfailure=on|off (Abhijeet Kasurde)
- virt-install: add --network link_state=up|down
- virt-install: add --vcpu placement=static|auto
Release 1.2.1 (June 06, 2015)
-----------------------------
- Bugfix release
......
Metadata-Version: 1.0
Name: virt-manager
Version: 1.2.1
Version: 1.3.2
Summary: UNKNOWN
Home-page: http://virt-manager.org
Author: Cole Robinson
......
......@@ -10,25 +10,7 @@ Qemu/KVM and Xen virtual machines, as well as LXC containers. The UI is
primarily tested with KVM, but is intended to be reasonably portable to any
virtualization backend libvirt supports.
Pre-requisite software
======================
virt-manager was ported to GTK3 at the beginning of 2013. Older GTK3
or pygobject3 versions likely will not work for running virt-manager.
Earliest tested versions of major components:
python >= 2.6
gtk3 >= 3.6
libvirt-python >= 0.4.0
pygobject3 >= 3.4
libosinfo >= 0.2.10
A more detailed dependency list can be found in virt-manager.spec.in. On
Debian based distributions you need to install the gobject-introspection
bindings for some depedencies like libvirt-glib and libosinfo. Look for
package names that start with 'gir'.
For dependency info and installation instructions, see the INSTALL file
Contact
......
......@@ -246,6 +246,14 @@ Enable APIC PV EOI
Enable hypver VAPIC, but disable spinlocks
=item B<--features kvm_hidden=on>
Allow the KVM hypervisor signature to be hidden from the guest
=item B<--features pvspinlock=on>
Notify the guest that the host supports paravirtual spinlocks for example by exposing the pvticketlocks mechanism.
=back
Use --features=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsFeatures>
......@@ -352,10 +360,14 @@ Some distro specific url samples:
http://download.fedoraproject.org/pub/fedora/linux/releases/21/Server/x86_64/os
=item Debian/Ubuntu
=item Debian
http://ftp.us.debian.org/debian/dists/stable/main/installer-amd64/
=item Ubuntu
http://us.archive.ubuntu.com/ubuntu/dists/wily/main/installer-amd64/
=item Suse
http://download.opensuse.org/distribution/11.0/repo/oss/
......@@ -563,6 +575,10 @@ Disk device type. Value can be 'cdrom', 'disk', 'lun' or 'floppy'. Default is
'disk'. If a 'cdrom' is specified, and no install method is chosen, the
cdrom is used as the install media.
=item B<boot_order>
Guest installation with multiple disks will need this parameter to boot correctly after being installed. A boot_order parameter will take values 1,2,3,... Devices with lower value has higher priority.
=item B<bus>
Disk bus type. Value can be 'ide', 'sata', 'scsi', 'usb', 'virtio' or 'xen'.
......@@ -592,7 +608,7 @@ whether to skip fully allocating newly created storage. Value is 'yes' or
'no'. Default is 'yes' (do not fully allocate) unless it isn't
supported by the underlying storage type.
The initial time taken to fully-allocate the guest virtual disk (sparse=false)
The initial time taken to fully-allocate the guest virtual disk (sparse=no)
will be usually balanced by faster install times inside the guest. Thus
use of this option is recommended to ensure consistently high performance
and to avoid I/O errors in the guest should the host filesystem fill up.
......@@ -780,6 +796,91 @@ Controlling firewall and network filtering in libvirt. Value can be any nwfilter
defined by the C<virsh> 'nwfilter' subcommands. Available filters can be listed
by running 'virsh nwfilter-list', e.g.: 'clean-traffic', 'no-mac-spoofing', ...
=item B<virtualport_type>
The type of virtual port profile, one the following values
=over 4
=item C<802.Qbg>
The following additional parameters are accepted
=over 4
=item B<virtualport_managerid>
The VSI Manager ID identifies the database containing the VSI type
and instance definitions. This is an integer value and the value
0 is reserved.
=item B<virtualport_typeid>
The VSI Type ID identifies a VSI type characterizing the network
access. VSI types are typically managed by network administrator.
This is an integer value.
=item B<virtualport_typeidversion>
The VSI Type Version allows multiple versions of a VSI Type. This
is an integer value.
=item B<virtualport_instanceid>
The VSI Instance ID Identifier is generated when a VSI instance
(i.e. a virtual interface of a virtual machine) is created. This
is a globally unique identifier.
=back
=item C<802.Qbh>
The following additional parameters are accepted
=over 4
=item B<virtualport_profileid>
The profile ID contains the name of the port profile that is to
be applied to this interface. This name is resolved by the port
profile database into the network parameters from the port profile,
and those network parameters will be applied to this interface.
=back
=item C<openvswitch>
The following additional parameters are accepted
=over 4
=item B<virtualport_profileid>
The OpenVSwitch port profile for the interface
=item B<virtualport_interfaceid>
A UUID to uniquely identify the interface. If omitted one will
be generated automatically
=back
=item C<midonet>
The following additional parameters are accepted
=over 4
=item B<virtualport_interfaceid>
A UUID identifying the port in the network to which the interface
will be bound
=back
=back
=back
Use --network=? to see a list of all available sub options. Complete details at L<http://libvirt.org/formatdomain.html#elementsNICS>
......@@ -1532,7 +1633,7 @@ Run a Live CD image under Xen fullyvirt, in diskless environment
--hvm \
--name demo \
--memory 500 \
--disks none \
--disk none \
--livecd \
--graphics vnc \
--cdrom /root/fedora7live.iso
......
......@@ -58,7 +58,7 @@ Edit the specified XML block. EDIT-OPTIONS tell B<virt-xml> which block to edit.
Certain XML options only ever map to a single XML block, like --cpu, --security, --boot, --clock, and a few others. In those cases, B<virt-xml> will not complain if a corresponding XML block does not already exist, it will create it for you.
Some XML option support 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.
Most XML options support 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.
EDIT-OPTIONS examples:
......@@ -274,13 +274,13 @@ See a list of all suboptions that --disk and --network take
# virt-xml --disk=? --network=?
Change the <description> of domain 'example':
Change the <description> of domain 'EXAMPLE':
# virt-xml example --edit --metadata description="my new description"
# virt-xml EXAMPLE --edit --metadata description="my new description"
# Enable the boot device menu for domain 'example':
# Enable the boot device menu for domain 'EXAMPLE':
# virt-xml example --edit --boot menu=on
# virt-xml EXAMPLE --edit --boot menu=on
Clear the previous <cpu> definition of domain 'winxp', change it to 'host-model', but interactively confirm the diff before saving:
......@@ -304,7 +304,8 @@ Change all disk devices of type 'disk' to use cache=none, using XML from stdin,
Change disk 'hda' IO to native and use startup policy as 'optional'.
# virt-xml fedora20 --edit target=hda --disk io=native,startup_policy=optional
# virt-xml fedora20 --edit target=hda \
--disk io=native,startup_policy=optional
Change all host devices to use driver_name=vfio for VM 'fedora20' on the remote connection
......@@ -313,7 +314,7 @@ Change all host devices to use driver_name=vfio for VM 'fedora20' on the remote
Hotplug host USB device 001.003 to running domain 'fedora19':
# virt-xml fedora19 --add-device --hostdev 001.003 --update
# virt-xml fedora19 --update --add-device --hostdev 001.003
Add a spicevmc channel to the domain 'winxp', that will be available after the next VM shutdown.
......@@ -324,9 +325,9 @@ Create a 10G qcow2 disk image and attach it to 'fedora18' for the next VM startu
# virt-xml fedora18 --add-device \
--disk /var/lib/libvirt/images/newimage.qcow2,format=qcow2,size=10
Remove the disk vdb from the running domain 'rhel7':
Hotunplug the disk vdb from the running domain 'rhel7':
# virt-xml rhel7 --remove-device --disk target=vdb
# virt-xml rhel7 --update --remove-device --disk target=vdb
Remove all graphics devices from the VM 'rhel7' after the next shutdown:
......
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.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<config xmlns="http://zanata.org/namespace/config/">
<url>https://fedora.zanata.org/</url>
<project>virt-manager</project>
<project-version>master</project-version>
<project-type>gettext</project-type>
</config>
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
<capabilities>
<!-- The xml comes from the Distro KVMIBM for s390x -->
<host>
<uuid>b53b15d6-348a-4620-afd3-81278b81fbd7</uuid>
<cpu>
<arch>s390x</arch>
<model>host</model>
<topology sockets="1" cores="4" threads="1"/>
<pages unit="KiB" size="4"/>
<pages unit="KiB" size="1024"/>
</cpu>
<power_management>
<suspend_disk/>
<suspend_hybrid/>
</power_management>
<migration_features>
<live/>
<uri_transports>
<uri_transport>tcp</uri_transport>
<uri_transport>rdma</uri_transport>
</uri_transports>
</migration_features>
<topology>
<cells num="1">
<cell id="0">
<memory unit="KiB">3911020</memory>
<cpus num="4">
<cpu id="0" socket_id="0" core_id="0" siblings="0"/>
<cpu id="1" socket_id="0" core_id="1" siblings="1"/>
<cpu id="2" socket_id="0" core_id="2" siblings="2"/>
<cpu id="3" socket_id="0" core_id="3" siblings="3"/>
</cpus>
</cell>
</cells>
</topology>
<secmodel>
<model>selinux</model>
<doi>0</doi>
<baselabel type="kvm">system_u:system_r:svirt_t:s0</baselabel>
<baselabel type="qemu">system_u:system_r:svirt_tcg_t:s0</baselabel>
</secmodel>
<secmodel>
<model>dac</model>
<doi>0</doi>
<baselabel type="kvm">+107:+107</baselabel>
<baselabel type="qemu">+107:+107</baselabel>
</secmodel>
</host>
<guest>
<os_type>hvm</os_type>
<arch name="s390x">
<wordsize>64</wordsize>
<emulator>/usr/bin/qemu-system-s390x</emulator>
<machine maxCpus="64">s390-ccw-kvmibm-1.1.1</machine>
<machine canonical="s390-ccw-kvmibm-1.1.1" maxCpus="64">s390-ccw-virtio</machine>
<machine maxCpus="64">s390-ccw-kvmibm-1.1.0</machine>
<machine maxCpus="255">s390-virtio</machine>
<machine canonical="s390-virtio" maxCpus="255">s390</machine>
<machine maxCpus="255">s390-ccw-virtio-2.4</machine>
<domain type="qemu">
<emulator>/usr/bin/qemu-system-s390x</emulator>
</domain>
<domain type="kvm">
<emulator>/usr/bin/qemu-kvm</emulator>
<machine maxCpus="64">s390-ccw-kvmibm-1.1.1</machine>
<machine canonical="s390-ccw-kvmibm-1.1.1" maxCpus="64">s390-ccw-virtio</machine>
<machine maxCpus="64">s390-ccw-kvmibm-1.1.0</machine>
<machine maxCpus="255">s390-virtio</machine>
<machine canonical="s390-virtio" maxCpus="255">s390</machine>
<machine maxCpus="255">s390-ccw-virtio-2.4</machine>
</domain>
</arch>
<features>
<cpuselection/>
<deviceboot/>
<disksnapshot default="on" toggle="no"/>
</features>
</guest>
</capabilities>
<capabilities>
<host>
<uuid>b88e553c-5920-4aa8-bb09-cc0ab8e6e0c2</uuid>
<cpu>
<arch>s390x</arch>
<model>host</model>
<topology sockets="2" cores="2" threads="1"/>
<pages unit="KiB" size="4"/>
<pages unit="KiB" size="1024"/>
</cpu>
<power_management>
<suspend_disk/>
<suspend_hybrid/>
</power_management>
<migration_features>
<live/>
<uri_transports>
<uri_transport>tcp</uri_transport>
<uri_transport>rdma</uri_transport>
</uri_transports>
</migration_features>
<topology>
<cells num="1">
<cell id="0">
<memory unit="KiB">2878860</memory>
<cpus num="4">
<cpu id="0" socket_id="0" core_id="0" siblings="0"/>
<cpu id="1" socket_id="0" core_id="1" siblings="1"/>
<cpu id="2" socket_id="1" core_id="0" siblings="2"/>
<cpu id="3" socket_id="1" core_id="1" siblings="3"/>
</cpus>
</cell>
</cells>
</topology>
<secmodel>
<model>selinux</model>
<doi>0</doi>
<baselabel type="kvm">system_u:system_r:svirt_t:s0</baselabel>
<baselabel type="qemu">system_u:system_r:svirt_tcg_t:s0</baselabel>
</secmodel>
<secmodel>
<model>dac</model>
<doi>0</doi>
<baselabel type="kvm">+107:+107</baselabel>
<baselabel type="qemu">+107:+107</baselabel>
</secmodel>
</host>
<guest>
<os_type>hvm</os_type>
<arch name="s390x">
<wordsize>64</wordsize>
<emulator>/usr/bin/qemu-system-s390x</emulator>
<machine canonical="s390-virtio" maxCpus="255">s390</machine>
<machine canonical="s390-ccw-virtio" maxCpus="255">s390-ccw</machine>
<domain type="qemu">
<emulator>/usr/bin/qemu-system-s390x</emulator>
</domain>
<domain type="kvm">
<emulator>/usr/bin/qemu-system-s390x</emulator>
<machine canonical="s390-virtio" maxCpus="255">s390</machine>
<machine canonical="s390-ccw-virtio" maxCpus="255">s390-ccw</machine>
</domain>
</arch>
<features>
<cpuselection/>
<deviceboot/>
<disksnapshot default="on" toggle="no"/>
</features>
</guest>
</capabilities>
......@@ -70,13 +70,20 @@ class TestCapabilities(unittest.TestCase):
caps_empty = self._buildCaps("test-old-vmx.xml")
def test_utils(caps, has_guests, is_kvm):
self.assertEquals(caps.has_install_options(), has_guests)
self.assertEquals(caps.is_kvm_available(), is_kvm)
if caps.guests:
self.assertEquals(caps.guests[0].has_install_options(), has_guests)
self.assertEquals(caps.guests[0].is_kvm_available(), is_kvm)
test_utils(caps_empty, False, False)
test_utils(caps_with_kvm, True, True)
test_utils(caps_no_kvm, True, False)
def testCapsNuma(self):
cells = self._buildCaps("lxc.xml").host.topology.cells
self.assertEquals(len(cells), 1)
self.assertEquals(len(cells[0].cpus), 8)
self.assertEquals(cells[0].cpus[3].id, '3')
################################################
# Test cpu_map.xml/getCPUModel output handling #
......
......@@ -63,6 +63,7 @@
<controller type="scsi" index="0"/>
<controller type="fdc" index="0"/>
<controller type="ide" index="0"/>
<controller type="virtio-serial" index="0"/>
<interface type="network">
<mac address="00:11:22:33:44:55"/>
<source network="default"/>
......@@ -75,5 +76,9 @@
<source path="/tmp/foo.log"/>
<target port="0"/>
</parallel>
<channel type="unix">
<source mode="bind"/>
<target type="virtio" name="org.qemu.guest_agent.0"/>
</channel>
</devices>
</domain>
......@@ -12,7 +12,6 @@
<features>
<acpi/>
<apic/>
<pae/>
<vmport state="off"/>
</features>
<cpu mode="custom" match="exact">
......
......@@ -11,7 +11,6 @@
<features>
<acpi/>
<apic/>
<pae/>
<vmport state="off"/>
</features>
<cpu mode="custom" match="exact">
......@@ -36,7 +35,7 @@
<source file="/var/lib/libvirt/images/fedora.qcow2"/>
<target dev="sda" bus="scsi"/>
</disk>