public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Dominik Csapak <d.csapak@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 14:04:30 +0200	[thread overview]
Message-ID: <mailman.911.1744286711.359.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <mailman.909.1744285245.359.pve-devel@lists.proxmox.com>

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

From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.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 14:04:30 +0200
Message-ID: <3b00d216-959b-45f3-85cd-e06c571284ec@proxmox.com>

On 4/10/25 13:39, Gilberto Ferreira via pve-devel wrote:
> Hi folks.

Hi

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

Yes, we held off on applying the remaining UI patches for now since it was too close to
the release.

FYI, you can use the uploaded images via the api or cli already, no need to wait
for the gui patches, see my other docs patch (not yet applied) for details:
https://lore.proxmox.com/all/20250408142239.3527806-1-d.csapak@proxmox.com/

as for vhd,vdi not sure if we'll support that, it would require a bit more work
to support this (if you want you can open an enhancement request on our bugzilla,
best with examples where such images are offered)

> 
> Cheers.

Best regards
Dominik



[-- 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 12:05 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
2025-04-10 12:04         ` Dominik Csapak via pve-devel [this message]
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.911.1744286711.359.pve-devel@lists.proxmox.com \
    --to=pve-devel@lists.proxmox.com \
    --cc=d.csapak@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