From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [RFC qemu-server] more flexible restore
Date: Fri, 15 Apr 2022 14:31:24 +0200 [thread overview]
Message-ID: <20220415123130.49099-1-f.ebner@proxmox.com> (raw)
Allows keeping around certain disks and overriding VM settings upon
restore.
Only gave this some very rudimentary testing, because I'm not fully
restored yet after getting sick earlier this week. Didn't test the
combniation with live-restore at all yet.
First few patches are related improvements/cleanups.
Last patch depends on
https://lists.proxmox.com/pipermail/pve-devel/2022-April/052558.html
Fabian Ebner (6):
restore: cleanup oldconf: also clean up snapshots from kept volumes
restore destroy volumes: remove check for absolute path
restore deactivate volumes: never die
restore: also deactivate/destroy cloud-init disk upon error
api: create: refactor parameter check logic
restore: allow overriding settings upon restore
PVE/API2/Qemu.pm | 48 ++++++++++++++---------
PVE/QemuServer.pm | 98 +++++++++++++++++++++++++++++++++--------------
2 files changed, 99 insertions(+), 47 deletions(-)
--
2.30.2
next reply other threads:[~2022-04-15 12:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 12:31 Fabian Ebner [this message]
2022-04-15 12:31 ` [pve-devel] [RFC qemu-server 1/6] restore: cleanup oldconf: also clean up snapshots from kept volumes Fabian Ebner
2022-04-15 12:31 ` [pve-devel] [RFC qemu-server 2/6] restore destroy volumes: remove check for absolute path Fabian Ebner
2022-04-15 12:31 ` [pve-devel] [RFC qemu-server 3/6] restore deactivate volumes: never die Fabian Ebner
2022-04-15 12:31 ` [pve-devel] [RFC qemu-server 4/6] restore: also deactivate/destroy cloud-init disk upon error Fabian Ebner
2022-04-15 12:31 ` [pve-devel] [RFC qemu-server 5/6] api: create: refactor parameter check logic Fabian Ebner
2022-04-15 12:31 ` [pve-devel] [RFC qemu-server 6/6] restore: allow overriding settings upon restore Fabian Ebner
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=20220415123130.49099-1-f.ebner@proxmox.com \
--to=f.ebner@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