From: Daniel Kral <d.kral@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH container 1/2] migration: allow rbd storages for remote migration
Date: Wed, 18 Dec 2024 15:21:25 +0100 [thread overview]
Message-ID: <e17bb790-3868-4d8c-a5eb-86839ca36236@proxmox.com> (raw)
In-Reply-To: <20241218103206.20822-1-f.ebner@proxmox.com>
On 12/18/24 11:32, Fiona Ebner wrote:
> [ ... ]
> --- a/src/PVE/LXC/Migrate.pm
> +++ b/src/PVE/LXC/Migrate.pm
> @@ -303,6 +303,7 @@ sub phase1 {
> if ($remote) {
> push @$migratable_storages, 'cifs';
> push @$migratable_storages, 'nfs';
> + push @$migratable_storages, 'rbd';
> }
>
> die "storage type '$scfg->{type}' not supported\n"
Works as expected, without this patch the remote migration fails. When
applied, containers stored on rbd storages are also allowed.
Tested-by: Daniel Kral <d.kral@proxmox.com>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-12-18 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 10:32 Fiona Ebner
2024-12-18 10:32 ` [pve-devel] [PATCH container 2/2] migration: add reminder to evaluate dropping seemingly useless check for PVE 9 Fiona Ebner
2024-12-18 14:21 ` Daniel Kral [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=e17bb790-3868-4d8c-a5eb-86839ca36236@proxmox.com \
--to=d.kral@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