From owner-freebsd-virtualization@FreeBSD.ORG  Fri Jan  3 19:44:15 2014
Return-Path: <owner-freebsd-virtualization@FreeBSD.ORG>
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 9487AC7F
 for <freebsd-virtualization@freebsd.org>; Fri,  3 Jan 2014 19:44:15 +0000 (UTC)
Received: from mail.grem.de (outcast.grem.de [213.239.217.27])
 by mx1.freebsd.org (Postfix) with SMTP id F27F01D9B
 for <freebsd-virtualization@freebsd.org>; Fri,  3 Jan 2014 19:44:14 +0000 (UTC)
Received: (qmail 57110 invoked by uid 89); 3 Jan 2014 19:44:12 -0000
Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@88.217.181.106)
 by mail.grem.de with ESMTPA; 3 Jan 2014 19:44:12 -0000
Date: Fri, 3 Jan 2014 20:44:11 +0100
From: Michael Gmelin <freebsd@grem.de>
To: Peter Grehan <grehan@freebsd.org>
Subject: Re: Real Device with BHyve
Message-ID: <20140103204411.755021bb@bsd64.grem.de>
In-Reply-To: <52C6F6BC.6070108@freebsd.org>
References: <CADfWLen8WsBHU51+8vU_71js3-DCFa13DTakbDLoWRmhAu6XHw@mail.gmail.com>
 <52C6F6BC.6070108@freebsd.org>
X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.18; amd64-portbld-freebsd9.1)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
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."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 19:44:15 -0000



On Fri, 03 Jan 2014 09:43:24 -0800
Peter Grehan <grehan@freebsd.org> wrote:

> Hi Andrea,
> > Well, the machine starts ok but when the "child" FreeBSD starts
> > installation something strange happens. When I get to the
> > partitioning screen I can see the device avaiable as /dev/vtdb0
> > with the correct size and such. I choose autopartitioning, the
> > installer writes the partition table but when it start to
> > write /dev/vtdb0p2 a very cryptic error appears about being unable
> > to write - sorry, did not write it down.
> >
> > The installer then stops.
> >
> > If I do a fdisk /dev/vtdb0 in the VM I can see the GPT partition
> > being there. If I do a fdisk /dev/da2 on the host machine, I can
> > see the GPT partition as well, but the VM just doesn't want to
> > write on it.
> >
> > I even tried changing kern.geom.debugflags=16 as I thought the host
> > machine could be locking somehow the drive, but that didn't seem to
> > make any difference. I know it was a lame check but I was out of
> > ideas.
> >
> > So I just wanted to understand if such a scenario is supposed to be
> > supported....
> 
>   It is. Been a while since I've done this but will try a repro.
> Other folk have supported success using zvols so I'd assumed it was
> working.

If it helps, I had the same problem using zvol as well (booting the
installer and install on the "raw" device) on 10-CURRENT from mid 2013.

I didn't try with a more recent release. I ended up installing FreeBSD
from the outside (create partitions and untar base.txz, kernel.txz etc.
- afaik the same thing the Dexter's vm0 script does now) and could then
boot into it just fine.

-- 
Michael Gmelin