mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-23 21:34:54 +03:00
b1c81567c7
The HTML5 doctype is simply <!DOCTYPE html> no DTD is present because HTML5 is no longer defined as an extension of SGML. XSL has no way to natively output a doctype without a public or system identifier, so we have to use an <xsl:text> hack instead. See also https://dev.w3.org/html5/html-author/#doctype-declaration Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
49 lines
1.9 KiB
XML
49 lines
1.9 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE html>
|
|
<html xmlns="http://www.w3.org/1999/xhtml">
|
|
<body>
|
|
<h1>Virtual machine lock manager</h1>
|
|
|
|
<ul id="toc"></ul>
|
|
|
|
<p>
|
|
Libvirt includes a framework for ensuring mutual exclusion
|
|
between virtual machines using host resources. Typically
|
|
this is used to prevent two VM processes from having concurrent
|
|
write access to the same disk image, as this would result in
|
|
data corruption if the guest was not using a cluster
|
|
aware filesystem.
|
|
</p>
|
|
|
|
<h2><a id="plugins">Lock manager plugins</a></h2>
|
|
|
|
<p>
|
|
The lock manager framework has a pluggable architecture,
|
|
to allow different locking technologies to be used.
|
|
</p>
|
|
|
|
<dl>
|
|
<dt><code>nop</code></dt>
|
|
<dd>This is a "no op" implementation which does absolutely
|
|
nothing. This can be used if mutual exclusion between
|
|
virtual machines is not required, or if it is being
|
|
solved at another level in the management stack.</dd>
|
|
<dt><code><a href="locking-lockd.html">lockd</a></code></dt>
|
|
<dd>This is the current preferred implementation shipped
|
|
with libvirt. It uses the <code>virtlockd</code> daemon
|
|
to manage locks using the POSIX fcntl() advisory locking
|
|
capability. As such it requires a shared filesystem of
|
|
some kind be accessible to all hosts which share the
|
|
same image storage.</dd>
|
|
<dt><code><a href="locking-sanlock.html">sanlock</a></code></dt>
|
|
<dd>This is an alternative implementation preferred by
|
|
the oVirt project. It uses a disk paxos algorithm for
|
|
maintaining continuously renewed leases. In the default
|
|
setup it requires some shared filesystem, but it is
|
|
possible to use it in a manual mode where the management
|
|
application creates leases in SAN storage volumes.
|
|
</dd>
|
|
</dl>
|
|
</body>
|
|
</html>
|