Date: Sun, 18 Jan 2026 20:16:47 +0000 From: Graham Perrin <grahamperrin@gmail.com> To: FreeBSD-CURRENT <freebsd-current@freebsd.org> Subject: FreeBSD-16.0-CURRENT-arm64-aarch64-zfs qcow in QEMU Message-ID: <53a41c7b-348a-4939-b803-f11251c7a889@gmail.com> In-Reply-To: <20260113032109.AD5CE7F84@freefall.freebsd.org>
index | next in thread | previous in thread | raw e-mail
New FreeBSD snapshots available: main (20260113 2b60e628d3b1) <https://lists.freebsd.org/archives/freebsd-snapshots/2026-January/000696.html>; On 13/01/2026 03:21, Colin Percival wrote: > … > > === Virtual Machine Disk Images === > > … FreeBSD-16.0-CURRENT-arm64-aarch64-zfs-20260113-2b60e628d3b1-283055.qcow I can not boot from this file in QEMU. <https://media.bsd.cafe/bsdmmedia01/media_attachments/files/115/911/456/995/267/785/original/c65131d5f2656d30.png>; pictures the symptom. On one hand: this may be lack of education. My first use of Virtual Machine Manager was only a few hours ago. <https://www.reddit.com/r/qemu_kvm/comments/1qg94mf/virtmanager_on_linux_how_to_use_edk2aarch64codefd/>; seeks advice. On the other hand: in a separate VM, I _can_ boot 16.0-CURRENT following a pkgbase major upgrade from 14.3.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53a41c7b-348a-4939-b803-f11251c7a889>