/usr/share/doc/drbd-doc/users-guide/s-xen-internal.html is in drbd-doc 8.4~20151102-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 | <?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>13.6. Internals of DRBD/Xen integration</title><link rel="stylesheet" type="text/css" href="default.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.79.1" /><link rel="home" href="drbd-users-guide.html" title="The DRBD User’s Guide" /><link rel="up" href="ch-xen.html" title="Chapter 13. Using Xen with DRBD" /><link rel="prev" href="s-manage-domu.html" title="13.5. Starting, stopping, and migrating DRBD-backed domU’s" /><link rel="next" href="s-xen-pacemaker.html" title="13.7. Integrating Xen with Pacemaker" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">13.6. Internals of DRBD/Xen integration</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="s-manage-domu.html">Prev</a> </td><th width="60%" align="center">Chapter 13. Using Xen with DRBD</th><td width="20%" align="right"> <a accesskey="n" href="s-xen-pacemaker.html">Next</a></td></tr></table><hr /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="s-xen-internal"></a>13.6. Internals of DRBD/Xen integration</h2></div></div></div><p>Xen supports two Virtual Block Device types natively:</p><p><strong><code class="literal">phy</code>. </strong>This device type is used to hand "physical" block devices, available
in the host environment, off to a guest domU in an essentially
transparent fashion.</p><p><strong><code class="literal">file</code>. </strong>This device type is used to make file-based block device images
available to the guest domU. It works by creating a loop block device
from the original image file, and then handing that block device off
to the domU in much the same fashion as the <code class="literal">phy</code> device type does.</p><p>If a Virtual Block Device configured in the <code class="literal">disk</code> option of a domU
configuration uses any prefix other than <code class="literal">phy:</code>, <code class="literal">file:</code>, or no prefix
at all (in which case Xen defaults to using the <code class="literal">phy</code> device type),
Xen expects to find a helper script named <code class="literal">block</code>-<span class="emphasis"><em>prefix</em></span> in the Xen
scripts directory, commonly <code class="literal">/etc/xen/scripts</code>.</p><p>The DRBD distribution provides such a script for the <code class="literal">drbd</code> device
type, named <code class="literal">/etc/xen/scripts/block-drbd</code>. This script handles the
necessary DRBD resource state transitions as described earlier in this
chapter.</p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="s-manage-domu.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch-xen.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="s-xen-pacemaker.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">13.5. Starting, stopping, and migrating DRBD-backed domU’s </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.7. Integrating Xen with Pacemaker</td></tr></table></div></body></html>
|