From owner-freebsd-virtualization@FreeBSD.ORG Fri Jan 3 14:09:30 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C9E4DE31 for ; Fri, 3 Jan 2014 14:09:30 +0000 (UTC) Received: from mail-vb0-f41.google.com (mail-vb0-f41.google.com [209.85.212.41]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8301C100E for ; Fri, 3 Jan 2014 14:09:30 +0000 (UTC) Received: by mail-vb0-f41.google.com with SMTP id p14so7811904vbm.0 for ; Fri, 03 Jan 2014 06:09:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=M3GTd4Sj7TN/sphg6Ka4vrri7CR8hFhmept5LIwXHuk=; b=buoEuQXCDxl2umqUDnTjSh3ZLpmAga+d+MLOzvub5+Dgw/nFf5p9TvmmiPu27uMG95 2lAK3H0tG1wH+z6lVM1SPVqdUz1YvFAF9nsLPtnfO6s8DnfBcq/rjPfWlNoaUZTs1Mbj mmlnSsphn4qzmoaqzM2bPDmYtKmd6ZoVBYtXxFFfDuehkoUrpYe3jI5tIp3DSIY3CYww cVi5GQX8cfEeFhCSLK/tk8c7Lj3yOFK2bEXubOoEkTTi1jtfVKs7ICuHyvHFTV/CK6n7 eYeWnumj9mEnndBkbvOE6bXB/e2Cvhm5vAjk3bR8C/DCe3zE3GEeoAMK6LsAU4lj+5Yw Qvfw== X-Gm-Message-State: ALoCoQnbhIJPcGU95jMm/wMFCsQE7gMc2AuQKenCO2/lhJmMO7F/J40N4ibhBYUNuVw+hUUdefuX MIME-Version: 1.0 X-Received: by 10.52.164.203 with SMTP id ys11mr460545vdb.37.1388737793011; Fri, 03 Jan 2014 00:29:53 -0800 (PST) Received: by 10.52.245.67 with HTTP; Fri, 3 Jan 2014 00:29:52 -0800 (PST) X-Originating-IP: [2001:470:28:12b::3] In-Reply-To: <52C5CC18.90105@mail.lifanov.com> References: <52C5CC18.90105@mail.lifanov.com> Date: Fri, 3 Jan 2014 09:29:52 +0100 Message-ID: Subject: Re: Real Device with BHyve From: Andrea Brancatelli To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 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: Fri, 03 Jan 2014 14:09:30 -0000 Forgive me, but I can't understand what you mean. Are we talking of using something like /dev/cciss (just to say...) instead of /dev/da2 as the device shared with the VM? Won't the VM and the real system clash in using the same device? On Thu, Jan 2, 2014 at 9:29 PM, Nikolai Lifanov w= rote: > On 01/02/14 15:22, freebsd-virtualization-request@freebsd.org wrote: > > Hello everybody. > > > > I'm doing some experiments with bhyve on 10.0-RC3 and I got stuck at a > > certain point. > > > > I was trying to have a VM use a direct device (/dev/da2) instead of a > disk > > image. I was trying it in order to understand if there was any real > > performance difference between using a raw drive or an image-disk on th= e > > same drive. > > > > 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 siz= e > > 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=3D16 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.... > > > > What I was thinking of, for example, was of having an external iSCSI > device > > connected on the hostmachine mapped as a virtual disk for a specific VM= , > in > > order to speed the VM disk performances. > > > > > > Just another quick question... I have seen some improvements by having > the > > VM's virtual disk on ZFS against UFS. Is it just me or is there any rea= l > > improvement by using ZFS? > > > > Thanks a lot. > > > > > > -- *Andrea BrancatelliSchema 31 S.r.l. - Socio UnicoResponsabile ITROMA > > - FIRENZE - PALERMO ITALYTel: +39. 06.98.358.472* *Cell: +39 > > 331.2488468Fax: +39. 055.71.880.466Societ? del Gruppo SC31 ITALIA* > > I'm not answering your question precisely, but can you pass through the > disk controller to the virtual machine instead? I also know that zvol > and iscsi backends work, at least the last time I checked. > > - Nikolai Lifanov > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" > --=20 *Andrea BrancatelliSchema 31 S.r.l. - Socio UnicoResponsabile ITROMA - FIRENZE - PALERMO ITALYTel: +39. 06.98.358.472* *Cell: +39 331.2488468Fax: +39. 055.71.880.466Societ=C3=A0 del Gruppo SC31 ITALIA*