From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH stable-7 guest-common] storage tunnel: correctly set disk-import parameters
Date: Wed, 5 Mar 2025 12:12:46 +0100 [thread overview]
Message-ID: <a3aa464a-69b7-4a81-b621-09901ebe5f16@proxmox.com> (raw)
In-Reply-To: <abcc5dde-9341-4128-abca-8d4e69daa526@proxmox.com>
Am 05.03.25 um 10:46 schrieb Fiona Ebner:
> Am 04.03.25 um 19:09 schrieb Thomas Lamprecht:
>> Not a huge fan, but it would be fine for me as long as they are
>> targeted; ensuring upgrade is easy reduces pressure for requiring an
>> LTS.
...
>> Albeit remote migration was/is rather a bit experimental in general,
>> but as mentioned above I agree in general with the sentiment.
>
> Apparently would still be useful, even months later:
>
> https://forum.proxmox.com/threads/issue-with-vm-migration-from-proxmox-7-4-to-8-3-involving-cloudinit-drive.163048/
Ok, thanks for the additional pointer.
So consider this patch:
Acked-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
You also have my OK for doing other backports in similar spirit as this one
here – Fabian might have some input in specific commits in mind already it
seems. Then bump and roll the package out over the next few weeks. Should
any user ask then we can argue that this is an exception for update
forward-compatibility only.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-03-05 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 11:54 Fiona Ebner
2025-02-12 10:55 ` Fabian Grünbichler
2025-03-04 18:09 ` Thomas Lamprecht
2025-03-05 9:46 ` Fiona Ebner
2025-03-05 11:12 ` Thomas Lamprecht [this message]
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=a3aa464a-69b7-4a81-b621-09901ebe5f16@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.