> Am 21.06.2022 um 02:18 schrieb Kevin Fenzi <kevin@xxxxxxxxx>: > > ... > What format image is to be produced? qcow2? or raw.xz? or something > else? The current implementation creates compressed qcow2 file to make use of the dynamic capabilities. The default max disk size is 40 GB, the image size is 595 MB. The server documentation will describe how to adjust the properties (https://docs.stg.fedoraproject.org/en-US/fedora-server/virtualization-vm-install-diskimg-fedoraserver/, currently incomplete first draft) > I assume this will not be release blocking at least at first? Admittedly, not thought and not decided explicitly about it in WG. In the long run it should have the same status as the other three server distribution files (full install, net install, aarch64 SBC image). Virtualization is one of the core features. But, if we don’t get it built and booted problem-free during beta, we would postpone it anyway (the current kickstart file builds fine in a local ImageFactory environment, https://pboy.fedorapeople.org) -- Peter Boy https://fedoraproject.org/wiki/User:Pboy pboy@xxxxxxxxxxxxxxxxx Timezone: CET (UTC+1) / CEST (UTC+2) Fedora Server Edition Working Group member Fedora docs team contributor Java developer and enthusiast _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
