/usr/share/doc/drbd-doc/users-guide/s-xen-configure-domu.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 29 30 | <?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.4. Using DRBD VBDs</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="ch-xen.html" title="Chapter 13. Using Xen with DRBD" /><link rel="prev" href="s-xen-create-resource.html" title="13.3. Creating a DRBD resource suitable to act as a Xen VBD" /><link rel="next" href="s-manage-domu.html" title="13.5. Starting, stopping, and migrating DRBD-backed domU’s" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">13.4. Using DRBD VBDs</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="s-xen-create-resource.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-manage-domu.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-configure-domu"></a>13.4. Using DRBD VBDs</h2></div></div></div><p>In order to use a DRBD resource as the virtual block device, you must
add a line like the following to your Xen domU configuration:
<a id="idp54101872" class="indexterm"></a></p><pre class="programlisting">disk = [ 'drbd:<resource>,xvda,w' ]</pre><p>This example configuration makes the DRBD resource named <span class="emphasis"><em>resource</em></span>
available to the domU as <code class="literal">/dev/xvda</code> in read/write mode ( <code class="literal">w</code>).</p><p>Of course, you may use multiple DRBD resources with a single domU. In
that case, simply add more entries like the one provided in the
example to the <code class="literal">disk</code> option, separated by commas.</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>There are three sets of circumstances under which you cannot use
this approach:</p></td></tr></table></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
You are configuring a fully virtualized (HVM) domU.
</li><li class="listitem">
You are installing your domU using a graphical installation utility,
<span class="emphasis"><em>and</em></span> that graphical installer does not support the <code class="literal">drbd:</code> syntax.
</li><li class="listitem"><p class="simpara">
You are configuring a domU without the <code class="literal">kernel</code>, <code class="literal">initrd</code>, and
<code class="literal">extra</code> options, relying instead on <code class="literal">bootloader</code> and
<code class="literal">bootloader_args</code> to use a Xen pseudo-bootloader, <span class="emphasis"><em>and</em></span> that
pseudo-bootloader does not support the <code class="literal">drbd:</code> syntax.
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem">
pygrub+ (prior to Xen 3.3) and <code class="literal">domUloader.py</code> (shipped with Xen on
SUSE Linux Enterprise Server 10) are two examples of
pseudo-bootloaders that do not support the <code class="literal">drbd:</code> virtual block device
configuration syntax.
</li><li class="listitem">
<code class="literal">pygrub</code> from Xen 3.3 forward, and the <code class="literal">domUloader.py</code> version that
ships with SLES 11 <span class="emphasis"><em>do</em></span> support this syntax.
</li></ul></div></li></ul></div><p>Under these circumstances, you must use the traditional <code class="literal">phy:</code> device
syntax and the DRBD device name that is associated with your resource,
not the resource name. That, however, requires that you manage DRBD
state transitions outside Xen, which is a less flexible approach than
that provided by the <code class="literal">drbd</code> resource type.</p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="s-xen-create-resource.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-manage-domu.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">13.3. Creating a DRBD resource suitable to act as a Xen VBD </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.5. Starting, stopping, and migrating DRBD-backed domU’s</td></tr></table></div></body></html>
|