From 05d1dd6b336d7d5eab84a148856b99afd0d3ea1e Mon Sep 17 00:00:00 2001 From: Roman Bogorodskiy Date: Sun, 14 Sep 2014 09:17:54 +0400 Subject: [PATCH] docs: update zfs documentation - docs/formatstorage.html.in: document 'zfs' pool type, add it to a list of pool types that could use source physical devices - docs/storage.html.in: update a ZFS pool example XML with source physical devices, mention that starting from 1.2.9 a pool could be created from this devices by libvirt and in earlier versions user still has to create a pool manually - docs/drvbhyve.html.in: add an example with ZFS pools --- docs/drvbhyve.html.in | 16 ++++++++++++++++ docs/formatstorage.html.in | 7 ++++--- docs/storage.html.in | 18 ++++++++++++------ 3 files changed, 32 insertions(+), 9 deletions(-) diff --git a/docs/drvbhyve.html.in b/docs/drvbhyve.html.in index 71e3bc4a88..39afdf51b3 100644 --- a/docs/drvbhyve.html.in +++ b/docs/drvbhyve.html.in @@ -141,5 +141,21 @@ tweak them.

/usr/sbin/bhyve -c 2 -m 214 -A -I -H -P -s 0:0,hostbridge -s 3:0,virtio-net,tap0,mac=52:54:00:5d:74:e3 -s 2:0,virtio-blk,/home/user/vm1.img -s 1,lpc -l com1,/dev/nmdm0A vm1 +

Using ZFS volumes

+ +

It's possible to use ZFS volumes as disk devices since 1.2.8. +An example of domain XML device entry for that will look like:

+ +
+  ...
+  <disk type='volume' device='disk'>
+    <source pool='zfspool' volume='vol1'/>
+    <target dev='vdb' bus='virtio'/>
+  </disk>
+  ...
+ +

Please refer to the Storage documentation for more details on storage +management.

+ diff --git a/docs/formatstorage.html.in b/docs/formatstorage.html.in index e25bba70f9..d3e6f05c2b 100644 --- a/docs/formatstorage.html.in +++ b/docs/formatstorage.html.in @@ -23,8 +23,9 @@ (since 0.7.1), rbd (since 0.9.13), sheepdog (since 0.10.0), - or gluster (since - 1.2.0). This corresponds to the + gluster (since + 1.2.0) or zfs (since + 1.2.8). This corresponds to the storage backend drivers listed further along in this document.

General metadata

@@ -115,7 +116,7 @@
device
Provides the source for pools backed by physical devices (pool types fs, logical, disk, - iscsi). + iscsi, zfs). May be repeated multiple times depending on backend driver. Contains a single attribute path which is the fully qualified path to the block device node. Since 0.4.1
diff --git a/docs/storage.html.in b/docs/storage.html.in index 5db79c7ae4..3d2ffcaafb 100644 --- a/docs/storage.html.in +++ b/docs/storage.html.in @@ -750,22 +750,28 @@

This provides a pool based on the ZFS filesystem. It is currently supported on FreeBSD only. +

- A pool has to be created before libvirt could start using it. That - could be done using zpool create command. Please refer to - the ZFS documentation for details on a pool creation. - - Since 1.2.8 +

A pool could either be created manually using the zpool create + command and its name specified in the source section or + since 1.2.9 source devices could be specified to create a pool using + libvirt.

+

Please refer to the ZFS documentation for details on a pool creation.

+ +

Since 1.2.8

. +

Example pool input

       <pool type="zfs">
         <name>myzfspool</name>
         <source>
           <name>zpoolname</name>
+          <device path="/dev/ada1"/>
+          <device path="/dev/ada2"/>
         </source>
-       </pool>
+ </pool>

Valid pool format types

-- GitLab