From: "Michael Köppl" <m.koeppl@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH e2e-tests 6/6] storage-plugin: README: document the vmid-range option
Date: Thu, 17 Sep 2026 18:23:24 +0200 [thread overview]
Message-ID: <20260917162324.1926056-7-m.koeppl@proxmox.com> (raw)
In-Reply-To: <20260917162324.1926056-1-m.koeppl@proxmox.com>
proxmox-test-runner exposes the range the tests draw their guest VMIDs
from, so list it with the other options a run may need. Concurrent runs
against one cluster can entirely avoid collisions through disjoint
ranges.
Signed-off-by: Michael Köppl <m.koeppl@proxmox.com>
---
storage-plugin-tests/README | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/storage-plugin-tests/README b/storage-plugin-tests/README
index 5f486a4..fe6972d 100644
--- a/storage-plugin-tests/README
+++ b/storage-plugin-tests/README
@@ -36,6 +36,10 @@ Options you may need
from the cluster status when omitted. The tests
are skipped on a node that is not clustered.
--iso-url URL An ISO image URL for the content-download test.
+ --vmid-range START:END Confine the VMIDs of the guests the tests
+ create to this range. Give concurrent runs on
+ one cluster disjoint ranges so they cannot
+ draw the same id. Defaults to 1000000:9999999.
--tags +storage-plugin-guest Also run the guest-based tests (see below).
Guest-based tests
--
2.47.3
prev parent reply other threads:[~2026-09-17 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 16:23 [PATCH test-tools,e2e-tests 0/6] randomly select VMIDs for test Michael Köppl
2026-09-17 16:23 ` [PATCH test-tools 1/6] runner: add vmid-range option for test guest VMIDs Michael Köppl
2026-09-17 16:23 ` [PATCH e2e-tests 2/6] lib: add function for drawing a random unused VMID Michael Köppl
2026-09-17 16:23 ` [PATCH e2e-tests 3/6] storage-plugin: use random_vmid function for getting VMIDs Michael Köppl
2026-09-17 16:23 ` [PATCH e2e-tests 4/6] hw-validation: " Michael Köppl
2026-09-17 16:23 ` [PATCH e2e-tests 5/6] tests: " Michael Köppl
2026-09-17 16:23 ` 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=20260917162324.1926056-7-m.koeppl@proxmox.com \
--to=m.koeppl@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