From: "Michael Köppl" <m.koeppl@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager v7 0/3] allow importing vm disk images on the UI
Date: Tue, 8 Apr 2025 17:44:16 +0200 [thread overview]
Message-ID: <fb4b0741-b110-45c1-8298-95e6ad436012@proxmox.com> (raw)
In-Reply-To: <20250408121312.312526-1-d.csapak@proxmox.com>
On 4/8/25 14:13, Dominik Csapak wrote:
> this is a continuation of my previous series [0]
>
> It enables importing disks on the UI in the HardwareView of a vm,
> in the create wizard, and in the storage content view.
>
> I split the patches so that the wizard and storage content view one are
> separate, so they can be reviewed independently.
>
> changes from v6:
> * drop applied patches
> * make import in hd edit panel dependant on configuration, instead of
> showing a checkbox
> * wizard and HardwareView got an explicit import button
> * make the import button work on the storage content view for disk
> images
> * split patches for hdedit, wizard and storage content
>
> 0: https://lore.proxmox.com/pve-devel/20250407101310.3196974-1-d.csapak@proxmox.com/
Hi,
tested this by creating disk images from existing VMs and importing them
in the following ways:
- during creation of a VM in the CreateWizard
- through the Hardware view of an existing VM, then changing the boot
order to boot from the imported disk
- from the storage content view; uploaded a disk image and imported into
an existing VM from there
- imported with IDE, SATA, SCSI, and VirtIO controllers
- imported qcow2, vmdk, and raw disk images
The tested cases worked as I would expect and I was able to create and
start VMs with the given images. Creating multiple new VMs with imported
disks in parallel did slow down the creation considerably, but otherwise
worked without problems for me. I also tried adding, removing, changing
disks in the CreateWizard to see if I could get around the constraints
set for the new selectors. The UI part was overall intuitive to use.
I pondered a bit on the icon chosen for the import, but would could not
really find a more fitting one. Maybe someone else has a stronger
opinion on this?
So please consider this:
Reviewed-by: Michael Köppl <m.koeppl@proxmox.com>
Tested-by: Michael Köppl <m.koeppl@proxmox.com>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-04-08 15:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 12:13 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
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 ` Michael Köppl [this message]
2025-04-10 12:04 ` [pve-devel] [PATCH manager v7 0/3] allow importing vm disk images on the UI 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=fb4b0741-b110-45c1-8298-95e6ad436012@proxmox.com \
--to=m.koeppl@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pve-devel@lists.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