External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-07-01 15:42:39 +00:00
Code Issues Packages Projects Releases Wiki Activity

Prefer https: everywhere where possible

Browse Source 
Use https: links for websites that support them.

The URIs which are used as namespace identifiers
are left alone.

Signed-off-by: Ján Tomko <jtomko@redhat.com>
Reviewed-by: Erik Skultety <eskultet@redhat.com>
Reviewed-by: Neal Gompa <ngompa13@gmail.com>
This commit is contained in:
Ján Tomko 2020-08-26 00:44:00 +02:00
parent 7e1b7acc51
commit 6fab37da59
60 changed files with 117 additions and 117 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/acl.html.in
View File

@ -50,7 +50,7 @@
control technologies. By default, the <code>none</code>
driver is used, which does no access control checks at
all. At this time, libvirt ships with support for using
<a href="http://www.freedesktop.org/wiki/Software/polkit/">polkit</a> as a real access
<a href="https://www.freedesktop.org/wiki/Software/polkit/">polkit</a> as a real access
control driver. To learn how to use the polkit access
driver consult <a href="aclpolkit.html">the configuration
docs</a>.

2
docs/aclpolkit.html.in
View File

@ -18,7 +18,7 @@
<p>
A default install of libvirt will typically use
<a href="http://www.freedesktop.org/wiki/Software/polkit/">polkit</a>
<a href="https://www.freedesktop.org/wiki/Software/polkit/">polkit</a>
to authenticate the initial user connection to libvirtd. This is a
very coarse grained check though, either allowing full read-write
access to all APIs, or just read-only access. The polkit access

4
docs/advanced-tests.rst
View File

@ -18,7 +18,7 @@ by running
$ meson test --setup valgrind
`Valgrind <http://valgrind.org/>`__ is a test that checks for
`Valgrind <https://valgrind.org/>`__ is a test that checks for
memory management issues, such as leaks or use of uninitialized
variables.
@ -160,7 +160,7 @@ filter. The filter should be unique enough to not suppress real
leaks, but it should be generic enough to cover multiple code
paths. The format of the entry can be found in the
documentation found at the `Valgrind home
page <http://valgrind.org/>`__. The following trace was added
page <https://valgrind.org/>`__. The following trace was added
to ``tests/.valgrind.supp`` in order to suppress the warning:
::

4
docs/api.html.in
View File

@ -116,7 +116,7 @@
however, it becomes invalid once the resource is deactivated.</p></li >
<li><code>UUID</code>
<p> A 16 byte unique identifier
as defined in <a href="http://www.ietf.org/rfc/rfc4122.txt">RFC 4122</a>,
as defined in <a href="https://www.ietf.org/rfc/rfc4122.txt">RFC 4122</a>,
which is guaranteed to be unique for long term usage and across a
set of nodes.</p></li>
</ul>
@ -369,7 +369,7 @@
for processing.
</p>
<p>If you are interested in contributing to libvirt, read the
<a href="http://wiki.libvirt.org/page/FAQ">FAQ</a> and
<a href="https://wiki.libvirt.org/page/FAQ">FAQ</a> and
<a href="hacking.html">hacking</a> guidelines to gain an understanding
of basic rules and guidelines. In order to add new API functionality
follow the instructions regarding

16
docs/apps.html.in
View File

@ -128,7 +128,7 @@
<h2><a id="continuousintegration">Continuous Integration</a></h2>
<dl>
<dt><a href="http://docs.buildbot.net/latest/manual/configuration/workers-libvirt.html">BuildBot</a></dt>
<dt><a href="https://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
@ -263,7 +263,7 @@
cloud where you want the most bang for the bucks.
</dd>
<dt><a href="http://en.zstack.io/">ZStack</a></dt>
<dt><a href="https://en.zstack.io/">ZStack</a></dt>
<dd>
ZStack is an open source IaaS software that aims to automate the
management of all resources (compute, storage, networking, etc.) in a
@ -324,14 +324,14 @@
<dl>
<dt><a href="https://collectd.org/plugins/libvirt.shtml">collectd</a></dt>
<dd>
The libvirt-plugin is part of <a href="http://collectd.org/">collectd</a>
The libvirt-plugin is part of <a href="https://collectd.org/">collectd</a>
and gathers statistics about virtualized guests on a system. This
way, you can collect CPU, network interface and block device usage
for each guest without installing collectd on the guest systems.
For a full description, please refer to the libvirt section in the
collectd.conf(5) manual page.
</dd>
<dt><a href="http://www.sflow.net/">Host sFlow</a></dt>
<dt><a href="https://www.sflow.net/">Host sFlow</a></dt>
<dd>
Host sFlow is a lightweight agent running on KVM hypervisors that
links to libvirt library and exports standardized cpu, memory, network
@ -346,15 +346,15 @@
<dt><a href="https://people.redhat.com/rjones/nagios-virt/">Nagios-virt</a></dt>
<dd>
Nagios-virt is a configuration tool to add monitoring of your
virtualised domains to <a href="http://www.nagios.org/">Nagios</a>.
virtualised domains to <a href="https://www.nagios.org/">Nagios</a>.
You can use this tool to either set up a new Nagios installation for
your Xen or QEMU/KVM guests, or to integrate with your existing Nagios
installation.
</dd>
<dt><a href="http://www.pcp.io/man/man1/pmdalibvirt.1.html">PCP</a></dt>
<dt><a href="https://pcp.io/man/man1/pmdalibvirt.1.html">PCP</a></dt>
<dd>
The PCP libvirt PMDA (plugin) is part of the
<a href="http://pcp.io/">PCP</a> toolkit and provides
<a href="https://pcp.io/">PCP</a> toolkit and provides
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.
@ -398,7 +398,7 @@
<h2><a id="web">Web applications</a></h2>
<dl>
<dt><a href="http://www.abiquo.com/">AbiCloud</a></dt>
<dt><a href="https://www.abiquo.com/">AbiCloud</a></dt>
<dd>
AbiCloud is an open source cloud platform manager which allows to
easily deploy a private cloud in your datacenter. One of the key

4
docs/bindings.html.in
View File

@ -28,7 +28,7 @@
</li>
<li>
<strong>Perl</strong>: Daniel Berrange develops
<a href="http://search.cpan.org/dist/Sys-Virt/">Perl bindings</a>.
<a href="https://search.cpan.org/dist/Sys-Virt/">Perl bindings</a>.
</li>
<li>
<p>
@ -60,7 +60,7 @@
</p>
<p>
This is named <b>libvirt-python</b> on RHEL/Fedora,
<a href="http://packages.ubuntu.com/search?keywords=python-libvirt"><b>python-libvirt</b></a>
<a href="https://packages.ubuntu.com/search?keywords=python-libvirt"><b>python-libvirt</b></a>
on Ubuntu, and may be named differently on others.
</p>
<p>

2
docs/coding-style.rst
View File

@ -116,7 +116,7 @@ following to your ~/.vimrc file:
Or if you don't want to mess your ~/.vimrc up, you can save the
above into a file called .lvimrc (not .vimrc) located at the root
of libvirt source, then install a vim script from
http://www.vim.org/scripts/script.php?script_id=1408, which will
https://www.vim.org/scripts/script.php?script_id=1408, which will
load the .lvimrc only when you edit libvirt code.
Code formatting (especially for new code)

2
docs/contact.html.in
View File

@ -98,7 +98,7 @@
<h2><a id="irc">IRC discussion</a></h2>
<p>
Some of the libvirt developers may be found on IRC on the <a href="http://oftc.net">OFTC IRC</a>
Some of the libvirt developers may be found on IRC on the <a href="https://oftc.net">OFTC IRC</a>
network. Use the settings:
</p>
<ul>

4
docs/contribute.html.in
View File

@ -91,7 +91,7 @@
to obtain support, it is common to rely on community help
forums such as <a href="contact.html#email">libvirt users
mailing list</a>, or sites such as
<a href="http://stackoverflow.com/questions/tagged/libvirt">stackoverflow.</a>
<a href="https://stackoverflow.com/questions/tagged/libvirt">stackoverflow.</a>
People who are familiar with libvirt and have ability &amp;
desire to help other users are encouraged to participate in
these help forums.</li>
@ -131,7 +131,7 @@
<p>
Since 2016, the libvirt project directly participates as an
organization in the <a href="http://wiki.libvirt.org/page/Google_Summer_of_Code_Ideas">Google Summer of Code program</a>. Prior to
organization in the <a href="https://wiki.libvirt.org/page/Google_Summer_of_Code_Ideas">Google Summer of Code program</a>. Prior to
this the project had a number of students in the program
via a joint application with the QEMU project. People are
encouraged to look at both the libvirt and QEMU programs

2
docs/csharp.html.in
View File

@ -32,7 +32,7 @@
<h2><a id="git">GIT source repository</a></h2>
<p>
The C# bindings source code is maintained in a <a
href="http://git-scm.com/">git</a> repository available on
href="https://git-scm.com/">git</a> repository available on
<a href="https://gitlab.com/libvirt/libvirt-csharp">gitlab.com</a>:
</p>

4
docs/docs.html.in
View File

@ -48,7 +48,7 @@
<dt><a href="nss.html">NSS module</a></dt>
<dd>Enable domain host name translation to IP addresses</dd>
<dt><a href="http://wiki.libvirt.org/page/FAQ">FAQ</a></dt>
<dt><a href="https://wiki.libvirt.org/page/FAQ">FAQ</a></dt>
<dd>Frequently asked questions</dd>
</dl>
@ -85,7 +85,7 @@
<a href="https://pkg.go.dev/libvirt.org/libvirt-go">go</a>,
<a href="java.html">java</a>,
<a href="https://libvirt.org/ocaml/">ocaml</a>,
<a href="http://search.cpan.org/dist/Sys-Virt/">perl</a>,
<a href="https://search.cpan.org/dist/Sys-Virt/">perl</a>,
<a href="python.html">python</a>,
<a href="php.html">php</a>,
<a href="https://libvirt.org/ruby/">ruby</a>

2
docs/downloads.html.in
View File

@ -564,7 +564,7 @@
<p>
For more details about contents of maintenance releases, see
<a href="http://wiki.libvirt.org/page/Maintenance_Releases">the
<a href="https://wiki.libvirt.org/page/Maintenance_Releases">the
wiki page</a>.
</p>

10
docs/drvbhyve.html.in
View File

@ -28,7 +28,7 @@ $
</pre>
<p>
Additional information on bhyve could be obtained on <a href="http://bhyve.org/">bhyve.org</a>.
Additional information on bhyve could be obtained on <a href="https://bhyve.org/">bhyve.org</a>.
</p>
<h2><a id="uri">Connections to the Bhyve driver</a></h2>
@ -233,7 +233,7 @@ of a guest.</p>
<p><b>NB:</b> Some versions of bhyve have a bug that prevents guests from booting
until the console is opened by a client. This bug was fixed in FreeBSD
<a href="http://svnweb.freebsd.org/changeset/base/262884">r262884</a>. If
<a href="https://svnweb.freebsd.org/changeset/base/262884">r262884</a>. If
an older version is used, one either has to open a console manually with <code>virsh console</code>
to let a guest boot or start a guest using:</p>
@ -392,8 +392,8 @@ it with the <code>port</code> attribute):</p>
<h3><a id="clockconfig">Clock configuration</a></h3>
<p>Originally bhyve supported only localtime for RTC. Support for UTC time was introduced in
<a href="http://svnweb.freebsd.org/changeset/base/284894">r284894</a> for <i>10-STABLE</i> and
in <a href="http://svnweb.freebsd.org/changeset/base/279225">r279225</a> for <i>-CURRENT</i>.
<a href="https://svnweb.freebsd.org/changeset/base/284894">r284894</a> for <i>10-STABLE</i> and
in <a href="https://svnweb.freebsd.org/changeset/base/279225">r279225</a> for <i>-CURRENT</i>.
It's possible to use this in libvirt <span class="since">since 1.2.18</span>, just place the
following to domain XML:</p>
@ -450,7 +450,7 @@ be wired and cannot be swapped out as follows:</p>
<p><span class="since">Since 4.5.0</span>, it's possible to specify guest CPU topology, if bhyve
supports that. Support for specifying guest CPU topology was added to bhyve in
<a href="http://svnweb.freebsd.org/changeset/base/332298">r332298</a> for <i>-CURRENT</i>.
<a href="https://svnweb.freebsd.org/changeset/base/332298">r332298</a> for <i>-CURRENT</i>.
Example:</p>
<pre>
&lt;domain type="bhyve"&gt;

20
docs/drvesx.html.in
View File

@ -15,7 +15,7 @@
<ul>
<li>
The <a href="http://www.vmware.com/">VMware ESX and GSX</a>
The <a href="https://www.vmware.com/">VMware ESX and GSX</a>
hypervisors
</li>
</ul>
@ -26,11 +26,11 @@
preparations are required on the server side, no libvirtd must be
installed on the ESX server. The driver uses version 2.5 of the remote,
SOAP based
<a href="http://www.vmware.com/support/developer/vc-sdk/visdk25pubs/ReferenceGuide/">
<a href="https://www.vmware.com/support/developer/vc-sdk/visdk25pubs/ReferenceGuide/">
VMware Virtual Infrastructure API</a> (VI API) to communicate with the
ESX server, like the VMware Virtual Infrastructure Client (VI client)
does. Since version 4.0 this API is called
<a href="http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/">
<a href="https://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/">
VMware vSphere API</a>.
</p>
@ -239,7 +239,7 @@ error: internal error curl_easy_perform() returned an error: Peer certificate ca
Generate new SSL certificates signed by a CA known to your client
computer and replace the original ones on your ESX server. See the
section <i>Replace a Default Certificate with a CA-Signed Certificate</i>
in the <a href="http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_server_config.pdf">ESX Configuration Guide</a>
in the <a href="https://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_server_config.pdf">ESX Configuration Guide</a>
</li>
</ul>
@ -468,7 +468,7 @@ ethernet0.checkMACAddress = "false"
<dt><code>vmpvscsi</code></dt>
<dd>
Special VMware Paravirtual SCSI controller, requires VMware tools inside
the guest. See <a href="http://kb.vmware.com/kb/1010398">VMware KB1010398</a>
the guest. See <a href="https://kb.vmware.com/kb/1010398">VMware KB1010398</a>
for details. <span class="since">Since 0.8.3</span>
</dd>
</dl>
@ -510,7 +510,7 @@ ethernet0.checkMACAddress = "false"
<dt><code>vmxnet</code>, <code>vmxnet2</code>, <code>vmxnet3</code></dt>
<dd>
Special VMware VMXnet network card, requires VMware tools inside
the guest. See <a href="http://kb.vmware.com/kb/1001805">VMware KB1001805</a>
the guest. See <a href="https://kb.vmware.com/kb/1001805">VMware KB1001805</a>
for details.
</dd>
<dt><code>e1000</code></dt>
@ -808,22 +808,22 @@ Enter administrator password for example-vcenter.com:
<h2><a id="links">Links</a></h2>
<ul>
<li>
<a href="http://www.vmware.com/support/developer/vc-sdk/">
<a href="https://www.vmware.com/support/developer/vc-sdk/">
VMware vSphere Web Services SDK Documentation
</a>
</li>
<li>
<a href="http://www.vmware.com/pdf/esx3_memory.pdf">
<a href="https://www.vmware.com/pdf/esx3_memory.pdf">
The Role of Memory in VMware ESX Server 3
</a>
</li>
<li>
<a href="http://www.sanbarrow.com/vmx.html">
<a href="https://www.sanbarrow.com/vmx.html">
VMware VMX config parameters
</a>
</li>
<li>
<a href="http://www.vmware.com/pdf/vsp_4_pvscsi_perf.pdf">
<a href="https://www.vmware.com/pdf/vsp_4_pvscsi_perf.pdf">
VMware ESX 4.0 PVSCSI Storage Performance
</a>
</li>

2
docs/drvlxc.html.in
View File

@ -75,7 +75,7 @@ would use the following XML
<p>
When the container "init" process is started, it will be given several useful
environment variables. The following standard environment variables are mandated
by <a href="http://www.freedesktop.org/wiki/Software/systemd/ContainerInterface">systemd container interface</a>
by <a href="https://www.freedesktop.org/wiki/Software/systemd/ContainerInterface">systemd container interface</a>
to be provided by all container technologies on Linux.
</p>

2
docs/drvnodedev.html.in
View File

@ -20,7 +20,7 @@
(<code>virsh nodedev-create</code>, <code>virsh nodedev-destroy</code>)
which are meant to be used to create virtual devices, currently only
supported by NPIV
(<a href="http://wiki.libvirt.org/page/NPIV_in_libvirt">more info about NPIV)</a>).
(<a href="https://wiki.libvirt.org/page/NPIV_in_libvirt">more info about NPIV)</a>).
Devices on the host system are arranged in a tree-like hierarchy, with
the root node being called <code>computer</code>. The node device driver
supports two backends to manage the devices, HAL and udev, with the former

4
docs/drvopenvz.html.in
View File

@ -19,7 +19,7 @@
<ul>
<li>
The <a href="http://openvz.org/">OpenVZ</a> Linux container
The <a href="https://openvz.org/">OpenVZ</a> Linux container
system
</li>
</ul>
@ -54,7 +54,7 @@ openvz+ssh://root@example.com/system (remote access, SSH tunnelled)
<p>
One or more of the physical devices must be attached to a bridge. The
process for this varies according to the operating system in use, so
for up to date notes consult the <a href="http://wiki.libvirt.org">Wiki</a>
for up to date notes consult the <a href="https://wiki.libvirt.org">Wiki</a>
or your operating system's networking documentation. The basic idea is
that the host OS should end up with a bridge device "br0" containing a
physical device "eth0", or a bonding device "bond0".

2
docs/drvvbox.html.in
View File

@ -13,7 +13,7 @@
<ul>
<li>
The <a href="http://www.virtualbox.org/">VirtualBox</a>
The <a href="https://www.virtualbox.org/">VirtualBox</a>
hypervisor
</li>
</ul>

8
docs/drvvmware.html.in
View File

@ -7,23 +7,23 @@
The libvirt VMware driver should be able to manage any Workstation,
Player, Fusion version supported by the VMware VIX API. See the
compatibility list
<a href="http://www.vmware.com/support/developer/vix-api/vix110_reference/">here</a>.
<a href="https://www.vmware.com/support/developer/vix-api/vix110_reference/">here</a>.
</p>
<p>
This driver uses the "vmrun" utility which is distributed with the VMware VIX API.
You can download the VIX API
from <a href="http://www.vmware.com/support/developer/vix-api/">here</a>.
from <a href="https://www.vmware.com/support/developer/vix-api/">here</a>.
</p>
<h2><a id="project">Project Links</a></h2>
<ul>
<li>
The <a href="http://www.vmware.com/">VMware Workstation and
The <a href="https://www.vmware.com/">VMware Workstation and
Player</a> hypervisors
</li>
<li>
The <a href="http://www.vmware.com/fusion">VMware Fusion</a>
The <a href="https://www.vmware.com/fusion">VMware Fusion</a>
hypervisor
</li>
</ul>

2
docs/firewall.html.in
View File

@ -175,7 +175,7 @@ MASQUERADE all -- * * 192.168.122.0/24 !192.168.122.0/24</pre>
the conceptual model is closely aligned with the DMTF CIM schema for
network filtering:
</p>
<p><a href="http://www.dmtf.org/standards/cim/cim_schema_v2230/CIM_Network.pdf">http://www.dmtf.org/standards/cim/cim_schema_v2230/CIM_Network.pdf</a></p>
<p><a href="https://www.dmtf.org/standards/cim/cim_schema_v2230/CIM_Network.pdf">https://www.dmtf.org/standards/cim/cim_schema_v2230/CIM_Network.pdf</a></p>
<p>The filters are managed in libvirt as a top level, standalone object.
This allows the filters to then be referenced by any libvirt object
that requires their functionality, instead tying them only to use

16
docs/formatdomain.rst
View File

@ -2423,7 +2423,7 @@ paravirtualized driver is specified via the ``disk`` element.
Using "lun" ( :since:`since 0.9.10` ) is only valid when the ``type`` is
"block" or "network" for ``protocol='iscsi'`` or when the ``type`` is
"volume" when using an iSCSI source ``pool`` for ``mode`` "host" or as an
`NPIV <http://wiki.libvirt.org/page/NPIV_in_libvirt>`__ virtual Host Bus
`NPIV <https://wiki.libvirt.org/page/NPIV_in_libvirt>`__ virtual Host Bus
Adapter (vHBA) using a Fibre Channel storage pool. Configured in this
manner, the LUN behaves identically to "disk", except that generic SCSI
commands from the guest are accepted and passed through to the physical
@ -3118,16 +3118,16 @@ A directory on the host that can be accessed directly from the guest.
``passthrough``
The ``source`` is accessed with the permissions of the user inside the
guest. This is the default ``accessmode`` if one is not specified. `More
info <http://lists.gnu.org/archive/html/qemu-devel/2010-05/msg02673.html>`__
info <https://lists.gnu.org/archive/html/qemu-devel/2010-05/msg02673.html>`__
``mapped``
The ``source`` is accessed with the permissions of the hypervisor (QEMU
process). `More
info <http://lists.gnu.org/archive/html/qemu-devel/2010-05/msg02673.html>`__
info <https://lists.gnu.org/archive/html/qemu-devel/2010-05/msg02673.html>`__
``squash``
Similar to 'passthrough', the exception is that failure of privileged
operations like 'chown' are ignored. This makes a passthrough-like mode
usable for people who run the hypervisor as non-root. `More
info <http://lists.gnu.org/archive/html/qemu-devel/2010-09/msg00121.html>`__
info <https://lists.gnu.org/archive/html/qemu-devel/2010-09/msg00121.html>`__
:since:`Since 5.2.0` , the filesystem element has an optional attribute
``model`` with supported values "virtio-transitional",
@ -3354,7 +3354,7 @@ few exceptions:
For more details see the `qemu patch
posting <https://lists.gnu.org/archive/html/qemu-devel/2018-12/msg00923.html>`__
and the `virtio-1.0
spec <http://docs.oasis-open.org/virtio/virtio/v1.0/virtio-v1.0.html>`__.
spec <https://docs.oasis-open.org/virtio/virtio/v1.0/virtio-v1.0.html>`__.
:anchor:`<a id="elementsControllers"/>`
@ -4461,7 +4461,7 @@ Direct attachment to physical interface
interface of the host. :since:`Since 0.7.7 (QEMU and KVM only)`
| This setup requires the Linux macvtap driver to be available. :since:`(Since
Linux 2.6.34.)` One of the modes 'vepa' ( `'Virtual Ethernet Port
Aggregator' <http://www.ieee802.org/1/files/public/docs2009/new-evb-congdon-vepa-modular-0709-v01.pdf>`__),
Aggregator' <https://www.ieee802.org/1/files/public/docs2009/new-evb-congdon-vepa-modular-0709-v01.pdf>`__),
'bridge' or 'private' can be chosen for the operation mode of the macvtap
device, 'vepa' being the default mode. The individual modes cause the delivery
of packets to behave as follows:
@ -6060,7 +6060,7 @@ type ``serial`` per guest.
Virtio consoles are usually accessible as ``/dev/hvc[0-7]`` from inside the
guest; for more information, see
http://fedoraproject.org/wiki/Features/VirtioSerial. :since:`Since 0.8.3`
https://fedoraproject.org/wiki/Features/VirtioSerial. :since:`Since 0.8.3`
For the relationship between serial ports and consoles, `see
below <#elementCharSerialAndConsole>`__.
@ -6181,7 +6181,7 @@ types have different ``target`` attributes.
Paravirtualized virtio channel. Channel is exposed in the guest under
/dev/vport*, and if the optional element ``name`` is specified,
/dev/virtio-ports/$name (for more info, please see
http://fedoraproject.org/wiki/Features/VirtioSerial). The optional element
https://fedoraproject.org/wiki/Features/VirtioSerial). The optional element
``address`` can tie the channel to a particular ``type='virtio-serial'``
controller, `documented above <#elementsAddress>`__. With qemu, if ``name``
is "org.qemu.guest_agent.0", then libvirt can interact with a guest agent

2
docs/formatstorage.html.in
View File

@ -267,7 +267,7 @@
<dd>Used by the "fc_host" adapter type to optionally specify the
parent scsi_host device defined in the
<a href="formatnode.html">Node Device</a> database as the
<a href="http://wiki.libvirt.org/page/NPIV_in_libvirt">NPIV</a>
<a href="https://wiki.libvirt.org/page/NPIV_in_libvirt">NPIV</a>
virtual Host Bus Adapter (vHBA). The value provided must be
a vport capable scsi_host. The value is not the scsi_host of
the vHBA created by 'virsh nodedev-create', rather it is

4
docs/index.html.in
View File

@ -61,7 +61,7 @@
<a href="formatsnapshot.html">snapshots</a>,
<a href="formatcheckpoint.html">checkpoints</a>,
<a href="formatbackup.html">backup jobs</a></dd>
<dt><a href="http://wiki.libvirt.org">Wiki</a></dt>
<dt><a href="https://wiki.libvirt.org">Wiki</a></dt>
<dd>Read further community contributed content</dd>
<dt><a href="https://libvirt.org/kbase.html">Knowledge base</a></dt>
@ -75,7 +75,7 @@
</div>
<p>
Read more on the <a href="http://planet.virt-tools.org/">Virt Tools blog planet</a>
Read more on the <a href="https://planet.virt-tools.org/">Virt Tools blog planet</a>
</p>
</div>

2
docs/java.html.in
View File

@ -25,7 +25,7 @@ which you can use to include this in your maven projects.</p>
<h2>GIT source repository</h2>
<p> The Java bindings code source is now maintained in a <a
href="http://git-scm.com/">git</a> repository available on
href="https://git-scm.com/">git</a> repository available on
<a href="https://gitlab.com/libvirt/libvirt-java/">gitlab.com</a>:
</p>
<pre>

2
docs/logging.html.in
View File

@ -151,7 +151,7 @@ x:name</pre>
<p>
When logging to the systemd journal, the following fields
are defined, in addition to any automatically recorded
<a href="http://www.freedesktop.org/software/systemd/man/systemd.journal-fields.html">standard fields</a>:
<a href="https://www.freedesktop.org/software/systemd/man/systemd.journal-fields.html">standard fields</a>:
</p>
<dl>

2
docs/logos/README
View File

@ -4,7 +4,7 @@
The master SVG files were created in InkScape, using the Overpass font from Red
Hat:
http://overpassfont.org/
https://overpassfont.org/
Logo formats

2
docs/manpages/virsh.rst
View File

@ -6348,7 +6348,7 @@ algorithms in order to define which algorithm to use for the wipe.
disks: random, 0x00, 0xff, verify.
* bsi - 9-pass method recommended by the German Center of
Security in Information Technologies
(http://www.bsi.bund.de): 0xff, 0xfe, 0xfd, 0xfb,
(https://www.bsi.bund.de): 0xff, 0xfe, 0xfd, 0xfb,
0xf7, 0xef, 0xdf, 0xbf, 0x7f.
* gutmann - The canonical 35-pass sequence described in
Gutmann's paper.

2
docs/nss.html.in
View File

@ -108,7 +108,7 @@ hosts: files libvirt libvirt_guest dns
<p>
Whenever an Unix process wants to do a host name translation
<a href="http://linux.die.net/man/3/gethostbyname"><code>gethostbyname()</code></a>
<a href="https://linux.die.net/man/3/gethostbyname"><code>gethostbyname()</code></a>
or some variant of it is called. This is a glibc function that takes a
string containing the host name, crunch it and produces a list of IP
addresses assigned to that host. Now, glibc developers made a really good

4
docs/page.xsl
View File

@ -161,8 +161,8 @@
<h3>Community</h3>
<ul>
<li><a href="https://twitter.com/hashtag/libvirt">twitter</a></li>
<li><a href="http://stackoverflow.com/questions/tagged/libvirt">stackoverflow</a></li>
<li><a href="http://serverfault.com/questions/tagged/libvirt">serverfault</a></li>
<li><a href="https://stackoverflow.com/questions/tagged/libvirt">stackoverflow</a></li>
<li><a href="https://serverfault.com/questions/tagged/libvirt">serverfault</a></li>
</ul>
</div>
<xsl:if test="$pagesrc != ''">

2
docs/php.html.in
View File

@ -10,7 +10,7 @@
<h2>Getting the source</h2>
<p> The PHP bindings code source is now maintained in a <a
href="http://git-scm.com/">git</a> repository available on
href="https://git-scm.com/">git</a> repository available on
<a href="https://gitlab.com/libvirt/libvirt-php">gitlab.com</a>:
</p>
<pre>

6
docs/remote.html.in
View File

@ -76,7 +76,7 @@ Remote libvirt supports a range of transports:
</dd>
<dt><code>ssh</code></dt>
<dd> Transported over an ordinary
<a href="http://www.openssh.com/" title="OpenSSH homepage">ssh
<a href="https://www.openssh.com/" title="OpenSSH homepage">ssh
(secure shell)</a> connection.
Requires <a href="http://netcat.sourceforge.net/">Netcat (nc)</a>
installed and libvirtd should be running
@ -95,14 +95,14 @@ Remote libvirt supports a range of transports:
The standard port is 16509. </dd>
<dt><code>libssh2</code></dt>
<dd> Transport over the SSH protocol using
<a href="http://libssh2.org/" title="libssh2 homepage">libssh2</a> instead
<a href="https://libssh2.org/" title="libssh2 homepage">libssh2</a> instead
of the OpenSSH binary. This transport uses the libvirt authentication callback for
all ssh authentication calls and therefore supports keyboard-interactive authentication
even with graphical management applications. As with the classic ssh transport
netcat is required on the remote side.</dd>
<dt><code>libssh</code></dt>
<dd> Transport over the SSH protocol using
<a href="http://libssh.org/" title="libssh homepage">libssh</a> instead
<a href="https://libssh.org/" title="libssh homepage">libssh</a> instead
of the OpenSSH binary. This transport uses the libvirt authentication callback for
all ssh authentication calls and therefore supports keyboard-interactive authentication
even with graphical management applications. As with the classic ssh transport

2
docs/storage.html.in
View File

@ -763,7 +763,7 @@
<p>
This provides a pool based on the ZFS filesystem. Initially it was developed
for FreeBSD, and <span class="since">since 1.3.2</span> experimental support
for <a href="http://zfsonlinux.org/">ZFS on Linux</a> version 0.6.4 or newer
for <a href="https://zfsonlinux.org/">ZFS on Linux</a> version 0.6.4 or newer
is available.
</p>

4
docs/testsuites.html.in
View File

@ -19,10 +19,10 @@
</li>
<li>the <a href="testtck.html">TCK test suite</a> is a functional
test suite implemented using the
<a href="http://search.cpan.org/dist/Sys-Virt/">Perl bindings</a>
<a href="https://search.cpan.org/dist/Sys-Virt/">Perl bindings</a>
of libvirt. It is available separately as a
<a href="ftp://libvirt.org/libvirt/tck/">download</a>, as a
<a href="http://rpmfind.net/linux/rpm2html/search.php?query=libvirt-tck">package</a>
<a href="https://rpmfind.net/linux/rpm2html/search.php?query=libvirt-tck">package</a>
in Fedora distributions, but best is probably to get
the <a href="https://gitlab.com/libvirt/libvirt-tck">version
from GIT</a>.

2
docs/testtck.html.in
View File

@ -28,7 +28,7 @@
<li> The initial
<a href="https://www.redhat.com/archives/libvir-list/2009-April/msg00176.html">mail
from Daniel Berrange</a> presenting the project.</li>
<li> The <a href="http://fedoraproject.org/wiki/Features/VirtTCK">page
<li> The <a href="https://fedoraproject.org/wiki/Features/VirtTCK">page
describing VirtTCK</a> the inclusion of libvirt-TCK as a
Fedora Feature.</li>
</ul>

2
docs/tlscerts.html.in
View File

@ -343,7 +343,7 @@ which can be installed on the server as
</h2>
<p>
For each client (ie. any program linked with libvirt, such as
<a href="http://virt-manager.org/">virt-manager</a>)
<a href="https://virt-manager.org/">virt-manager</a>)
you need to issue a certificate with the X.509 Distinguished Name (DN)
set to a suitable name. You can decide this on a company / organisation
policy. For example:

2
docs/uri.html.in
View File

@ -13,7 +13,7 @@ Additionally we may want to refer to a driver on a remote
machine over the network.
</p>
<p>
To this end, libvirt uses URIs as used on the Web and as defined in <a href="http://www.ietf.org/rfc/rfc2396.txt">RFC 2396</a>. This page
To this end, libvirt uses URIs as used on the Web and as defined in <a href="https://www.ietf.org/rfc/rfc2396.txt">RFC 2396</a>. This page
documents libvirt URIs.
</p>
<h2><a id="URI_libvirt">Specifying URIs to libvirt</a></h2>

2
docs/virshcmdref.html.in
View File

@ -67,7 +67,7 @@
<h2><a id="git">DocBook source GIT repository</a></h2>
<p>
The DocBook source is archived in a <a
href="http://git-scm.com/">git</a> repository available on
href="https://git-scm.com/">git</a> repository available on
<a href="https://gitlab.com/libvirt/libvirt-virshcmdref">gitlab.com</a>.
</p>

6
docs/windows.html.in
View File

@ -16,8 +16,8 @@
<p>
Users who need pre-built Windows DLLs of libvirt are advised
to use the <a href="http://virt-manager.org">Virt Viewer</a>
pre-compiled <a href="http://virt-manager.org/download/">Windows MSI packages</a>
to use the <a href="https://virt-manager.org">Virt Viewer</a>
pre-compiled <a href="https://virt-manager.org/download/">Windows MSI packages</a>
</p>
<p>
@ -93,7 +93,7 @@
Information on generating TLS certificates can be found here:
</p>
<a href="http://wiki.libvirt.org/page/TLSSetup">http://wiki.libvirt.org/page/TLSSetup</a>
<a href="https://wiki.libvirt.org/page/TLSSetup">https://wiki.libvirt.org/page/TLSSetup</a>
<p>
These instructions are for *nix, and have not yet been adapted for

2
meson.build
View File

@ -1316,7 +1316,7 @@ if readline_dep.found()
# the fix has landed in FreeBSD ports and macOS homebrew we can safely
# drop the kludge and rely on pkg-config alone on those platforms.
#
# [1] http://lists.gnu.org/archive/html/bug-readline/2019-04/msg00007.html
# [1] https://lists.gnu.org/archive/html/bug-readline/2019-04/msg00007.html
if readline_dep.type_name() == 'pkgconfig' and host_machine.system() != 'linux'
pkg_config_prog = find_program('pkg-config')
rc = run_command(pkg_config_prog, '--cflags', 'readline', check: true)

2
run.in
View File

@ -41,7 +41,7 @@
#----------------------------------------------------------------------
# Function to intelligently prepend a path to an environment variable.
# See http://stackoverflow.com/a/9631350
# See https://stackoverflow.com/a/9631350
prepend()
{
eval $1="$2\${$1:+:\$$1}"

2
src/conf/virchrdev.c
View File

@ -128,7 +128,7 @@ static int virChrdevLockFileCreate(const char *dev)
/* lockfile doesn't (shouldn't) exist */
/* ensure correct format according to filesystem hierarchy standard */
/* http://www.pathname.com/fhs/pub/fhs-2.3.html#VARLOCKLOCKFILES */
/* https://www.pathname.com/fhs/pub/fhs-2.3.html#VARLOCKLOCKFILES */
pidStr = g_strdup_printf("%10lld\n", (long long)getpid());
/* create the lock file */

18
src/esx/README
View File

@ -4,23 +4,23 @@ Some links to relevant documentation
VI/vSphere API:
http://www.vmware.com/support/developer/vc-sdk/visdk25pubs/ReferenceGuide/
http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/
http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/
https://www.vmware.com/support/developer/vc-sdk/visdk25pubs/ReferenceGuide/
https://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/
https://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/
VMX config:
http://www.sanbarrow.com/vmx.html
https://www.sanbarrow.com/vmx.html
CPUID:
http://www.sandpile.org/ia32/cpuid.htm
https://www.sandpile.org/ia32/cpuid.htm
Memory model:
http://www.vmware.com/pdf/esx3_memory.pdf
http://www.vmware.com/pdf/usenix_resource_mgmt.pdf
https://www.vmware.com/pdf/esx3_memory.pdf
https://www.vmware.com/pdf/usenix_resource_mgmt.pdf
Virtual serial port (network backed):
http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.vm.device.VirtualSerialPort.URIBackingInfo.html
http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/vsp41_usingproxy_virtual_serial_ports.pdf
https://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.vm.device.VirtualSerialPort.URIBackingInfo.html
https://www.vmware.com/support/developer/vc-sdk/visdk41pubs/vsp41_usingproxy_virtual_serial_ports.pdf

6
src/esx/esx_driver.c
View File

@ -3375,9 +3375,9 @@ esxDomainSetAutostart(virDomainPtr domain, int autostart)
/*
* The scheduler interface exposes basically the CPU ResourceAllocationInfo:
*
* - http://www.vmware.com/support/developer/vc-sdk/visdk25pubs/ReferenceGuide/vim.ResourceAllocationInfo.html
* - http://www.vmware.com/support/developer/vc-sdk/visdk25pubs/ReferenceGuide/vim.SharesInfo.html
* - http://www.vmware.com/support/developer/vc-sdk/visdk25pubs/ReferenceGuide/vim.SharesInfo.Level.html
* - https://www.vmware.com/support/developer/vc-sdk/visdk25pubs/ReferenceGuide/vim.ResourceAllocationInfo.html
* - https://www.vmware.com/support/developer/vc-sdk/visdk25pubs/ReferenceGuide/vim.SharesInfo.html
* - https://www.vmware.com/support/developer/vc-sdk/visdk25pubs/ReferenceGuide/vim.SharesInfo.Level.html
*
*
* Available parameters:

2
src/hyperv/hyperv_wmi_generator.input
View File

@ -19,7 +19,7 @@
#
#
# Based on MSDN Hyper-V WMI Classes:
# http://msdn.microsoft.com/en-us/library/cc136986%28v=vs.85%29.aspx
# https://msdn.microsoft.com/en-us/library/cc136986%28v=vs.85%29.aspx
#

2
src/internal.h
View File

@ -128,7 +128,7 @@
* whether a parameter is nonnull. Make this attribute conditional
* based on whether we are compiling for real or for analysis, while
* still requiring correct gcc syntax when it is turned off. See also
* http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17308 */
* https://gcc.gnu.org/bugzilla/show_bug.cgi?id=17308 */
#ifndef ATTRIBUTE_NONNULL
# if STATIC_ANALYSIS
# define ATTRIBUTE_NONNULL(m) __attribute__((__nonnull__(m)))

2
src/libxl/libxl_conf.c
View File

@ -567,7 +567,7 @@ libxlMakeDomBuildInfo(virDomainDefPtr def,
* configured when building Xen using '--with-system-ovmf='. If
* not specified, LIBXL_FIRMWARE_DIR/ovmf.bin is used. In the
* future, Xen will support a user-specified firmware path. See
* http://lists.xenproject.org/archives/html/xen-devel/2016-03/msg01628.html
* https://lists.xenproject.org/archives/html/xen-devel/2016-03/msg01628.html
*/
if (virDomainDefHasOldStyleUEFI(def))
b_info->u.hvm.bios = LIBXL_BIOS_TYPE_OVMF;

2
src/lxc/lxc_container.c
View File

@ -1586,7 +1586,7 @@ lxcNeedNetworkNamespace(virDomainDefPtr def)
/* Got a FS mapped to /, we're going the pivot_root
* approach to do a better-chroot-than-chroot
* this is based on this thread http://lkml.org/lkml/2008/3/5/29
* this is based on this thread https://lkml.org/lkml/2008/3/5/29
*/
static int lxcContainerSetupPivotRoot(virDomainDefPtr vmDef,
virDomainFSDefPtr root,

2
src/rpc/virnetdaemon.c
View File

@ -496,7 +496,7 @@ virNetDaemonGotInhibitReply(DBusPendingCall *pending,
}
/* As per: http://www.freedesktop.org/wiki/Software/systemd/inhibit */
/* As per: https://www.freedesktop.org/wiki/Software/systemd/inhibit */
static void
virNetDaemonCallInhibit(virNetDaemonPtr dmn,
const char *what,

2
src/rpc/virnetlibsshsession.c
View File

@ -40,7 +40,7 @@ VIR_LOG_INIT("rpc.netlibsshsession");
/* TRACE_LIBSSH=<level> enables tracing in libssh itself.
* The meaning of <level> is described here:
* http://api.libssh.org/master/group__libssh__log.html
* https://api.libssh.org/master/group__libssh__log.html
*
* The LIBVIRT_LIBSSH_DEBUG environment variable can be used
* to set/override the level of libssh debug.

6
src/storage/storage_backend_gluster.c
View File

@ -334,8 +334,8 @@ virStorageBackendGlusterRefreshPool(virStoragePoolObjPtr pool)
/* Why oh why did glfs 3.4 decide to expose only readdir_r rather
* than readdir? POSIX admits that readdir_r is inherently a
* flawed design, because systems are not required to define
* NAME_MAX: http://austingroupbugs.net/view.php?id=696
* http://womble.decadent.org.uk/readdir_r-advisory.html
* NAME_MAX: https://austingroupbugs.net/view.php?id=696
* https://womble.decadent.org.uk/readdir_r-advisory.html
*
* Fortunately, gluster appears to limit its underlying bricks to
* only use file systems such as XFS that have a NAME_MAX of 255;
@ -343,7 +343,7 @@ virStorageBackendGlusterRefreshPool(virStoragePoolObjPtr pool)
* tail padding, then we should have enough space to avoid buffer
* overflow no matter whether the OS used d_name[], d_name[1], or
* d_name[256] in its 'struct dirent'.
* http://lists.gnu.org/archive/html/gluster-devel/2013-10/msg00083.html
* https://lists.gnu.org/archive/html/gluster-devel/2013-10/msg00083.html
*/
if (!(dir = glfs_opendir(state->vol, state->dir))) {

2
src/storage/storage_util.c
View File

@ -2443,7 +2443,7 @@ virStorageBackendVolDownloadLocal(virStoragePoolObjPtr pool G_GNUC_UNUSED,
* truncate and extend it to its original size, filling it with
* zeroes. This behavior is guaranteed by POSIX:
*
* http://www.opengroup.org/onlinepubs/9699919799/functions/ftruncate.html
* https://www.opengroup.org/onlinepubs/9699919799/functions/ftruncate.html
*
* If fildes refers to a regular file, the ftruncate() function shall
* cause the size of the file to be truncated to length. If the size

2
src/util/virhashcode.c
View File

@ -18,7 +18,7 @@
* <http://www.gnu.org/licenses/>.
*
* The hash code generation is based on the public domain MurmurHash3 from Austin Appleby:
* http://code.google.com/p/smhasher/source/browse/trunk/MurmurHash3.cpp
* https://code.google.com/p/smhasher/source/browse/trunk/MurmurHash3.cpp
*
* We use only the 32 bit variant because the 2 produce different results while
* we need to produce the same result regardless of the architecture as

2
src/util/virhashcode.h
View File

@ -18,7 +18,7 @@
* <http://www.gnu.org/licenses/>.
*
* The hash code generation is based on the public domain MurmurHash3 from Austin Appleby:
* http://code.google.com/p/smhasher/source/browse/trunk/MurmurHash3.cpp
* https://code.google.com/p/smhasher/source/browse/trunk/MurmurHash3.cpp
*
* We use only the 32 bit variant because the 2 produce different result while
* we need to produce the same result regardless of the architecture as

2
src/util/virprocess.c
View File

@ -455,7 +455,7 @@ int virProcessSetAffinity(pid_t pid, virBitmapPtr map)
* So you have no option but to pick a size, try, catch EINVAL,
* enlarge, and re-try.
*
* http://lkml.org/lkml/2009/7/28/620
* https://lkml.org/lkml/2009/7/28/620
*/
realloc:
masklen = CPU_ALLOC_SIZE(numcpus);

2
src/util/virsysinfo.c
View File

@ -1295,7 +1295,7 @@ virSysinfoRead(void)
#else /* WIN32 || not supported arch */
/*
* this can probably be extracted from Windows using API or registry
* http://www.microsoft.com/whdc/system/platform/firmware/SMBIOS.mspx
* https://www.microsoft.com/whdc/system/platform/firmware/SMBIOS.mspx
*/
virReportSystemError(ENOSYS, "%s",
_("Host sysinfo extraction not supported on this platform"));

2
src/util/virutil.c
View File

@ -140,7 +140,7 @@ int virSetSockReuseAddr(int fd G_GNUC_UNUSED, bool fatal G_GNUC_UNUSED)
* Win32 sockets have Linux/BSD-like SO_REUSEADDR behaviour
* by default, so we can be a no-op.
*
* http://msdn.microsoft.com/en-us/library/windows/desktop/ms740621.aspx
* https://msdn.microsoft.com/en-us/library/windows/desktop/ms740621.aspx
*/
return 0;
}

6
src/vmx/vmx.c
View File

@ -1559,7 +1559,7 @@ virVMXParseConfig(virVMXContext *ctx,
if (sched_cpu_shares != NULL) {
unsigned int vcpus = virDomainDefGetVcpus(def);
/* See http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.SharesInfo.Level.html */
/* See https://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.SharesInfo.Level.html */
if (STRCASEEQ(sched_cpu_shares, "low")) {
def->cputune.shares = vcpus * 500;
} else if (STRCASEEQ(sched_cpu_shares, "normal")) {
@ -3282,7 +3282,7 @@ virVMXFormatConfig(virVMXContext *ctx, virDomainXMLOptionPtr xmlopt, virDomainDe
/* def:cputune.shares -> vmx:sched.cpu.shares */
if (def->cputune.sharesSpecified) {
unsigned int vcpus = virDomainDefGetVcpus(def);
/* See http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.SharesInfo.Level.html */
/* See https://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/vim.SharesInfo.Level.html */
if (def->cputune.shares == vcpus * 500) {
virBufferAddLit(&buffer, "sched.cpu.shares = \"low\"\n");
} else if (def->cputune.shares == vcpus * 1000) {
@ -4072,7 +4072,7 @@ virVMXFormatSVGA(virDomainVideoDefPtr def, virBufferPtr buffer)
/*
* For Windows guests the VRAM size should be a multiple of 64 kilobyte.
* See http://kb.vmware.com/kb/1003 and http://kb.vmware.com/kb/1001558
* See https://kb.vmware.com/kb/1003 and https://kb.vmware.com/kb/1001558
*/
vram = VIR_DIV_UP(def->vram, 64) * 64;

2
tests/cputestdata/cpu-gather.sh
View File

@ -2,7 +2,7 @@
#
# The cpuid tool can be usually found in a package called "cpuid". If your
# distro does not provide such package, you can find the sources or binary
# packages at http://www.etallen.com/cpuid.html
# packages at https://www.etallen.com/cpuid.html
grep 'model name' /proc/cpuinfo | head -n1

2
tools/wireshark/README.rst
View File

@ -11,7 +11,7 @@ specification.
See also:
* http://www.google-melange.com/gsoc/project/google/gsoc2013/kawamuray/7001
* https://www.google-melange.com/gsoc/project/google/gsoc2013/kawamuray/7001
* https://wiki.qemu.org/Features/LibvirtWiresharkDissector

2
tools/wireshark/util/genxdrstub.pl
View File

@ -18,7 +18,7 @@
# <http://www.gnu.org/licenses/>.
#
#
# For XDR syntax, see http://tools.ietf.org/html/rfc4506#section-6.3
# For XDR syntax, see https://tools.ietf.org/html/rfc4506#section-6.3
# This script does not strictly check syntax of xdr protocol specification.
# Make sure the specification files you have are correctly compilable with rpcgen(1).
# If something fails with this script in spite of you had confirmed that the `make' with libvirt was succeed,