From owner-freebsd-stable@freebsd.org Sat Jan 26 15:39:53 2019 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BCA3114C6930; Sat, 26 Jan 2019 15:39:53 +0000 (UTC) (envelope-from paul@redbarn.org) Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (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 4C50487E07; Sat, 26 Jan 2019 15:39:53 +0000 (UTC) (envelope-from paul@redbarn.org) Received: from [192.168.0.58] (cpc130782-camd17-2-0-cust84.know.cable.virginm.net [82.37.104.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id A9370892C6; Sat, 26 Jan 2019 15:39:42 +0000 (UTC) Subject: Re: freebsd-12 and bhyve and the azure platform To: freebsd-virtualization@freebsd.org, freebsd-stable@freebsd.org References: <20190126151701.GA87737@rpi3.zyxst.net> From: Paul Vixie Message-ID: <920a79f6-f7ea-fe2b-16cb-cde2a8112721@redbarn.org> Date: Sat, 26 Jan 2019 16:39:39 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 PostboxApp/6.1.9 MIME-Version: 1.0 In-Reply-To: <20190126151701.GA87737@rpi3.zyxst.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jan 2019 15:39:53 -0000 tech-lists wrote on 2019-01-26 16:17: > Is it possible to migrate a byve freebsd instance/image to Azure? Or > does one have to have the instance initially provisioned via their > marketplace? bhyve does not participate in the virtualbox/vmware/etc ecosystem where "appliances" in the form of "open virtualization format" files can be exported and imported. this in turn means that you would have to manually control the parameters of an azure instance to be sure that it can contain your existing system image. i would expect you to use dump | restore, or zfs dump | zfs restore, to move a system image from one container strategy (or bare metal) to another (such as azure), after first booting a rescue image inside the destination container. you'd then fine-tune your /etc/rc.conf file to have whatever settings were appropriate for the new container. i know that's somewhat old school, but, that's one reason to love bhyve. -- P Vixie