Skip to content
Commits on Source (2)
2019-04-01 intrigeri <intrigeri+libvirt@boum.org>
apparmor: support more QEMU architectures
Add hppa, nios2, or1k, riscv32 and riscv64 to the profile.
Fixes: https://bugs.debian.org/914940
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
2019-04-01 Daniel P. Berrangé <berrange@redhat.com>
apps: remove VM Manager android app
The VM Manager app is no longer present on the Play store and while
Google shows a couple of hits they look like the typical untrustworthy
3rd party download redistributors rather than an official site.
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
2019-04-01 Daniel P. Berrangé <berrange@redhat.com>
apps: drop link for zenoss software
The page we link to is a 404 and github repo hasn't been touched since
2012 so is clearly dead.
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
2019-04-01 Daniel P. Berrangé <berrange@redhat.com>
apps: update link for buildbot
The libvirt specific page linked for buildbot is a 404. This replacement
link is the closest to what was originally linked.
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
2019-04-01 Daniel P. Berrangé <berrange@redhat.com>
apps: remove dead archipel project
The project website http://archipelproject.org/ is dead, reporting a
cloudflare error message
The git repo at https://github.com/ArchipelProject/Archipel/ hasn't
had a commit since Nov 2016, and the last release was a beta6 release
in 2013.
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
2019-04-01 Andrea Bolognani <abologna@redhat.com>
news: Update for 5.2.0 release
Acked-by: Michal Privoznik <mprivozn@redhat.com>
2019-03-30 John Ferlan <jferlan@redhat.com>
 
tools: Tweak wording for iothreadset
libvirt releases
================
# v5.2.0 (unreleased)
# v5.2.0 (2019-04-03)
* New features
......@@ -64,8 +64,27 @@ libvirt releases
are required. This means that if a network doesn't have IPv6 enabled
then those tables are not required.
- Don't default to building the QEMU driver
Historically, the QEMU driver has been special in that it was enabled
by default, with the option to explicitly opt-out of it; starting now,
we're enabling it opportunistically if we detect that all requirements
are available, just like we do with other drivers.
* Bug fixes
- virt-host-validate: Fix IOMMU check on s390x
- qemu: Allow creating pSeries guests with graphics and no USB mouse
It's now possible to prevent libvirt from automatically adding a USB
mouse to pSeries guests by including a USB tablet in the input XML:
doing so is desiderable as using a tablet results in a much better user
experience when working with GUIs.
- qemu: Set $HOME and XGD variables for qemu:///system guests
This avoids files being accidentally created under / or the guests not
being able to start because they lack the necessary permissions to
write to that location.
# v5.1.0 (2019-03-04)
* New features
......
libvirt (5.2.0~rc1-1~2.gbp668897) UNRELEASED; urgency=medium
libvirt (5.2.0~rc1-1~3.gbp21533c) UNRELEASED; urgency=medium
** SNAPSHOT build @66889790c47b782cd12d98b49b30d2e1f80dfa02 **
** SNAPSHOT build @21533cff1685c78c610fa9e9ad7452a03a0ce620 **
* [932fa9d] New upstream version 5.2.0~rc1
* [0b5e54e] Bump symbol versions
* [bf0bc67] New upstream version 5.2.0~rc2
* [dd9d74f] New upstream version 5.2.0
-- Guido Günther <agx@sigxcpu.org> Mon, 01 Apr 2019 12:56:36 +0200
-- Guido Günther <agx@sigxcpu.org> Fri, 05 Apr 2019 09:17:27 +0200
libvirt (5.1.0-1) experimental; urgency=medium
......
......@@ -6,7 +6,7 @@
Do not edit this file. Changes will be lost.
-->
<!--
This page was generated at Thu Mar 28 08:58:09 UTC 2019.
This page was generated at Wed Apr 3 07:06:10 UTC 2019.
-->
<head>
<meta charset="UTF-8"/>
......@@ -64,9 +64,6 @@
<li>
<a href="#add">Add an application</a>
</li>
<li>
<a href="#clientserver">Client/Server applications</a>
</li>
<li>
<a href="#command">Command line tools</a>
</li>
......@@ -100,9 +97,6 @@
<li>
<a href="#web">Web applications</a>
</li>
<li>
<a href="#mobile">Mobile applications</a>
</li>
<li>
<a href="#other">Other</a>
</li>
......@@ -126,29 +120,6 @@
<img src="logos/logo-square-powered-192.png" alt="libvirt powered"/>
<img src="logos/logo-square-powered-256.png" alt="libvirt powered"/>
</p>
<h2>
<a id="clientserver">Client/Server applications</a>
<a class="headerlink" href="#clientserver" title="Permalink to this headline"></a>
</h2>
<dl>
<dt>
<a href="http://archipelproject.org">Archipel</a>
</dt>
<dd>
Archipel is a libvirt-based solution to manage and supervise virtual
machines. It uses XMPP for all communication. There is no web
service or custom protocol. You just need at least one XMPP server,
like eJabberd, to start playing with it. This allows Archipel to
work completely real time. You never have to refresh the user
interface, you'll be notified as soon as something happens. You can
even use your favorite chat clients to command your infrastructure.
</dd>
<dd>
Isn't it great to be able to open a chat conversation with your
virtual machine and say things like "How are you today?" or "Hey,
please reboot"?
</dd>
</dl>
<h2>
<a id="command">Command line tools</a>
<a class="headerlink" href="#command" title="Permalink to this headline"></a>
......@@ -264,7 +235,7 @@
</h2>
<dl>
<dt>
<a href="https://buildbot.net/buildbot/docs/current/Libvirt.html">BuildBot</a>
<a href="http://docs.buildbot.net/latest/manual/configuration/workers-libvirt.html">BuildBot</a>
</dt>
<dd>
BuildBot is a system to automate the compile/test cycle required
......@@ -542,14 +513,6 @@
hypervisor and guest information and complete set of guest performance
metrics. It supports pCPU, vCPU, memory, block device, network interface,
and performance event metrics for each virtual guest.
</dd>
<dt>
<a href="https://community.zenoss.org/docs/DOC-4687">Zenoss</a>
</dt>
<dd>
The Zenoss libvirt Zenpack adds support for monitoring virtualization
servers. It has been tested with KVM, QEMU, VMware ESX, and VMware
GSX.
</dd>
</dl>
<h2>
......@@ -656,20 +619,6 @@
Virtlyst is an open source web application built with C++11, Cutelyst and Qt.
It features:
<ul><li>Low memory usage (around 5 MiB of RAM)</li><li>Look and feel easily customized with HTML templates that use the Django syntax</li><li>VNC/Spice console directly in the browser using websockets on the same HTTP port</li><li>Host and Domain statistics graphs (CPU, Memory, IO, Network)</li><li>Connect to multiple libvirtd instances (over local Unix domain socket, SSH, TCP and TLS)</li><li>Manage Storage Pools, Storage Volumes, Networks, Interfaces, and Secrets</li><li>Create and launch VMs</li><li>Configure VMs with easy panels or go pro and edit the VM's XML</li></ul>
</dd>
</dl>
<h2>
<a id="mobile">Mobile applications</a>
<a class="headerlink" href="#mobile" title="Permalink to this headline"></a>
</h2>
<dl>
<dt>
<a href="https://market.android.com/details?id=vm.manager">VM Manager</a>
</dt>
<dd>
VM Manager is VM (libvirt) manager (over SSH) application. VM Manager
is an application for libvirt VM / Domain management over SSH.
Please keep in mind that this software is under heavy development.
</dd>
</dl>
<h2>
......
......@@ -30,26 +30,6 @@
<img src="logos/logo-square-powered-256.png" alt="libvirt powered"/>
</p>
<h2><a id="clientserver">Client/Server applications</a></h2>
<dl>
<dt><a href="http://archipelproject.org">Archipel</a></dt>
<dd>
Archipel is a libvirt-based solution to manage and supervise virtual
machines. It uses XMPP for all communication. There is no web
service or custom protocol. You just need at least one XMPP server,
like eJabberd, to start playing with it. This allows Archipel to
work completely real time. You never have to refresh the user
interface, you'll be notified as soon as something happens. You can
even use your favorite chat clients to command your infrastructure.
</dd>
<dd>
Isn't it great to be able to open a chat conversation with your
virtual machine and say things like "How are you today?" or "Hey,
please reboot"?
</dd>
</dl>
<h2><a id="command">Command line tools</a></h2>
<dl>
......@@ -142,7 +122,7 @@
<h2><a id="continuousintegration">Continuous Integration</a></h2>
<dl>
<dt><a href="https://buildbot.net/buildbot/docs/current/Libvirt.html">BuildBot</a></dt>
<dt><a href="http://docs.buildbot.net/latest/manual/configuration/workers-libvirt.html">BuildBot</a></dt>
<dd>
BuildBot is a system to automate the compile/test cycle required
by most software projects. CVS commits trigger new builds, run on
......@@ -373,12 +353,6 @@
metrics. It supports pCPU, vCPU, memory, block device, network interface,
and performance event metrics for each virtual guest.
</dd>
<dt><a href="https://community.zenoss.org/docs/DOC-4687">Zenoss</a></dt>
<dd>
The Zenoss libvirt Zenpack adds support for monitoring virtualization
servers. It has been tested with KVM, QEMU, VMware ESX, and VMware
GSX.
</dd>
</dl>
<h2><a id="provisioning">Provisioning</a></h2>
......@@ -483,17 +457,6 @@
</dd>
</dl>
<h2><a id="mobile">Mobile applications</a></h2>
<dl>
<dt><a href="https://market.android.com/details?id=vm.manager">VM Manager</a></dt>
<dd>
VM Manager is VM (libvirt) manager (over SSH) application. VM Manager
is an application for libvirt VM / Domain management over SSH.
Please keep in mind that this software is under heavy development.
</dd>
</dl>
<h2><a id="other">Other</a></h2>
<dl>
......
......@@ -6,7 +6,7 @@
Do not edit this file. Changes will be lost.
-->
<!--
This page was generated at Thu Mar 28 08:58:08 UTC 2019.
This page was generated at Wed Apr 3 07:06:10 UTC 2019.
-->
<head>
<meta charset="UTF-8"/>
......@@ -63,7 +63,7 @@
<a href="https://libvirt.org/git/?p=libvirt.git;a=log">git log</a>.
</p>
<h3>
<strong>v5.2.0 (unreleased)</strong>
<strong>v5.2.0 (2019-04-03)</strong>
</h3>
<ul>
<li>
......@@ -161,11 +161,39 @@
corresponding IP version are required. This means that if a
network doesn't have <code>IPv6</code> enabled then those
tables are not required.
</li>
<li>
Don't default to building the QEMU driver
<br/>
Historically, the QEMU driver has been special in that it was
enabled by default, with the option to explicitly opt-out of it;
starting now, we're enabling it opportunistically if we detect that
all requirements are available, just like we do with other drivers.
</li>
</ul>
</li>
<li>
<strong>Bug fixes</strong>
<ul>
<li>
virt-host-validate: Fix IOMMU check on s390x
</li>
<li>
qemu: Allow creating pSeries guests with graphics and no USB mouse
<br/>
It's now possible to prevent libvirt from automatically adding a
USB mouse to pSeries guests by including a USB tablet in the input
XML: doing so is desiderable as using a tablet results in a much
better user experience when working with GUIs.
</li>
<li>
qemu: Set $HOME and XGD variables for qemu:///system guests
<br/>
This avoids files being accidentally created under <code>/</code> or
the guests not being able to start because they lack the necessary
permissions to write to that location.
</li>
</ul>
</li>
</ul>
<h3>
......
......@@ -12,7 +12,7 @@
<h1>Releases</h1><p>This is the list of official releases for libvirt, along with an
overview of the changes introduced by each of them.</p><p>For a more fine-grained view, use the
<a href="https://libvirt.org/git/?p=libvirt.git;a=log">git log</a>.
</p><h3><strong>v5.2.0 (unreleased)</strong></h3><ul><li><strong>New features</strong><ul><li>
</p><h3><strong>v5.2.0 (2019-04-03)</strong></h3><ul><li><strong>New features</strong><ul><li>
Add Storage Pool Capabilities output
<br/>
Add support to list an enumerated list of supported Storage
......@@ -86,7 +86,29 @@
corresponding IP version are required. This means that if a
network doesn't have <code>IPv6</code> enabled then those
tables are not required.
</li></ul></li><li><strong>Bug fixes</strong></li></ul><h3><strong>v5.1.0 (2019-03-04)</strong></h3><ul><li><strong>New features</strong><ul><li>
</li><li>
Don't default to building the QEMU driver
<br/>
Historically, the QEMU driver has been special in that it was
enabled by default, with the option to explicitly opt-out of it;
starting now, we're enabling it opportunistically if we detect that
all requirements are available, just like we do with other drivers.
</li></ul></li><li><strong>Bug fixes</strong><ul><li>
virt-host-validate: Fix IOMMU check on s390x
</li><li>
qemu: Allow creating pSeries guests with graphics and no USB mouse
<br/>
It's now possible to prevent libvirt from automatically adding a
USB mouse to pSeries guests by including a USB tablet in the input
XML: doing so is desiderable as using a tablet results in a much
better user experience when working with GUIs.
</li><li>
qemu: Set $HOME and XGD variables for qemu:///system guests
<br/>
This avoids files being accidentally created under <code>/</code> or
the guests not being able to start because they lack the necessary
permissions to write to that location.
</li></ul></li></ul><h3><strong>v5.1.0 (2019-03-04)</strong></h3><ul><li><strong>New features</strong><ul><li>
bhyve: Add support for additional command-line arguments
<br/>
The bhyve driver now supports passing additional command-line
......
......@@ -33,7 +33,7 @@
-->
<libvirt>
<release version="v5.2.0" date="unreleased">
<release version="v5.2.0" date="2019-04-03">
<section title="New features">
<change>
<summary>
......@@ -148,8 +148,45 @@
tables are not required.
</description>
</change>
<change>
<summary>
Don't default to building the QEMU driver
</summary>
<description>
Historically, the QEMU driver has been special in that it was
enabled by default, with the option to explicitly opt-out of it;
starting now, we're enabling it opportunistically if we detect that
all requirements are available, just like we do with other drivers.
</description>
</change>
</section>
<section title="Bug fixes">
<change>
<summary>
virt-host-validate: Fix IOMMU check on s390x
</summary>
</change>
<change>
<summary>
qemu: Allow creating pSeries guests with graphics and no USB mouse
</summary>
<description>
It's now possible to prevent libvirt from automatically adding a
USB mouse to pSeries guests by including a USB tablet in the input
XML: doing so is desiderable as using a tablet results in a much
better user experience when working with GUIs.
</description>
</change>
<change>
<summary>
qemu: Set $HOME and XGD variables for qemu:///system guests
</summary>
<description>
This avoids files being accidentally created under <code>/</code> or
the guests not being able to start because they lack the necessary
permissions to write to that location.
</description>
</change>
</section>
</release>
<release version="v5.1.0" date="2019-03-04">
......
......@@ -216,14 +216,14 @@
Summary: Library providing a simple virtualization API
Name: libvirt
Version: 5.2.0
Release: 0rc2%{?dist}%{?extra_release}
Release: 1%{?dist}
License: LGPLv2+
URL: https://libvirt.org/
%if %(echo %{version} | grep -q "\.0$"; echo $?) == 1
%define mainturl stable_updates/
%endif
Source: https://libvirt.org/sources/%{?mainturl}libvirt-%{version}-rc2.tar.xz
Source: https://libvirt.org/sources/%{?mainturl}libvirt-%{version}.tar.xz
Requires: libvirt-daemon = %{version}-%{release}
Requires: libvirt-daemon-config-network = %{version}-%{release}
......
......@@ -216,14 +216,14 @@
Summary: Library providing a simple virtualization API
Name: libvirt
Version: @VERSION@
Release: 0rc2%{?dist}%{?extra_release}
Release: 1%{?dist}
License: LGPLv2+
URL: https://libvirt.org/
%if %(echo %{version} | grep -q "\.0$"; echo $?) == 1
%define mainturl stable_updates/
%endif
Source: https://libvirt.org/sources/%{?mainturl}libvirt-%{version}-rc2.tar.xz
Source: https://libvirt.org/sources/%{?mainturl}libvirt-%{version}.tar.xz
Requires: libvirt-daemon = %{version}-%{release}
Requires: libvirt-daemon-config-network = %{version}-%{release}
......
......@@ -103,6 +103,7 @@
/usr/bin/qemu-system-alpha rmix,
/usr/bin/qemu-system-arm rmix,
/usr/bin/qemu-system-cris rmix,
/usr/bin/qemu-system-hppa rmix,
/usr/bin/qemu-system-i386 rmix,
/usr/bin/qemu-system-lm32 rmix,
/usr/bin/qemu-system-m68k rmix,
......@@ -113,10 +114,14 @@
/usr/bin/qemu-system-mips64el rmix,
/usr/bin/qemu-system-mipsel rmix,
/usr/bin/qemu-system-moxie rmix,
/usr/bin/qemu-system-nios2 rmix,
/usr/bin/qemu-system-or1k rmix,
/usr/bin/qemu-system-or32 rmix,
/usr/bin/qemu-system-ppc rmix,
/usr/bin/qemu-system-ppc64 rmix,
/usr/bin/qemu-system-ppcemb rmix,
/usr/bin/qemu-system-riscv32 rmix,
/usr/bin/qemu-system-riscv64 rmix,
/usr/bin/qemu-system-s390x rmix,
/usr/bin/qemu-system-sh4 rmix,
/usr/bin/qemu-system-sh4eb rmix,
......