From: Philipp Hufnagl <p.hufnagl@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-docs] pmxcfs: fix incorrect exmple command
Date: Fri, 14 Jul 2023 11:18:39 +0200 [thread overview]
Message-ID: <20230714091839.36336-1-p.hufnagl@proxmox.com> (raw)
There is an error in this example. The .conf has to be moved in the
quemu-server folder of the new node for the migration to work.
Signed-off-by: Philipp Hufnagl <p.hufnagl@proxmox.com>
---
pmxcfs.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pmxcfs.adoc b/pmxcfs.adoc
index ca4e327..f4aa847 100644
--- a/pmxcfs.adoc
+++ b/pmxcfs.adoc
@@ -226,7 +226,7 @@ For example, recovering the VM with ID `100` from an offline `node1` to another
node `node2` works by running the following command as root on any member node
of the cluster:
- mv /etc/pve/nodes/node1/qemu-server/100.conf /etc/pve/nodes/node2/
+ mv /etc/pve/nodes/node1/qemu-server/100.conf /etc/pve/nodes/node2/qemu-server/
WARNING: Before manually recovering a guest like this, make absolutely sure
that the failed source node is really powered off/fenced. Otherwise {pve}'s
--
2.39.2
next reply other threads:[~2023-07-14 9:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 9:18 Philipp Hufnagl [this message]
2023-07-17 13:10 ` [pve-devel] applied: " 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=20230714091839.36336-1-p.hufnagl@proxmox.com \
--to=p.hufnagl@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