From 245720cbe26b17531bfa512fb06d70f63c214371 Mon Sep 17 00:00:00 2001 From: Dan Nicholson Date: Sat, 20 Apr 2024 09:36:06 -0600 Subject: [PATCH] config: Build qcow2 images for eos base In my ideal world, we'd do this for all eos products and add them to osinfo-db. That way we could streamline the GNOME Boxes experience where it's just going to write all the data from the ISO to a qcow2 image anyways. However, doing this for the bigger personalities would add a lot of overhead. We'd really want to choose one of OVF or qcow2 as "the VM image" since doing both would be painful. For now, punt on that question and just enable it for the small base image where it can essentially be a power user tool. https://phabricator.endlessm.com/T35332 --- config/product-personality/eos-base.ini | 3 +++ 1 file changed, 3 insertions(+) diff --git a/config/product-personality/eos-base.ini b/config/product-personality/eos-base.ini index a340d958..1c1c5f82 100644 --- a/config/product-personality/eos-base.ini +++ b/config/product-personality/eos-base.ini @@ -11,6 +11,9 @@ compression = xz # This setting only works for arch=amd64, for all other values this is a no-op vm_image = true +# Build QEMU qcow2 image +qcow2 = true + [iso] # The capacity of a single-later DVD+R, which is the smallest # commonly-available writeable format according to