From: "Michael Köppl" <m.koeppl@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Cc: t.lamprecht@proxmox.com, pve-devel <pve-devel-bounces@lists.proxmox.com>
Subject: superseded: [pve-devel] [PATCH SERIES v4] Add ability to prevent suggesting previously used VM/CT IDs
Date: Mon, 21 Sep 2026 18:00:47 +0200 [thread overview]
Message-ID: <DLL4BTU6TT7K.MG3UTO37MQDJ@proxmox.com> (raw)
In-Reply-To: <mailman.62.1731030290.372.pve-devel@lists.proxmox.com>
It has been a while since there has been any activity on this series
and the topic of unique VMIDs has been more actively discussed again
recently, which is why I created a v5 of this series:
https://lore.proxmox.com/pve-devel/20260921155410.938337-1-m.koeppl@proxmox.com
I hope I didn't misattribute any of the commits (regarding the
trailers).
On Fri Nov 8, 2024 at 2:44 AM CET, Severen Redwood via pve-devel wrote:
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2026-09-21 16:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 1:44 [pve-devel] [PATCH SERIES v4] Add ability to prevent suggesting previously used VM/CT IDs Severen Redwood via pve-devel
2024-11-08 1:46 ` [pve-devel] [PATCH manager v4 1/2] close #4369: api: optionally only suggest unique IDs Severen Redwood via pve-devel
2025-01-27 12:16 ` Fabian Grünbichler
2025-03-26 3:50 ` Severen Redwood via pve-devel
[not found] ` <20241108014620.73352-1-severen.redwood@sitehost.co.nz>
2024-11-08 1:46 ` [pve-devel] [PATCH manager v4 2/2] close #4369: ui: add datacenter option for unique VM/CT IDs Severen Redwood via pve-devel
2024-11-08 1:46 ` [pve-devel] [PATCH cluster v4 1/2] cluster files: add used_vmids.list Severen Redwood via pve-devel
2025-01-27 12:18 ` Fabian Grünbichler
2025-01-28 14:57 ` Thomas Lamprecht
2025-03-26 3:51 ` Severen Redwood via pve-devel
[not found] ` <fd441572-6c7c-4b62-bdef-0d738ac699fb@sitehost.co.nz>
2025-03-26 7:22 ` Thomas Lamprecht
2025-03-27 21:02 ` Severen Redwood via pve-devel
2024-11-08 1:46 ` [pve-devel] [PATCH cluster v4 2/2] datacenter config: add unique-next-id to schema Severen Redwood via pve-devel
2024-11-08 1:46 ` [pve-devel] [PATCH qemu-server v4] api: record VM ID as used after a virtual machine is destroyed Severen Redwood via pve-devel
2024-11-08 1:46 ` [pve-devel] [PATCH container v4] api: record CT ID as used after a container " Severen Redwood via pve-devel
2025-01-27 12:16 ` Fabian Grünbichler
2025-03-26 3:51 ` Severen Redwood via pve-devel
2024-12-03 21:43 ` [pve-devel] [PATCH SERIES v4] Add ability to prevent suggesting previously used VM/CT IDs Severen Redwood via pve-devel
[not found] ` <d39f8d05-d5a6-48c9-996a-dca751f62ff3@sitehost.co.nz>
2025-01-19 22:01 ` Severen Redwood via pve-devel
2026-09-21 16:00 ` Michael Köppl [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=DLL4BTU6TT7K.MG3UTO37MQDJ@proxmox.com \
--to=m.koeppl@proxmox.com \
--cc=pve-devel-bounces@lists.proxmox.com \
--cc=pve-devel@lists.proxmox.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 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.