From 1003142f07d5ca0c0565a13ef345e9910f751923 Mon Sep 17 00:00:00 2001 From: George Melikov Date: Wed, 21 Dec 2016 22:29:14 +0400 Subject: [PATCH] Fixed Xen Hypervisor header --- FAQ.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/FAQ.md b/FAQ.md index 09ed361..44a1c1b 100644 --- a/FAQ.md +++ b/FAQ.md @@ -20,7 +20,7 @@ - [Performance Considerations](#performance-considerations) - [Advanced Format Disks](#advanced-format-disks) - [Using a zvol for a swap device](#using-a-zvol-for-a-swap-device) - * [Using ZFS on Xen Hypervisor or Xen Dom0](#using-zfs-on-xen-hypervisor-or-xen-dom0) +- [Using ZFS on Xen Hypervisor or Xen Dom0](#using-zfs-on-xen-hypervisor-or-xen-dom0) - [Licensing](#licensing) - [Reporting a problem](#reporting-a-problem) @@ -317,7 +317,7 @@ $ zfs create -V 4G -b $(getconf PAGESIZE) \ -o com.sun:auto-snapshot=false rpool/swap ``` -### Using ZFS on Xen Hypervisor or Xen Dom0 +## Using ZFS on Xen Hypervisor or Xen Dom0 It is usually recommended to keep virtual machine storage and hypervisor pools, quite separate. Although few people have managed to successfully deploy and run ZFS on Linux using the same machine configured as Dom0. There are few caveats: