From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 839106B07A; Fri, 26 Mar 2021 21:20:28 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7368A2B79C; Fri, 26 Mar 2021 21:20:28 +0100 (CET) Received: from mout.web.de (mout.web.de [212.227.15.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 3D49E2B791; Fri, 26 Mar 2021 21:20:27 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=dbaedf251592; t=1616790020; bh=86De0rcsC2d7/yA2Odnt3Yf056Kzt6G4PqdUDPcEdMM=; h=X-UI-Sender-Class:From:Subject:Date:References:Cc:In-Reply-To:To; b=gkfRt6x2XkbCETKli0uk8IQm2vD+rUU5v8sA0JhJaYq/1p44KCRi6a3m/xPr68LXj XnqnYnl2hsy7VjHV0hqvwQRg/l5nPnBdPsGHmSVVyUz/SiizYuyfwIJ2oS39F5rRmZ 2he0v475m0pcZWj719UrcguodoGgK3VIVpjQa6/c= X-UI-Sender-Class: c548c8c5-30a9-4db5-a2e7-cb6cb037b8f9 Received: from [192.168.179.48] ([78.49.107.251]) by smtp.web.de (mrweb006 [213.165.67.108]) with ESMTPSA (Nemesis) id 1MKuKH-1l5CmH3gRp-00LC1D; Fri, 26 Mar 2021 21:15:00 +0100 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Roland privat Mime-Version: 1.0 (1.0) Date: Fri, 26 Mar 2021 21:14:59 +0100 Message-Id: <5F6C1EDD-1A33-4B90-B5B8-5AC42E052101@web.de> References: <386108369.821.1616775326688@webmail.proxmox.com> Cc: Proxmox VE user list , PVE User List In-Reply-To: <386108369.821.1616775326688@webmail.proxmox.com> To: =?utf-8?Q?Fabian_Gr=C3=BCnbichler?= X-Mailer: iPhone Mail (18D61) X-Provags-ID: V03:K1:8vU3nnai1CR6xVuHzfEdWCEgevHKYn8UXlMjCHmoqQugHNP0464 DN4CTEqzCp4NxdV4LtUfP0VjGxS/DqXyOUXfHtLuPnWwMtP17JVsNTN/zQyraLoXWqlXkpe yVnSGe9dMxsMd+CO4XD7xSChCPEc9jP0nbhq6UBDyJyhKudPtACLh0TMfuUfhFi3XIhZw/o 2cWOB8gJwBmouBpMsEgqw== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:Wf9LDSpU9eA=:uPiRGJIez5LNkGaVVW///U E3cWJ+CURkHt91gXjOsEIZHV70z57lj3r0sifDEbGK5LIDANCZyAf18j5gu4NXt1NYL2FLp8e lrulQc2nt92Z6dC1KztUcGizVIeyUhhuAF9TPCPRRhpVfWZI8SyBFdPPvDgyYYAa0M92KjaWu e//3udHuflqOz8sHqi1Hy8BvP4gCj6/U5Baf1D8BSL6GXlgqwFkfhOqHBYfIpkbFxUlshcAYo VH70aaTe/arL+CaQAVsevM3vb+kmRycADODJcnAo4ZRY17s5IqGuiBlbcExTlI1pqmjDg+OOU BIHpmnVrNI7A0OUJBN03lkry8O5BT50hIDHLjaJ2y19kO2zqUZSyKJyRwdKxpOiFEBcpYAtDE 0qSJ10NiNSwWdw0AJY6fCg1ybl+BR4I4L0thKZIYsT7K6/25/z+amciv/X9zatH4JsQg+tKZu fGJxzG3f7rg4wWnYU38hwwflVdmZxw87rbhbmlhi+PYCfN+WKEKvtZkTpgMXMg+4uI0NAVP0M f0kaLm9TGQPSGnJOkQOEjonrvCZjgKYTbGTA/u3Uzz5jhmIt1nQgLciBfTiqfXBXr9T7WOAbf L5hBMC37PYuyuGzABuDIh2G6qKn5R6MJNSKP37NlXMVdoKEE1psinj1H313N0bnlm4WDlQkPk CmbboA7Wi+om2YodvS5jdmKk7c6pDAfjb1uxMKt4aHus1Fvd2kejYLSddBFC84etpB9ygYC7z nfpxD3IMXuIvogpUjRz57seI2TOC1ikYFom3WKZEj2OG8p86e4ip7wVY9SCqSSspmY0bqH3TA xm0bCHS+JWx+F9I03s3y28UHrthul+VGZS/diPvMz3B7lQsqSydVRrA7O9l+yyp+PqE4RO4n4 bp69TOk54JUZN7TgwBxADdqbTVfEG5T27BHce3Q4x0d3vGtMpf7brF2kjDy94nurp+BfUNn4j UduZsCUKpc9q5N+lc51hd2h2gKXZoiWeahGOuW1k+V67mZkFj8lATv6lKgn9o7+fsBGmnPO4p Ael+AYXfOmTSNR/xzIajx/VPwnUbAnKjn1tTfbg+UzNgey6poXUJ7EkGoZTIa2AUc4w2CQLNQ EH+vEuwRIhJvOEtq4h2BD77ImY2KySX+EF2yyvIlqgpoQ7vf6xRdB9sh6kbC2LT+iMftCjamE CdmgrTaUdkaTZJRiRfJw1sdgVX6I9NUui2hY/E4UlFpyU+pTJojPyE47GNTiz2N+/cXfo= X-SPAM-LEVEL: Spam detection results: 0 DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider RCVD_IN_DNSWL_LOW -0.7 Sender listed at https://www.dnswl.org/, low trust RCVD_IN_MSPIKE_H3 0.001 Good reputation (+3) RCVD_IN_MSPIKE_WL 0.001 Mailspike good senders SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [PVE-User] offline VM migration node1->node2 with local storage X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Mar 2021 20:20:28 -0000 thanks, very nice feature!=20 hope it will be available in webgui one day, though. roland >=20 > Am 26.03.2021 um 17:15 schrieb Fabian Gr=C3=BCnbichler : >=20 > =EF=BB=BF >> Roland hat am 26.03.2021 16:29 geschrieben: >>=20 >>=20 >> Hello, >>=20 >> to pick up this older one: >>=20 >>>>> On 2/16/20 11:28 AM, Roland @web.de wrote: >>> /> why do i need to have the same local storage name when migrating a vm= />>/from node1 to node2 in dual-node cluster with local disks ? />>//>>/i'm= curious that migration is possible in online state (which is much />>/more c= omplex/challenging task) without a problem, but offline i get />/> "storage i= s not available on selected target" (because there are />/> differenz zfs po= ols on both machines) /> >>> This is because offline and online migration use two very different >>> mechanism. >>> AFAIK Qemu NBD is used for online migration and ZFS send->recv is used >>> for offline migration. >>=20 >> i had a closer look on offline-migration, and apparently zfs send->recv i= s only >> being used with ZVOLS, the default for VMs on ZFS. >> for normal (qcow/raw...) files on any filesystem (even zfs), pvesm export= /import >> is being used. >>=20 >> this is working straightforward and apparently, it seems there is missing= >> appropriate logic inside proxmox including missing parameterization in th= e webgui >> (and probably error handling etc..) !? >>=20 >> for example, on the target system i can open a "receiver" like this: >> # pvesm import ${TARGETDS}:100/vm-100-disk-0.qcow2 qcow2+size tcp://10.16= .37.0/24 -with-snapshots 1 -allow-rename 1 >>=20 >> where on the source i can send the data like this: >> # /sbin/pvesm export ${SOURCEDS}:100/vm-100-disk-0.qcow2 qcow2+size - -wi= th-snapshots 1|mbuffer -O 10.16.37.55:60000 >>=20 >> so we apparently see, what's being needed exists at the base level... >>=20 >>>> //>>/i guess there is no real technical hurdle, it just needs to get />= >/implemented appropriatley !? /> >>> There is a patch in the works to make different target storages possible= >>> for offline migration. >>=20 >> has there been any progress on this in the meantime ? >=20 > for compatible storages and setups (e.g., snapshots/replication impose fur= ther restrictions since that is hard to carry across different storage types= /formats), --targetstorage should allow both live and offline migration and s= witching storages in one go. you can provide either a single targetstorage, o= r mappings of source to target storages, or a combination (which means the s= ingle storage is used as fallback for storages for which no explicit mapping= exists). >=20