Skip to content

Commit

Permalink
config: Build qcow2 images for eos base
Browse files Browse the repository at this point in the history
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
  • Loading branch information
dbnicholson committed Apr 24, 2024
1 parent 3635faf commit 245720c
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions config/product-personality/eos-base.ini
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 245720c

Please sign in to comment.