/usr/share/doc/drbd-doc/users-guide/ch-xen.html is in drbd-doc 8.4~20140825-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 | <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 13. Using Xen with DRBD</title><link rel="stylesheet" type="text/css" href="default.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /><link rel="home" href="drbd-users-guide.html" title="The DRBD User’s Guide" /><link rel="up" href="p-apps.html" title="Part IV. DRBD-enabled applications" /><link rel="prev" href="s-ocfs2-legacy.html" title="12.5. Legacy OCFS2 management (without Pacemaker)" /><link rel="next" href="s-xen-drbd-mod-params.html" title="13.2. Setting DRBD module parameters for use with Xen" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 13. Using Xen with DRBD</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="s-ocfs2-legacy.html">Prev</a> </td><th width="60%" align="center">Part IV. DRBD-enabled applications</th><td width="20%" align="right"> <a accesskey="n" href="s-xen-drbd-mod-params.html">Next</a></td></tr></table><hr /></div><div class="chapter"><div class="titlepage"><div><div><h2 class="title"><a id="ch-xen"></a>Chapter 13. Using Xen with DRBD</h2></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="section"><a href="ch-xen.html#s-xen-primer">13.1. Xen primer</a></span></dt><dt><span class="section"><a href="s-xen-drbd-mod-params.html">13.2. Setting DRBD module parameters for use with Xen</a></span></dt><dt><span class="section"><a href="s-xen-create-resource.html">13.3. Creating a DRBD resource suitable to act as a Xen VBD</a></span></dt><dt><span class="section"><a href="s-xen-configure-domu.html">13.4. Using DRBD VBDs</a></span></dt><dt><span class="section"><a href="s-manage-domu.html">13.5. Starting, stopping, and migrating DRBD-backed domU’s</a></span></dt><dt><span class="section"><a href="s-xen-internal.html">13.6. Internals of DRBD/Xen integration</a></span></dt><dt><span class="section"><a href="s-xen-pacemaker.html">13.7. Integrating Xen with Pacemaker</a></span></dt></dl></div><p><a id="idp54078832" class="indexterm"></a>This chapter outlines the use of DRBD as a Virtual
Block Device (VBD) for virtualization environments using the Xen
hypervisor.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="s-xen-primer"></a>13.1. Xen primer</h2></div></div></div><p>Xen is a virtualization framework originally developed at the
University of Cambridge (UK), and later being maintained by XenSource,
Inc. (now a part of Citrix). It is included in reasonably recent
releases of most Linux distributions, such as Debian GNU/Linux (since
version 4.0), SUSE Linux Enterprise Server (since release 10), Red Hat
Enterprise Linux (since release 5), and many others.</p><p>Xen uses <a id="idp54082416" class="indexterm"></a>paravirtualization — a virtualization method
involving a high degree of cooperation between the virtualization host
and guest virtual machines — with selected guest operating systems for
improved performance in comparison to conventional virtualization
solutions (which are typically based on hardware
emulation). <a id="idp54084080" class="indexterm"></a>Xen also supports full hardware emulation
on CPUs that support the appropriate virtualization extensions, in Xen
parlance, this is known as HVM ( "hardware-assisted virtual machine").</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.png" /></td><th align="left">Note</th></tr><tr><td align="left" valign="top"><p>At the time of writing, CPU extensions supported by Xen for HVM
are Intel’s Virtualization Technology (VT, formerly codenamed
"Vanderpool"), and AMD’s Secure Virtual Machine (SVM, formerly known
as "Pacifica").</p></td></tr></table></div><p>Xen supports <a id="idp54086576" class="indexterm"></a><span class="emphasis"><em>live migration</em></span>, which refers to the
capability of transferring a running guest operating system from one
physical host to another, without interruption.</p><p>When a DRBD resource is used as a replicated Virtual Block Device
(VBD) for Xen, it serves to make the entire contents of a domU’s
virtual disk available on two servers, which can then be configured
for automatic fail-over. That way, DRBD does not only provide
redundancy for Linux servers (as in non-virtualized DRBD deployment
scenarios), but also for any other operating system that can be
virtualized under Xen — which, in essence, includes any operating
system available on 32- or 64-bit Intel compatible architectures.</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="s-ocfs2-legacy.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="p-apps.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="s-xen-drbd-mod-params.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">12.5. Legacy OCFS2 management (without Pacemaker) </td><td width="20%" align="center"><a accesskey="h" href="drbd-users-guide.html">Home</a></td><td width="40%" align="right" valign="top"> 13.2. Setting DRBD module parameters for use with Xen</td></tr></table></div></body></html>
|