From: Friedrich Weber <f.weber@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 4/4] qm: add overrule-shutdown to CLI usage examples
Date: Thu, 18 Apr 2024 15:46:37 +0200 [thread overview]
Message-ID: <20240418134637.262082-5-f.weber@proxmox.com> (raw)
In-Reply-To: <20240418134637.262082-1-f.weber@proxmox.com>
Signed-off-by: Friedrich Weber <f.weber@proxmox.com>
---
qm.adoc | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/qm.adoc b/qm.adoc
index 45e3a57..42c26db 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -1839,6 +1839,13 @@ Same as above, but only wait for 40 seconds.
# qm shutdown 300 && qm wait 300 -timeout 40
----
+If the VM does not shut down, force-stop it and overrule any running shutdown
+tasks. As stopping VMs may incur data loss, use it with caution.
+
+----
+# qm stop 300 -overrule-shutdown 1
+----
+
Destroying a VM always removes it from Access Control Lists and it always
removes the firewall configuration of the VM. You have to activate
'--purge', if you want to additionally remove the VM from replication jobs,
--
2.39.2
_______________________________________________
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:[~2024-04-18 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 13:46 [pve-devel] [PATCH qemu-server/container/docs 0/4] overrule-shutdown: documentation fixes Friedrich Weber
2024-04-18 13:46 ` [pve-devel] [PATCH qemu-server 1/4] api: fix spacing and punctuation in shutdown and stop descriptions Friedrich Weber
2024-04-18 13:46 ` [pve-devel] [PATCH qemu-server 2/4] api: stop: reword overrule-shutdown parameter description Friedrich Weber
2024-04-18 13:46 ` [pve-devel] [PATCH container 3/4] " Friedrich Weber
2024-04-18 13:46 ` Friedrich Weber [this message]
2024-04-18 21:10 ` [pve-devel] applied-series: [PATCH qemu-server/container/docs 0/4] overrule-shutdown: documentation fixes Thomas Lamprecht
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=20240418134637.262082-5-f.weber@proxmox.com \
--to=f.weber@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