8:41 a.m.
Libvirt 1.1.1 was released 6 years ago. This was the version that
ended up in RHEL 7.0. It is unlikely that the reader will need to
consider libvirt versions beyond that. Remove the since markers
for older versions to de-clutter the documentation a bit.
Signed-off-by: Ján Tomko <jtomko(a)redhat.com>
---
docs/drvnodedev.html.in | 8 ++++----
docs/drvqemu.html.in | 11 +++++------
docs/formatcaps.html.in | 22 ++++++++++------------
docs/storage.html.in | 5 -----
4 files changed, 19 insertions(+), 27 deletions(-)
diff --git a/docs/drvnodedev.html.in b/docs/drvnodedev.html.in
index 71a8a57b0c..fa7b37f58d 100644
--- a/docs/drvnodedev.html.in
+++ b/docs/drvnodedev.html.in
@@ -68,12 +68,12 @@
<code>usb_device</code>,
<code>net</code>,
<code>scsi</code>,
- <code>scsi_host</code> (<span class="since">Since
0.4.7</span>),
+ <code>scsi_host</code>,
<code>fc_host</code>,
<code>vports</code>,
- <code>scsi_target</code> (<span class="since">Since
0.7.3</span>),
- <code>storage</code> (<span class="since">Since
1.0.4</span>),
- <code>scsi_generic</code> (<span
class="since">Since 1.0.7</span>),
+ <code>scsi_target</code>,
+ <code>storage</code>,
+ <code>scsi_generic</code>,
<code>drm</code> (<span class="since">Since
3.1.0</span>), and
<code>mdev</code> (<span class="since">Since
3.4.0</span>).
This element can be nested in which case it further specifies a
diff --git a/docs/drvqemu.html.in b/docs/drvqemu.html.in
index 294117ee1f..50f10376c9 100644
--- a/docs/drvqemu.html.in
+++ b/docs/drvqemu.html.in
@@ -104,7 +104,7 @@ qemu+ssh://root@example.com/system (remote access, SSH tunnelled)
</p>
<p>
- In the "system" instance, libvirt releases from 0.7.0 onwards allow
+ In the "system" instance, libvirt allows
control over the user/group that the QEMU virtual machines are run
as. A build of libvirt with no configuration parameters set will
still run QEMU processes as root:root. It is possible to change
@@ -475,15 +475,14 @@ mount -t cgroup none /dev/cgroup -o devices
<p>The library provides two
API: <code>virDomainQemuMonitorCommand</code>, for sending an
arbitrary monitor command (in either HMP or QMP format) to a
- qemu guest (<span class="since">Since 0.8.3</span>),
+ qemu guest,
and <code>virDomainQemuAttach</code>, for registering a qemu
domain that was manually started so that it can then be managed
- by libvirtd (<span class="since">Since 0.9.4</span>,
- <span class="removed">removed as of 5.5.0</span>).
+ by libvirtd (<span class="removed">removed as of
5.5.0</span>).
</p>
<p>Additionally, the following XML additions allow fine-tuning of
- the command line given to qemu when starting a domain
- (<span class="since">Since 0.8.3</span>). In order to use
the
+ the command line given to qemu when starting a domain.
+ In order to use the
XML additions, it is necessary to issue an XML namespace request
(the special <code>xmlns:<i>name</i></code> attribute)
that
pulls in <code>http://libvirt.org/schemas/domain/qemu/1.0</code>;
diff --git a/docs/formatcaps.html.in b/docs/formatcaps.html.in
index 2a0aa963bb..67fc802afa 100644
--- a/docs/formatcaps.html.in
+++ b/docs/formatcaps.html.in
@@ -10,7 +10,7 @@
<p>As new virtualization engine support gets added to libvirt, and to
handle cases like QEMU supporting a variety of emulations, a query
- interface has been added in 0.2.1 allowing to list the set of supported
+ interface has been added allowing to list the set of supported
virtualization capabilities on the host:</p>
<pre>char * virConnectGetCapabilities (virConnectPtr conn);</pre>
@@ -118,35 +118,33 @@
with a guest of described type. Possible subelements are:
<dl>
<dt><code>pae</code></dt><dd>If present, 32-bit
guests can use PAE
- address space extensions, <span class="since">since
- 0.4.1</span></dd>
+ address space extensions.
+ </dd>
<dt><code>nonpae</code></dt><dd>If present,
32-bit guests can be run
- without requiring PAE, <span class="since">since
- 0.4.1</span></dd>
+ without requiring PAE.
+ </dd>
<dt><code>ia64_be</code></dt><dd>If present,
IA64 guests can be run in
- big-endian mode, <span class="since">since
0.4.1</span></dd>
+ big-endian mode.</dd>
<dt><code>acpi</code></dt><dd>If this element
is present,
the <code>default</code> attribute describes whether the
hypervisor exposes ACPI to the guest by default, and
the <code>toggle</code> attribute describes whether the
- user can override this
- default. <span class="since">Since
0.4.1</span></dd>
+ user can override this default. </dd>
<dt><code>apic</code></dt><dd>If this element
is present,
the <code>default</code> attribute describes whether the
hypervisor exposes APIC to the guest by default, and
the <code>toggle</code> attribute describes whether the
user can override this
- default. <span class="since">Since
0.4.1</span></dd>
+ default. </dd>
<dt><code>cpuselection</code></dt><dd>If this
element is present, the
hypervisor supports the <code><cpu></code>
element
within a domain definition for fine-grained control over
the CPU presented to the
- guest. <span class="since">Since
0.7.5</span></dd>
+ guest. </dd>
<dt><code>deviceboot</code></dt><dd>If this
element is present,
the <code><boot order='...'/></code>
element can
be used inside devices, rather than the older boot
- specification by category. <span class="since">Since
- 0.8.8</span></dd>
+ specification by category. </dd>
<dt><code>disksnapshot</code></dt><dd>If this
element is present,
the <code>default</code> attribute describes whether
external disk snapshots are supported. If absent,
diff --git a/docs/storage.html.in b/docs/storage.html.in
index e0e4edec1e..f22e979eab 100644
--- a/docs/storage.html.in
+++ b/docs/storage.html.in
@@ -480,7 +480,6 @@
aren't generally stable, it is recommended to configure the pool
to use <code>/dev/disk/by-path</code> or
<code>/dev/disk/by-id</code>
for the target path. These provide persistent stable naming for LUNs
- <span class="since">Since 0.6.2</span>
</p>
<h3>Example pool input</h3>
@@ -516,7 +515,6 @@
Configuring multipathing is not currently supported, this just covers
the case where users want to discover all the available multipath
devices, and assign them to guests.
- <span class="since">Since 0.7.1</span>
</p>
<h3>Example pool input</h3>
@@ -556,7 +554,6 @@
refers to the UUID of the stored secret.<br />
The port attribute for a Ceph monitor does not have to be provided.
If not provided librados will use the default Ceph monitor port.
- <span class="since">Since 0.9.13</span>
</p>
<h3>Example pool input</h3>
@@ -619,8 +616,6 @@
can be attached to QEMU/KVM virtual machines.
The cluster must already be formatted.
-
- <span class="since">Since 0.9.13</span>
</p>
<h3>Example pool input</h3>
--
2.20.1