--- Begin Message ---
Hi folks.
I tried this feature in the new Proxmox VE 8.4, I just can upload vmdk,
qcow2 and raw file.
Tried vhd and vdi and no luck.
And I can't use the uploaded file to import the image and create a new VM.
Is that supposed to be this way, at least for now?
Is there any further development to be done?
I suppose this is not a bug, right? But, instead, something to fully
implement in next upgrades.
Cheers.
---
Gilberto Nunes Ferreira
+55 (47) 99676-7530 - Whatsapp / Telegram
Em qua., 9 de abr. de 2025 às 04:10, Dominik Csapak <d.csa...@proxmox.com>
escreveu:
> On 4/8/25 17:34, Thomas Lamprecht wrote:
> > Am 08.04.25 um 14:13 schrieb Dominik Csapak:
> >> By enabling the import button for qcow2/vmdk/raw files, and showing a
> >> window with a VMID selector and the disk edit panel.
> >>
> > functionality wise I'd have applied that as it would be new and have thus
> > almost no regression potential, might be also better to factor out the
> > panel upfront in a dedicated commit and then integrate it everywhere.
> >
> > But lets wait this out, no point in rushing things here.
>
> Sure, don't rush this. Is there anything concrete you'd want to do have
> done differently
> here though?
>
> Even for the import storage content I'd really like to reuse the general
> disk edit panel
> (for e.g. the detection of which bus/controller is used, etc.), so the
> regression potential
> would be no different even if we'd only show it in the storage content.
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>
--- End Message ---
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
