Date: Sat, 18 Jun 2016 11:08:02 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-doc@FreeBSD.org Subject: [Bug 210361] Virtual Machine images don't work with VirtualBox [.qcow file format] 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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-210361-9-NDiN1lfAoT>