From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id C11A51FF37F for ; Thu, 18 Apr 2024 15:47:53 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 3C42D1DC21; Thu, 18 Apr 2024 15:47:46 +0200 (CEST) From: Friedrich Weber To: pve-devel@lists.proxmox.com Date: Thu, 18 Apr 2024 15:46:37 +0200 Message-Id: <20240418134637.262082-5-f.weber@proxmox.com> X-Mailer: git-send-email 2.39.2 In-Reply-To: <20240418134637.262082-1-f.weber@proxmox.com> References: <20240418134637.262082-1-f.weber@proxmox.com> MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.063 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH docs 4/4] qm: add overrule-shutdown to CLI usage examples X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Signed-off-by: Friedrich Weber --- 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