public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Gilberto Ferreira via pve-devel <pve-devel@lists.proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Gilberto Ferreira <gilberto.nunes32@gmail.com>,
	Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager v7 3/3] ui: import storage content: allow importing of vm disk images
Date: Thu, 10 Apr 2025 08:39:58 -0300	[thread overview]
Message-ID: <mailman.909.1744285245.359.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <22a457f5-12ce-48f3-9dfa-d4ae90715670@proxmox.com>

[-- Attachment #1: Type: message/rfc822, Size: 7077 bytes --]

From: Gilberto Ferreira <gilberto.nunes32@gmail.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager v7 3/3] ui: import storage content: allow importing of vm disk images
Date: Thu, 10 Apr 2025 08:39:58 -0300
Message-ID: <CAOKSTBsFSWxePJzuVY2UvWioNdrDOOHXyhjmAVBTYN9HtjbfAQ@mail.gmail.com>

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.csapak@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
>
>

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

  reply	other threads:[~2025-04-10 11:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 12:13 [pve-devel] [PATCH manager v7 0/3] allow importing vm disk images on the UI Dominik Csapak
2025-04-08 12:13 ` [pve-devel] [PATCH manager v7 1/3] ui: qemu hd edit: allow importing a disk from the import storage Dominik Csapak
2025-04-08 12:13 ` [pve-devel] [PATCH manager v7 2/3] ui: vm create wizard: allow importing disks Dominik Csapak
2025-04-08 12:13 ` [pve-devel] [PATCH manager v7 3/3] ui: import storage content: allow importing of vm disk images Dominik Csapak
2025-04-08 15:34   ` Thomas Lamprecht
2025-04-09  7:10     ` Dominik Csapak
2025-04-10 11:39       ` Gilberto Ferreira via pve-devel [this message]
2025-04-10 12:04         ` Dominik Csapak via pve-devel
2025-04-10 12:13           ` Gilberto Ferreira via pve-devel
2025-04-10 12:25           ` Gilberto Ferreira via pve-devel
2025-04-08 15:44 ` [pve-devel] [PATCH manager v7 0/3] allow importing vm disk images on the UI Michael Köppl
2025-04-10 12:04 ` Lukas Wagner via pve-devel
     [not found] ` <c7b3dfb5-89aa-4f42-927d-08475d17e7f0@proxmox.com>
2025-04-10 12:06   ` Dominik Csapak via pve-devel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=mailman.909.1744285245.359.pve-devel@lists.proxmox.com \
    --to=pve-devel@lists.proxmox.com \
    --cc=gilberto.nunes32@gmail.com \
    --cc=t.lamprecht@proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal