[pve-devel] [PATCH docs 2/3] cloud init: use expected disk number in example

Starting from a storage with no disks for the VM ID in question, the imported disk will be called vm-9000-disk-0. Signed-off-by: Fiona Ebner --- qm-cloud-init.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/qm-cloud-init.adoc b/qm-cloud-init.adoc index 25cd700..618d0f7 1

[pve-devel] [PATCH docs 1/3] cloud init: use 'order' variant for 'boot' property

instead of the legacy 'boot: c'+bootdisk combination. Signed-off-by: Fiona Ebner --- qm-cloud-init.adoc | 9 - 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/qm-cloud-init.adoc b/qm-cloud-init.adoc index 8363f10..25cd700 100644 --- a/qm-cloud-init.adoc +++ b/qm-cloud-init.

[pve-devel] [PATCH/RFC docs 3/3] cloud init: use 'import-from' disk syntax to avoid a step

Put the 'scsihw' part into the previous command, so that the rather complicated import command can stand on its own. Signed-off-by: Fiona Ebner --- Not entirely sure about this one, because it does make the commands a bit more involved. qm-cloud-init.adoc | 11 --- 1 file changed, 4 in

Re: [pve-devel] [PATCH V5 pve-manager 1/2] fix #2822: add iscsi, lvm, lvmthin & zfs storage for all cluster nodes

thanks for the resend, i can now apply it ;) i played a bit around with this and i'm not completely happy with the ux here. having 'localhost' as text in the box is not really helpful because the user might not actually know what 'localhost' actuall is. also it's possible to empty the field, of

[pve-devel] applied: [PATCH http-server v2 2/7] acknowledge content-disposition header

Am 07/09/2022 um 10:56 schrieb Daniel Tschlatscher: > Acknowledging the Content-Disposition header makes it possible for the > backend to tell the browser whether a file should be downloaded, > rather than displayed inline, and what it's default name should be. > > Signed-off-by: Daniel Tschlatsch

[pve-devel] applied: [PATCH v6 storage 1/1] (remote) export: check and untaint format

Am 28/09/2022 um 14:50 schrieb Fabian Grünbichler: > this format comes from the remote cluster, so it might not be supported > on the source side - checking whether it's known (as additional > safeguard) and untainting (to avoid open3 failure) is required. > > Signed-off-by: Fabian Grünbichler >

[pve-devel] [PATCH qemu-server 2/2] reuse existing cloud-init disks

When a disk exists but is not referenced in the config, it will be reused instead of dying during the attempt to allocate the disk. Signed-off-by: Mira Limbeck --- This patch is not required to fix the rollback code, but might be nice to have in addition since there will still be some users with

[pve-devel] [PATCH qemu-server 1/2] fix #4201: delete cloud-init disk on rollback

If the config doesn't contain the cloud-init disk anymore after the rollback, we have to clean it up since otherwise no further disk can be attached unless the one still existing on the storage is deleted. Signed-off-by: Mira Limbeck --- PVE/QemuConfig.pm | 34 ++

[pve-devel] applied: [PATCH v2 http-server 1/2] AnyEvent: whitespace fix

Am 13/05/2022 um 15:48 schrieb Matthias Heiserer: > and remove unnecessary parentheses. > > Signed-off-by: Matthias Heiserer > --- > > Changes from v1: > new patch > > src/PVE/APIServer/AnyEvent.pm | 3 +-- > 1 file changed, 1 insertion(+), 2 deletions(-) > > applied, thanks! _

[pve-devel] applied: [PATCH v2 http-server 2/2] AnyEvent: Fix #3990 - make small files uploadable

Am 13/05/2022 um 15:49 schrieb Matthias Heiserer: > == The problem > Upload of files smaller than ~16kb failed. > This was because the code assumed that it would be called > several times, and each time would do a certain action. > When the whole file was in the buffer, this failed because > the fu