From owner-freebsd-questions@freebsd.org Mon Jan 22 15:45:13 2018 Return-Path: Delivered-To: freebsd-questions@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 06DCDEC71E9; Mon, 22 Jan 2018 15:45:13 +0000 (UTC) (envelope-from tech-lists@zyxst.net) 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 CB4C480F37; Mon, 22 Jan 2018 15:45:12 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 1B21B20F9A; Mon, 22 Jan 2018 10:45:11 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Mon, 22 Jan 2018 10:45:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=++56bBjUYlYN2mdpdkK8MPpgxRZ1iRuq+sz+3b6guKw=; b=ILlFb59B 1XOQcT84RW3XrGref8swEiOZv7eK+VWVBlMq4WOjPGBJ6LpW0Os19k/VBjVQMfhU bx8x3so47y24C09yyQtyhNB2MJd1QReJDF2KeyXrOK160W/tzyCPo3FJv0lJ0ovC UZ+x5jnQ/45B8uLxHnTQE4SZ3xmUAH7gD49hSBOj62NJTvAsoLGogdfQ9MBW7igf dkST1IJAgwnn1mlZFYk4A5pZeyowRWgxxI3z6SY1FVYZ9ba0iRtgZWun9i4REvxA Xfeb63eQW+yvrH+oumFunysWP4uv4VYAgiwPHUP0JFdsbRmKcL67PXg/JsYJWtXh FXeqh6IG95TJhQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=++56bBjUYlYN2mdpdkK8MPpgxRZ1i Ruq+sz+3b6guKw=; b=H8aej3PGHq6yfdJvDH5HN03NU9RyKpn8XMgUOGykUpeSI 3x8mjwNXZqSXt9LN1aPUt8xjaHyVrO9xPhB3b0S6dAUbGy/0SWx7bQuz1/mJaf+s oBVttyKXtOAMpg1WbwgLEumjcThUu81voEvjaXTMTxgObAKyqwJ3cKWwyLRD97em 8+fP7cnoOMsyvzYoxTGs0MwxUlMCeeh1SwpvNGchyv/zycskCHxDu3sLdFiLrqsg xsTMuZvSSZBmY8VEVLe+R7Dsb8ymEVsxn9LLMmH2AQ/KUKw5kk34E1agmjjOJoZt rvV1+zwXb3If3UnEs4I0KD5r1Y3ATMFfJPC3VBp3w== X-ME-Sender: Received: from desktop.parsley.growveg.org (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 8AEB6247A9; Mon, 22 Jan 2018 10:45:10 -0500 (EST) To: freebsd-virtualization@freebsd.org From: tech-lists Subject: syncing bhyve instances Cc: freebsd-questions@freebsd.org Message-ID: Date: Mon, 22 Jan 2018 15:45:09 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2018 15:45:13 -0000 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.