From owner-freebsd-virtualization@freebsd.org  Tue Dec  5 15:37:14 2017
Return-Path: <owner-freebsd-virtualization@freebsd.org>
Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 506B9E6DE8D
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Tue,  5 Dec 2017 15:37:14 +0000 (UTC)
 (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net)
Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 256617F45E
 for <freebsd-virtualization@freebsd.org>; Tue,  5 Dec 2017 15:37:13 +0000 (UTC)
 (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net)
Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1])
 by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id vB5Fb17T052053;
 Tue, 5 Dec 2017 07:37:01 -0800 (PST)
 (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net)
Received: (from freebsd-rwg@localhost)
 by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id vB5Fb1dv052052;
 Tue, 5 Dec 2017 07:37:01 -0800 (PST) (envelope-from freebsd-rwg)
From: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net>
Message-Id: <201712051537.vB5Fb1dv052052@pdx.rh.CN85.dnsmgr.net>
Subject: Re: Storage overhead on zvols
In-Reply-To: <32BA4687-AB70-4370-A9BA-EF4F66BF69A6@ebureau.com>
To: Dustin Wenz <dustinwenz@ebureau.com>
Date: Tue, 5 Dec 2017 07:37:01 -0800 (PST)
CC: Paul Vixie <paul@redbarn.org>,
 FreeBSD virtualization <freebsd-virtualization@freebsd.org>
X-Mailer: ELM [version 2.4ME+ PL121h (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Dec 2017 15:37:14 -0000

> I'm not using ZFS in my VMs for data integrity (the host already provides that); it's mainly for the easy creation and management of filesystems, and the ability to do snapshots for rollback and replication. Some of my deployments have hundreds of filesystems in an organized hierarchy, with delegated permissions and automated snapshots, send/recvs, and clones for various operations.

I architect things in such a way that I have 1 VM used as a NAS that
runs zfs and allows all that nice functionality then all the other
VM's run with ufs + nfs mounts.  And can actually run a VM with
no local disk over iPxe netbooting.

I find this very flexible and minimally impacting.  Though it
does make a single point of failure, that could be cured with
some redundancy.

-- 
Rod Grimes                                                 rgrimes@freebsd.org