From nobody Sun Feb 8 19:44:01 2026
Delivered-To: importer@patchew.org
Received-SPF: pass (zohomail.com: domain of redhat.com designates
207.211.31.81 as permitted sender) client-ip=207.211.31.81;
envelope-from=libvir-list-bounces@redhat.com;
helo=us-smtp-delivery-1.mimecast.com;
Authentication-Results: mx.zohomail.com;
dkim=pass;
spf=pass (zohomail.com: domain of redhat.com designates 207.211.31.81 as
permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com;
dmarc=pass(p=none dis=none) header.from=redhat.com
ARC-Seal: i=1; a=rsa-sha256; t=1598534946; cv=none;
d=zohomail.com; s=zohoarc;
b=OQBHXp1XEgo4hgRPZABuZXcs2LycCkziTYKsHLEehSRqDL3JVfV7mahsccOF9POjLhSpgkD9woQaGALGjrtnMruD/4Q6huCByVDMcOadYURF5PilaJoE9NREZ9E3Kc18chDV8Ovl8eoIpHGPbloC9jiVOwAszC7g0TSWiuhnMoY=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com;
s=zohoarc;
t=1598534946;
h=Content-Type:Content-Transfer-Encoding:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To;
bh=YpZEve18du3qQKsB8MjYSnOWYD3q7YCAUdQUOoJCiEM=;
b=SiAXz9rGnyYL0JJoEjlpWVb5ZW87iOA+wHsvItXjLzVeRD9WUBVKwiLnwwQQn9aIW9391pLq9rNGVFADRGMfBVRnDG0LdAquT9nuMuxk5ANhs+ykLIHCsfDywSUIDA4pFrcdNuruGzJhgjU3hkzcG1gaHqoyrdPR3gshUt4VZxI=
ARC-Authentication-Results: i=1; mx.zohomail.com;
dkim=pass;
spf=pass (zohomail.com: domain of redhat.com designates 207.211.31.81 as
permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com;
dmarc=pass header.from=
A default install of libvirt will typically use
- polkit<=
/a>
+ polkit=
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
diff --git a/docs/advanced-tests.rst b/docs/advanced-tests.rst
index 458a9105b6..772fe1dd16 100644
--- a/docs/advanced-tests.rst
+++ b/docs/advanced-tests.rst
@@ -18,7 +18,7 @@ by running
=20
$ meson test --setup valgrind
=20
-`Valgrind A 16 byte unique identifier
- as defined in RFC 41=
22,
+ as defined in RFC 4=
122,
which is guaranteed to be unique for long term usage and across a
set of nodes.none
driver is used, which does no access control checks at
all. At this time, libvirt ships with support for using
- polkit<=
/a> as a real access
+ polkit=
as a real access
control driver. To learn how to use the polkit access
driver consult the configuration
docs.
diff --git a/docs/aclpolkit.html.in b/docs/aclpolkit.html.in
index 8bd8b58e02..a82001187e 100644
--- a/docs/aclpolkit.html.in
+++ b/docs/aclpolkit.html.in
@@ -18,7 +18,7 @@
=20
UUID
If you are interested in contributing to libvirt, read the - FAQ and + FAQ and hacking guidelines to gain an understandi= ng of basic rules and guidelines. In order to add new API functionality follow the instructions regarding diff --git a/docs/apps.html.in b/docs/apps.html.in index 92f7950b07..a5696967fd 100644 --- a/docs/apps.html.in +++ b/docs/apps.html.in @@ -128,7 +128,7 @@
@@ -60,7 +60,7 @@
This is named libvirt-python on RHEL/Fedora, - python-libvirt + python-libvirt on Ubuntu, and may be named differently on others.
diff --git a/docs/coding-style.rst b/docs/coding-style.rst index 9212a42a77..00d95b960f 100644 --- a/docs/coding-style.rst +++ b/docs/coding-style.rst @@ -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=3D1408, which will +https://www.vim.org/scripts/script.php?script_id=3D1408, which will load the .lvimrc only when you edit libvirt code. =20 Code formatting (especially for new code) diff --git a/docs/contact.html.in b/docs/contact.html.in index 7c2b71501a..ad95800b1b 100644 --- a/docs/contact.html.in +++ b/docs/contact.html.in @@ -98,7 +98,7 @@
- Some of the libvirt developers may be found on IRC on the OFTC IRC + Some of the libvirt developers may be found on IRC on the OFTC IRC network. Use the settings:
Since 2016, the libvirt project directly participates as an - organization in the Google Summer of Code program. Prior to + organization in the Google Summer of Code program. 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 diff --git a/docs/csharp.html.in b/docs/csharp.html.in index 89b3957904..257637495d 100644 --- a/docs/csharp.html.in +++ b/docs/csharp.html.in @@ -32,7 +32,7 @@
The C# bindings source code is maintained in a git repository available on + href=3D"https://git-scm.com/">git repository available on gitlab.com:
=20 diff --git a/docs/docs.html.in b/docs/docs.html.in index ceb95a4f17..428a2ac974 100644 --- a/docs/docs.html.in +++ b/docs/docs.html.in @@ -48,7 +48,7 @@For more details about contents of maintenance releases, see - the + the wiki page.
=20 diff --git a/docs/drvbhyve.html.in b/docs/drvbhyve.html.in index 66a13be1f6..ca511eeccd 100644 --- a/docs/drvbhyve.html.in +++ b/docs/drvbhyve.html.in @@ -28,7 +28,7 @@ $ =20-Additional information on bhyve could be obtained on bhyve.org. +Additional information on bhyve could be obtained on bhyve.org.
=20NB: 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 -r262884. If +r262884. = If an older version is used, one either has to open a console manually with <= code>virsh console to let a guest boot or start a guest using:
=20 @@ -392,8 +392,8 @@ it with theport attribute):
Originally bhyve supported only localtime for RTC. Support for UTC time= was introduced in -r284894 fo= r 10-STABLE and -in r279225= for -CURRENT. +r284894 f= or 10-STABLE and +in r279225 for -CURRENT. It's possible to use this in libvirt since 1.2.18, just place the following to domain XML:
=20 @@ -450,7 +450,7 @@ be wired and cannot be swapped out as follows: =20Since 4.5.0, it's possible to specify gues= t CPU topology, if bhyve supports that. Support for specifying guest CPU topology was added to bhyv= e in -r332298 fo= r -CURRENT. +r332298 f= or -CURRENT. Example:
<domain type=3D"bhyve">
diff --git a/docs/drvesx.html.in b/docs/drvesx.html.in
index 59b27bd43e..e25cf07e92 100644
--- a/docs/drvesx.html.in
+++ b/docs/drvesx.html.in
@@ -15,7 +15,7 @@
=20
vmpvscsivmxnet, vmxnet2, vmxnet3e1000When the container "init" process is started, it will be given several use= ful environment variables. The following standard environment variables are ma= ndated -by systemd container interface +by systemd container interface to be provided by all container technologies on Linux.
=20 diff --git a/docs/drvnodedev.html.in b/docs/drvnodedev.html.in index e28af4e737..ab87b6bbd2 100644 --- a/docs/drvnodedev.html.in +++ b/docs/drvnodedev.html.in @@ -20,7 +20,7 @@ (virsh nodedev-create, virsh nodedev-destroy)
which are meant to be used to create virtual devices, currently only
supported by NPIV
- (more info =
about NPIV)).
+ (more info=
about NPIV)).
Devices on the host system are arranged in a tree-like hierarchy, wi=
th
the root node being called computer. The node device dr=
iver
supports two backends to manage the devices, HAL and udev, with the =
former
diff --git a/docs/drvopenvz.html.in b/docs/drvopenvz.html.in
index 2dc53c1340..64a75e3fec 100644
--- a/docs/drvopenvz.html.in
+++ b/docs/drvopenvz.html.in
@@ -19,7 +19,7 @@
=20
@@ -54,7 +54,7 @@ openvz+ssh://root@example.com/system (remote access, SSH =
tunnelled)
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 W=
iki
+ for up to date notes consult the =
Wiki
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".
diff --git a/docs/drvvbox.html.in b/docs/drvvbox.html.in
index c97dc0f049..0c0d14fa6a 100644
--- a/docs/drvvbox.html.in
+++ b/docs/drvvbox.html.in
@@ -13,7 +13,7 @@
=20
-
- The VirtualBox
+ The VirtualBox
hypervisor
diff --git a/docs/drvvmware.html.in b/docs/drvvmware.html.in
index caa99e257d..d581ad1d1c 100644
--- a/docs/drvvmware.html.in
+++ b/docs/drvvmware.html.in
@@ -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
- here.
+ here.
This driver uses the "vmrun" utility which is distributed with the VMw=
are VIX API.
You can download the VIX API
- from here=
.
+ from her=
e.
=20
Project Links
=20
-
- The VMware Workstation and
+ The VMware Workstation and
Player hypervisors
-
- The VMware Fusion
+ The VMware Fusion
hypervisor
diff --git a/docs/firewall.html.in b/docs/firewall.html.in
index 2d55021d9b..62f37e0eea 100644
--- a/docs/firewall.html.in
+++ b/docs/firewall.html.in
@@ -175,7 +175,7 @@ MASQUERADE all -- * * 192.168.122.0/24 =
!192.168.122.0/24
the conceptual model is closely aligned with the DMTF CIM schema for
network filtering:
- http://www.dmtf.org/standards/cim/cim_schema_v2230/CIM_Network.=
pdf
+ https://www.dmtf.org/standards/cim/cim_schema_v2230/CIM_Networ=
k.pdf
The filters are managed in libvirt as a top level, standalone objec=
t.
This allows the filters to then be referenced by any libvirt object
that requires their functionality, instead tying them only to use
diff --git a/docs/formatdomain.rst b/docs/formatdomain.rst
index 9da1320f1c..250beb4b76 100644
--- a/docs/formatdomain.rst
+++ b/docs/formatdomain.rst
@@ -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=3D'iscsi'`` or when the ``type``=
is
"volume" when using an iSCSI source ``pool`` for ``mode`` "host" or =
as an
- `NPIV `__ virtual Host=
Bus
+ `NPIV `__ virtual Hos=
t Bus
Adapter (vHBA) using a Fibre Channel storage pool. Configured in this
manner, the LUN behaves identically to "disk", except that generic S=
CSI
commands from the guest are accepted and passed through to the physi=
cal
@@ -3118,16 +3118,16 @@ A directory on the host that can be accessed direct=
ly from the guest.
``passthrough``
The ``source`` is accessed with the permissions of the user inside t=
he
guest. This is the default ``accessmode`` if one is not specified. `=
More
- info `__
+ info `__
``mapped``
The ``source`` is accessed with the permissions of the hypervisor (Q=
EMU
process). `More
- info `__
+ info `__
``squash``
Similar to 'passthrough', the exception is that failure of privileged
operations like 'chown' are ignored. This makes a passthrough-like m=
ode
usable for people who run the hypervisor as non-root. `More
- info `__
+ info `__
=20
: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 `__
and the `virtio-1.0
-spec `__.
+spec `__.
=20
:anchor:``
=20
@@ -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:`(S=
ince
Linux 2.6.34.)` One of the modes 'vepa' ( `'Virtual Ethernet Port
- Aggregator' `__),
+ Aggregator' `__),
'bridge' or 'private' can be chosen for the operation mode of the macvtap
device, 'vepa' being the default mode. The individual modes cause the de=
livery
of packets to behave as follows:
@@ -6060,7 +6060,7 @@ type ``serial`` per guest.
=20
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`
=20
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 elem=
ent
+ https://fedoraproject.org/wiki/Features/VirtioSerial). The optional ele=
ment
``address`` can tie the channel to a particular ``type=3D'virtio-serial=
'``
controller, `documented above <#elementsAddress>`__. With qemu, if ``na=
me``
is "org.qemu.guest_agent.0", then libvirt can interact with a guest age=
nt
diff --git a/docs/formatstorage.html.in b/docs/formatstorage.html.in
index 7493714c5c..8eee7ccf9e 100644
--- a/docs/formatstorage.html.in
+++ b/docs/formatstorage.html.in
@@ -267,7 +267,7 @@
- Used by the "fc_host" adapter type to optionally specify the
parent scsi_host device defined in the
Node Device database as the
- NPIV<=
/a>
+ NPIV=
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
diff --git a/docs/index.html.in b/docs/index.html.in
index 20184a7441..97421c5e7b 100644
--- a/docs/index.html.in
+++ b/docs/index.html.in
@@ -61,7 +61,7 @@
snapshots,
checkpoints,
backup jobs
- - Wiki
+ - Wiki
- Read further community contributed content
=20
- Knowledge base<=
/dt>
@@ -75,7 +75,7 @@
=20
- Read more on the Virt To=
ols blog planet
+ Read more on the Virt T=
ools blog planet
=20
diff --git a/docs/java.html.in b/docs/java.html.in
index fa3fe8f900..1f8c255d26 100644
--- a/docs/java.html.in
+++ b/docs/java.html.in
@@ -25,7 +25,7 @@ which you can use to include this in your maven projects.=
=20
GIT source repository
The Java bindings code source is now maintained in a git repository available on
+href=3D"https://git-scm.com/">git repository available on
gitlab.com:
diff --git a/docs/logging.html.in b/docs/logging.html.in
index 3ff0dd3eb6..1052b763a0 100644
--- a/docs/logging.html.in
+++ b/docs/logging.html.in
@@ -151,7 +151,7 @@ x:name
When logging to the systemd journal, the following fields
are defined, in addition to any automatically recorded
- standard fields:
+ standard fields:
=20
diff --git a/docs/logos/README b/docs/logos/README
index bd37f5470f..888ba18798 100644
--- a/docs/logos/README
+++ b/docs/logos/README
@@ -4,7 +4,7 @@
The master SVG files were created in InkScape, using the Overpass font fro=
m Red
Hat:
=20
- http://overpassfont.org/
+ https://overpassfont.org/
=20
=20
Logo formats
diff --git a/docs/manpages/virsh.rst b/docs/manpages/virsh.rst
index 0482fe8b26..7c9240faf3 100644
--- a/docs/manpages/virsh.rst
+++ b/docs/manpages/virsh.rst
@@ -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.
diff --git a/docs/nss.html.in b/docs/nss.html.in
index 4b11bf0c7c..5c58d1bd49 100644
--- a/docs/nss.html.in
+++ b/docs/nss.html.in
@@ -108,7 +108,7 @@ hosts: files libvirt libvirt_guest dns
=20
Whenever an Unix process wants to do a host name translation
- gethostbyna=
me()
+ gethostbyn=
ame()
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 g=
ood
diff --git a/docs/page.xsl b/docs/page.xsl
index 9ab8d3dd69..36168305fa 100644
--- a/docs/page.xsl
+++ b/docs/page.xsl
@@ -161,8 +161,8 @@
Community
diff --git a/docs/php.html.in b/docs/php.html.in
index 1605175976..9340c81eec 100644
--- a/docs/php.html.in
+++ b/docs/php.html.in
@@ -10,7 +10,7 @@
=20
Getting the source
The PHP bindings code source is now maintained in a git repository available on
+href=3D"https://git-scm.com/">git repository available on
gitlab.com:
diff --git a/docs/remote.html.in b/docs/remote.html.in
index 9b06e8a449..cc8db80c95 100644
--- a/docs/remote.html.in
+++ b/docs/remote.html.in
@@ -76,7 +76,7 @@ Remote libvirt supports a range of transports:
ssh
- Transported over an ordinary
- ssh
+ ssh
(secure shell) connection.
Requires Netcat (nc)
installed and libvirtd should be running
@@ -95,14 +95,14 @@ Remote libvirt supports a range of transports:
The standard port is 16509.
libssh2
- Transport over the SSH protocol using
- libssh2=
a> instead
+ libssh2<=
/a> instead
of the OpenSSH binary. This transport uses the libvirt authentication call=
back for
all ssh authentication calls and therefore supports keyboard-interactive a=
uthentication
even with graphical management applications. As with the classic ssh trans=
port
netcat is required on the remote side.
libssh
- Transport over the SSH protocol using
- libssh =
instead
+ libssh=
instead
of the OpenSSH binary. This transport uses the libvirt authentication call=
back for
all ssh authentication calls and therefore supports keyboard-interactive a=
uthentication
even with graphical management applications. As with the classic ssh trans=
port
diff --git a/docs/storage.html.in b/docs/storage.html.in
index 72fa13944a..b2cf343933 100644
--- a/docs/storage.html.in
+++ b/docs/storage.html.in
@@ -763,7 +763,7 @@
This provides a pool based on the ZFS filesystem. Initially it was d=
eveloped
for FreeBSD, and since 1.3.2 experiment=
al support
- for ZFS on Linux version 0.6.=
4 or newer
+ for ZFS on Linux version 0.6=
.4 or newer
is available.
=20
diff --git a/docs/testsuites.html.in b/docs/testsuites.html.in
index cd9cad9160..2e61684b63 100644
--- a/docs/testsuites.html.in
+++ b/docs/testsuites.html.in
@@ -19,10 +19,10 @@
- the TCK test suite is a functional
test suite implemented using the
- Perl bindings<=
/a>
+ Perl bindings=
of libvirt. It is available separately as a
download, as a
- package
+ package
in Fedora distributions, but best is probably to get
the version
from GIT.
diff --git a/docs/testtck.html.in b/docs/testtck.html.in
index 5925752900..137586682b 100644
--- a/docs/testtck.html.in
+++ b/docs/testtck.html.in
@@ -28,7 +28,7 @@
- The initial
mail
from Daniel Berrange presenting the project.
- - The =
page
+
- The page
describing VirtTCK the inclusion of libvirt-TCK as a
Fedora Feature.
For each client (ie. any program linked with libvirt, such as -virt-manager) +virt-manager) 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: diff --git a/docs/uri.html.in b/docs/uri.html.in index 49f92773f8..429768116b 100644 --- a/docs/uri.html.in +++ b/docs/uri.html.in @@ -13,7 +13,7 @@ Additionally we may want to refer to a driver on a remote machine over the network.
-To this end, libvirt uses URIs as used on the Web and as defined in RFC 2396. This page +To this end, libvirt uses URIs as used on the Web and as defined in RFC 2396. This page documents libvirt URIs.
The DocBook source is archived in a git repository available on + href=3D"https://git-scm.com/">git repository available on gitlab.co= m.
=20 diff --git a/docs/windows.html.in b/docs/windows.html.in index 13dab1f6a4..0f2d9061c4 100644 --- a/docs/windows.html.in +++ b/docs/windows.html.in @@ -16,8 +16,8 @@ =20Users who need pre-built Windows DLLs of libvirt are advised - to use the Virt Viewer - pre-compiled Windows M= SI packages + to use the Virt Viewer + pre-compiled Windows = MSI packages
=20@@ -93,7 +93,7 @@ Information on generating TLS certificates can be found here:
=20 - http://wiki.libvirt.= org/page/TLSSetup + https://wiki.libvir= t.org/page/TLSSetup =20
These instructions are for *nix, and have not yet been adapted for
diff --git a/meson.build b/meson.build
index dabd4196e6..3c138b77d5 100644
--- a/meson.build
+++ b/meson.build
@@ -1313,7 +1313,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.ht=
ml
+ # [1] https://lists.gnu.org/archive/html/bug-readline/2019-04/msg00007.h=
tml
if readline_dep.type_name() =3D=3D 'pkgconfig' and host_machine.system()=
!=3D 'linux'
pkg_config_prog =3D find_program('pkg-config')
rc =3D run_command(pkg_config_prog, '--cflags', 'readline', check: tru=
e)
diff --git a/run.in b/run.in
index 73bebbf805..6ddf5fc58f 100644
--- a/run.in
+++ b/run.in
@@ -41,7 +41,7 @@
#----------------------------------------------------------------------
=20
# 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=3D"$2\${$1:+:\$$1}"
diff --git a/src/conf/virchrdev.c b/src/conf/virchrdev.c
index 800e82869e..635aa43c49 100644
--- a/src/conf/virchrdev.c
+++ b/src/conf/virchrdev.c
@@ -128,7 +128,7 @@ static int virChrdevLockFileCreate(const char *dev)
/* lockfile doesn't (shouldn't) exist */
=20
/* 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 =3D g_strdup_printf("%10lld\n", (long long)getpid());
=20
/* create the lock file */
diff --git a/src/esx/README b/src/esx/README
index b7a5865cd8..372227cc9c 100644
--- a/src/esx/README
+++ b/src/esx/README
@@ -4,23 +4,23 @@ Some links to relevant documentation
=20
=20
VI/vSphere API:
- http://www.vmware.com/support/developer/vc-sdk/visdk25pubs/ReferenceGuid=
e/
- http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGui=
de/
- http://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/
+ https://www.vmware.com/support/developer/vc-sdk/visdk25pubs/ReferenceGui=
de/
+ https://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGu=
ide/
+ https://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/
=20
VMX config:
- http://www.sanbarrow.com/vmx.html
+ https://www.sanbarrow.com/vmx.html
=20
CPUID:
- http://www.sandpile.org/ia32/cpuid.htm
+ https://www.sandpile.org/ia32/cpuid.htm
=20
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
=20
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_usingpr=
oxy_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_usingp=
roxy_virtual_serial_ports.pdf
=20
=20
=20
diff --git a/src/esx/esx_driver.c b/src/esx/esx_driver.c
index 3fb7a3b62c..9080478435 100644
--- a/src/esx/esx_driver.c
+++ b/src/esx/esx_driver.c
@@ -3375,9 +3375,9 @@ esxDomainSetAutostart(virDomainPtr domain, int autost=
art)
/*
* The scheduler interface exposes basically the CPU ResourceAllocationInf=
o:
*
- * - http://www.vmware.com/support/developer/vc-sdk/visdk25pubs/ReferenceG=
uide/vim.ResourceAllocationInfo.html
- * - http://www.vmware.com/support/developer/vc-sdk/visdk25pubs/ReferenceG=
uide/vim.SharesInfo.html
- * - http://www.vmware.com/support/developer/vc-sdk/visdk25pubs/ReferenceG=
uide/vim.SharesInfo.Level.html
+ * - https://www.vmware.com/support/developer/vc-sdk/visdk25pubs/Reference=
Guide/vim.ResourceAllocationInfo.html
+ * - https://www.vmware.com/support/developer/vc-sdk/visdk25pubs/Reference=
Guide/vim.SharesInfo.html
+ * - https://www.vmware.com/support/developer/vc-sdk/visdk25pubs/Reference=
Guide/vim.SharesInfo.Level.html
*
*
* Available parameters:
diff --git a/src/hyperv/hyperv_wmi_generator.input b/src/hyperv/hyperv_wmi_=
generator.input
index da19765f1b..77543cf6ef 100644
--- a/src/hyperv/hyperv_wmi_generator.input
+++ b/src/hyperv/hyperv_wmi_generator.input
@@ -19,7 +19,7 @@
#
#
# Based on MSDN Hyper-V WMI Classes:
-# http://msdn.microsoft.com/en-us/library/cc136986%28v=3Dvs.85%29.aspx
+# https://msdn.microsoft.com/en-us/library/cc136986%28v=3Dvs.85%29.aspx
#
=20
=20
diff --git a/src/internal.h b/src/internal.h
index d95db330b3..1a5ad2bfef 100644
--- a/src/internal.h
+++ b/src/internal.h
@@ -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=3D17308 */
+ * https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D17308 */
#ifndef ATTRIBUTE_NONNULL
# if STATIC_ANALYSIS
# define ATTRIBUTE_NONNULL(m) __attribute__((__nonnull__(m)))
diff --git a/src/libxl/libxl_conf.c b/src/libxl/libxl_conf.c
index e7c7022b69..9ae8ad1860 100644
--- a/src/libxl/libxl_conf.c
+++ b/src/libxl/libxl_conf.c
@@ -567,7 +567,7 @@ libxlMakeDomBuildInfo(virDomainDefPtr def,
* configured when building Xen using '--with-system-ovmf=3D'. 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/msg=
01628.html
+ * https://lists.xenproject.org/archives/html/xen-devel/2016-03/ms=
g01628.html
*/
if (virDomainDefHasOldStyleUEFI(def))
b_info->u.hvm.bios =3D LIBXL_BIOS_TYPE_OVMF;
diff --git a/src/lxc/lxc_container.c b/src/lxc/lxc_container.c
index ede419c275..d1aa622be4 100644
--- a/src/lxc/lxc_container.c
+++ b/src/lxc/lxc_container.c
@@ -1586,7 +1586,7 @@ lxcNeedNetworkNamespace(virDomainDefPtr def)
=20
/* 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,
diff --git a/src/rpc/virnetdaemon.c b/src/rpc/virnetdaemon.c
index bb81a43d43..81c2816e6e 100644
--- a/src/rpc/virnetdaemon.c
+++ b/src/rpc/virnetdaemon.c
@@ -496,7 +496,7 @@ virNetDaemonGotInhibitReply(DBusPendingCall *pending,
}
=20
=20
-/* 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,
diff --git a/src/rpc/virnetlibsshsession.c b/src/rpc/virnetlibsshsession.c
index 3ae53392ef..81646a360a 100644
--- a/src/rpc/virnetlibsshsession.c
+++ b/src/rpc/virnetlibsshsession.c
@@ -40,7 +40,7 @@ VIR_LOG_INIT("rpc.netlibsshsession");
=20
/* TRACE_LIBSSH=3D