On 3/26/25 11:37, Fiona Ebner wrote:
Am 25.03.25 um 16:14 schrieb Dominik Csapak:
most of the building blocks are already there:
* we can have qcow2 files in an import storage
* we can import qcow2 files via the api from such a storage
this series fills in the missing bits & pieces:
* allow uploading qcow2 files into an import storage via the webgui
* adding the possibility to select such a file when creating a vm/disk
We could maybe also allow this for raw/vmdk if we want to, but IMHO
we can start out with qcow2 and add the others as necssary.
(if wanted, I can of course also add the others in a next version or as
a follow up)
Yes, please! It would be nice to have all three at the same time. Or is
there any specific reason why you limit it to qcow2? Otherwise, users
will just ask why support for these is missing right away.
No specific reason, it was just easier/quicker to implement one first. When we
also allow raw files,
should we also allow other extensions than '.raw'? not sure if there is one that
is often used (since I think '.raw' is more a PVE thing)
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel