NuKVM/libvirt
3
0
Fork 0
mirror of https://github.com/libvirt/libvirt.git synced 2025-02-25 18:55:26 -06:00
Code Issues Packages Projects Releases Wiki Activity

Prefer https: for Wikipedia links

Browse Source 
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:46:53 +02:00
parent 4216192929
commit 4e7a27b610
7 changed files with 42 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/formatdomain.rst
View File

@@ -1036,7 +1036,7 @@ Memory Tuning
QEMU and KVM are strongly advised not to set this limit as domain may get
killed by the kernel if the guess is too low, and determining the memory
needed for a process to run is an `undecidable
problem <http://en.wikipedia.org/wiki/Undecidable_problem>`__; that said, if
problem <https://en.wikipedia.org/wiki/Undecidable_problem>`__; that said, if
you already set ``locked`` in `memory backing <#elementsMemoryBacking>`__
because your workload demands it, you'll have to take into account the
specifics of your deployment and figure out a value for ``hard_limit`` that

2
docs/internals/rpc.html.in
View File

@@ -22,7 +22,7 @@
<p>
libvirt uses a simple, variable length, packet based RPC protocol.
All structured data within packets is encoded using the
<a href="http://en.wikipedia.org/wiki/External_Data_Representation">XDR standard</a>
<a href="https://en.wikipedia.org/wiki/External_Data_Representation">XDR standard</a>
as currently defined by <a href="https://tools.ietf.org/html/rfc4506">RFC 4506</a>.
On any connection running the RPC protocol, there can be multiple
programs active, each supporting one or more versions. A program

2
docs/remote.html.in
View File

@@ -58,7 +58,7 @@ Remote libvirt supports a range of transports:
</p>
<dl>
<dt><code>tls</code></dt>
<dd><a href="http://en.wikipedia.org/wiki/Transport_Layer_Security" title="Transport Layer Security">TLS</a>
<dd><a href="https://en.wikipedia.org/wiki/Transport_Layer_Security" title="Transport Layer Security">TLS</a>
1.0 (SSL 3.1) authenticated and encrypted TCP/IP socket, usually
listening on a public port number. To use this you will need to
<a href="tlscerts.html" title="Generating TLS certificates">generate client and

2
docs/securityprocess.html.in
View File

@@ -78,7 +78,7 @@
<p>
The libvirt security team operates a policy of
<a href="http://en.wikipedia.org/wiki/Responsible_disclosure">responsible disclosure</a>.
<a href="https://en.wikipedia.org/wiki/Responsible_disclosure">responsible disclosure</a>.
As such any security issue reported, that is not already publicly disclosed
elsewhere, will have an embargo date assigned. Members of the security team agree
not to publicly disclose any details of the security issue until the embargo

2
docs/tlscerts.html.in
View File

@@ -135,7 +135,7 @@ server. May be enabled and disabled in the <a href="#Remote_libvirtd_configurat
</ul>
<p>
For full certificate checking you will need to have certificates
issued by a recognised <a href="http://en.wikipedia.org/wiki/Certificate_authority">Certificate
issued by a recognised <a href="https://en.wikipedia.org/wiki/Certificate_authority">Certificate
Authority (CA)</a> for your server(s) and all clients. To avoid the
expense of getting certificates from a commercial CA, you can set up
your own CA and tell your server(s) and clients to trust certificates