From owner-freebsd-doc@freebsd.org  Sat Jun 18 11:08:02 2016
Return-Path: <owner-freebsd-doc@freebsd.org>
Delivered-To: freebsd-doc@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 489CBA7874A
 for <freebsd-doc@mailman.ysv.freebsd.org>;
 Sat, 18 Jun 2016 11:08:02 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (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 385431364
 for <freebsd-doc@FreeBSD.org>; Sat, 18 Jun 2016 11:08:02 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u5IB82Ae079050
 for <freebsd-doc@FreeBSD.org>; Sat, 18 Jun 2016 11:08:02 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-doc@FreeBSD.org
Subject: [Bug 210361] Virtual Machine images don't work with VirtualBox
 [.qcow file format]
Date: Sat, 18 Jun 2016 11:08:02 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Documentation
X-Bugzilla-Component: Website
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: bcr@FreeBSD.org
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-doc@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_status cc
Message-ID: <bug-210361-9-NDiN1lfAoT@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-210361-9@https.bugs.freebsd.org/bugzilla/>
References: <bug-210361-9@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Documentation project <freebsd-doc.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-doc>,
 <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/>
List-Post: <mailto:freebsd-doc@freebsd.org>
List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-doc>,
 <mailto:freebsd-doc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jun 2016 11:08:02 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210361

Benedict Reuschling <bcr@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |In Progress
                 CC|                            |bcr@FreeBSD.org

--- Comment #1 from Benedict Reuschling <bcr@FreeBSD.org> ---
I just verified it. Downloaded the qcow2 10.3. image, extracted it from the=
 xz
and created a new VirtualBox VM using that qcow2 file as the underlying dis=
k.
After starting the VM I get: FATAL: Could not read from the boot medium! Sy=
stem
halted.=20

A quick search on the web revealed this:=20
https://forums.virtualbox.org/viewtopic.php?f=3D1&t=3D75859

The issue seems to be with VirtualBox, not FreeBSD. To convert your qcow2 i=
mage
to VDI, which you can then import as a new VM in VirtualBox, open a console=
 and
enter this:

VBoxManage convertfromraw --format vdi
/path/to/FreeBSD-10.3-RELEASE-amd64.qcow2
/output/path/FreeBSD-10.3-RELEASE-amd64.vdi

We should think about providing VDI (or any other format) files instead of =
QCOW
until VirtualBox fully supports running that format.

--=20
You are receiving this mail because:
You are the assignee for the bug.=