Date: Sun, 18 Jan 2026 20:30:08 +0000 From: Colin Percival <cperciva@tarsnap.com> To: Graham Perrin <grahamperrin@gmail.com>, FreeBSD-CURRENT <freebsd-current@freebsd.org> Subject: Re: FreeBSD-16.0-CURRENT-arm64-aarch64-zfs qcow in QEMU Message-ID: <0100019bd2ccfdea-5246b911-2304-42ad-a249-a7a44505ef57-000000@email.amazonses.com> In-Reply-To: <53a41c7b-348a-4939-b803-f11251c7a889@gmail.com> References: <20260113032109.AD5CE7F84@freefall.freebsd.org> <53a41c7b-348a-4939-b803-f11251c7a889@gmail.com>
index | next in thread | previous in thread | raw e-mail
On 1/18/26 12:16, Graham Perrin wrote: > 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. Yeah, we had some weird breakage on the VM builds last week. At first I thought it was just cloudware but it turned out to be VM images as well. On my to-do list... -- Colin Percival FreeBSD Release Engineering Lead & EC2 platform maintainer Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoidhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0100019bd2ccfdea-5246b911-2304-42ad-a249-a7a44505ef57-000000>