From owner-freebsd-virtualization@FreeBSD.ORG Mon Feb 10 15:39:56 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B7E7A81E for ; Mon, 10 Feb 2014 15:39:56 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 7639D18DD for ; Mon, 10 Feb 2014 15:39:56 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTPS id 294BC11E4D; Tue, 11 Feb 2014 01:39:48 +1000 (EST) Received: from Peters-MacBook-Pro.local (c-69-181-164-196.hsd1.ca.comcast.net [69.181.164.196]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BRS30938 (AUTH peterg@ptree32.com.au); Tue, 11 Feb 2014 01:39:47 +1000 Message-ID: <52F8F2C1.9030505@freebsd.org> Date: Mon, 10 Feb 2014 07:39:45 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: Aryeh Friedman Subject: Re: are ahci-hd images the same as raw under bhyve References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 10 Feb 2014 15:39:56 -0000 Hi Aryeh, > When I was playing with bhyve-grub a while ago I noticed there seemed to be > little difference between ahci-hd and "raw" (if no format it given besides > just naming a md file). Is it safe to treat the two formats > interchangeably in bhyve (and bhyve-grub)? Can I do this to the point of > mixing and matching them on instances created with both (i.e. boot with > ahci on a raw image and vice versa)? Not quite sure what you mean here: ahci-hd is a device emulation (as are ahci-cd and virtio-blk). The backend for these is either a disk image on a filesystem or a block device. later, Peter.