Summary: | Virtual Machine images don't work with VirtualBox [.qcow file format] | ||
---|---|---|---|
Product: | Documentation | Reporter: | Drew <drew> |
Component: | Website | Assignee: | freebsd-doc (Nobody) <doc> |
Status: | Closed Overcome By Events | ||
Severity: | Affects Many People | CC: | bcr, carlavilla |
Priority: | --- | ||
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any |
Description
Drew
2016-06-17 22:27:34 UTC
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 disk. After starting the VM I get: FATAL: Could not read from the boot medium! System halted. A quick search on the web revealed this: https://forums.virtualbox.org/viewtopic.php?f=1&t=75859 The issue seems to be with VirtualBox, not FreeBSD. To convert your qcow2 image 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. batch change: For bugs that match the following - Status Is In progress AND - Untouched since 2018-01-01. AND - Affects Base System OR Documentation DO: Reset to open status. Note: I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed. Now, the README[1] of the VM clarifies that the .qcow2 is for QEMU and KVM. [1] https://download.freebsd.org/ftp/releases/VM-IMAGES/README.txt |