From owner-freebsd-virtualization@freebsd.org Mon Jan 22 16:01:12 2018 Return-Path: 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 14138EC7F97 for ; Mon, 22 Jan 2018 16:01:12 +0000 (UTC) (envelope-from jason@corrupted.io) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D3B91825D1 for ; Mon, 22 Jan 2018 16:01:11 +0000 (UTC) (envelope-from jason@corrupted.io) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 1EFB921007 for ; Mon, 22 Jan 2018 11:01:10 -0500 (EST) Received: from web4 ([10.202.2.214]) by compute6.internal (MEProxy); Mon, 22 Jan 2018 11:01:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=corrupted.io; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=m5fqSY1Gx+VJYtxA+5rbaB1BEe CD9Dx+pmRgv3L/9bU=; b=spS3jUVkkHBLhTmoKlOhx8RdWLNgS1qBldm5C2zPS0 H4hgbuktEFH+x/K5ntjM9ZRawCfo2rRLe7CAlnR++UWKllBMwbljKhN1OBALRnou 2Sg9ygcNuEYNcGCsAUlIl9+4h/0NMu/9urbupGfD7cK4luptHWsaZPpRWcEYF9SL U= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=m5fqSY 1Gx+VJYtxA+5rbaB1BEeCD9Dx+pmRgv3L/9bU=; b=ouJ6/LviHYw32cqwFg4BFx hX3z4CvmTyEMxNOYR4UPgc00kx/90oLirMeeZgSRbfm9RlejDzasJblyJFsoPp8j vIXcbD1fOyzJnLHLfBlp4K9LYJstjyItzY8oHz5Ibn+zkfZJmaasOCF4JIC0vW0w 1uugTIxk3Flo6Ulrf0r/NqJyGhOfau9u+3TLHce2lSXOBxrn0pF9HfMki8PL5cRO ZUYRJEZgpoZMxfWXgQ7VfXKfz/v7yRHfZOal4eBWsVrEed+y1M3/38iz4dRmr7rA UJN8mrE9dN+7VKYEpSbBWnBA0Zca/AVg1ZriGekOHf+ZTiYWLCjcg+0EjZ7rVS5A == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id F1138BA1AC; Mon, 22 Jan 2018 11:01:09 -0500 (EST) Message-Id: <1516636869.1772621.1243946728.02042214@webmail.messagingengine.com> From: Jason Barbier To: freebsd-virtualization@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-75de3051 In-Reply-To: Subject: Re: syncing bhyve instances References: Date: Mon, 22 Jan 2018 08:01:09 -0800 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2018 16:01:12 -0000 Assuming you wanted sync and not just a shared volume the guest/host running rsync to push/pull would work the best. But to be totally honest what I do right now to allow guests access to stuff on the host file system is just CIFS/SMB shares. It would probably be better to do NFS shares but I have a few windows guests that don't play nice with NFS. There is a bit of future work here though where someone could make some guest utils and stand up a file system bridge. There is some demand there and honestly it could be as simple as what virtualbox does where it provides a CIFS/SMB share through a local pipe. Whatever the solution is there I would lean more toward CIFS/SMB since it does have better cross-platform compatibility. --- Jason Barbier | E: jason@corrupted.io GPG: 0x40B8FA1D72EF0D89 (https://keybase.io/kusuriya) On Mon, Jan 22, 2018, at 7:45 AM, tech-lists wrote: > Hello lists, > > If I have two bhyve hosts, production [p] and reserve [r], and on both > there are identical guest[s] [1] and [2], what is the best way to sync > the guests? What's the best tool? > > 1. would syncing the guests from the host work? (in other words, running > some kind of tool like say rsync on the host work?). What about the > internal state of the guest? Could rsync account for changes in its > internal state? > > 2. or would it be better to run a tool like rsync inside each guest? > > 3. is there a better tool for this than rsync? > > thanks, > -- > J. > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization- > unsubscribe@freebsd.org"