From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60170) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZkCaf-00026s-Ic for qemu-devel@nongnu.org; Thu, 08 Oct 2015 10:54:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZkCab-00085u-F8 for qemu-devel@nongnu.org; Thu, 08 Oct 2015 10:54:41 -0400 Received: from relay.parallels.com ([195.214.232.42]:58229) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZkCab-00084y-7I for qemu-devel@nongnu.org; Thu, 08 Oct 2015 10:54:37 -0400 References: <5614531B.5080107@redhat.com> <1444198846-5383-1-git-send-email-den@openvz.org> <1444198846-5383-4-git-send-email-den@openvz.org> <561534A4.1070306@redhat.com> From: "Denis V. Lunev" Message-ID: <5616839E.1050909@openvz.org> Date: Thu, 8 Oct 2015 17:54:22 +0300 MIME-Version: 1.0 In-Reply-To: <561534A4.1070306@redhat.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] [PATCH 3/8] migration: add new capability test-only List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake Cc: Igor Redko , jsnow@redhat.com, qemu-devel@nongnu.org, annam@virtuozzo.com On 10/07/2015 06:05 PM, Eric Blake wrote: > On 10/07/2015 12:20 AM, Denis V. Lunev wrote: >> From: Igor Redko >> >> This patch declares a new migration capability that allows >> to distinguish between true migration and the test. >> >> An alternative is using a custom URI but in this case the >> following problems should be solved: >> 1/ QEMUFile abstraction hides the real transport type >> 2/ We must be ensured that VM will not be stopped due to >> “successful migration” >> >> Possible solutions: >> 1/ Using global variable analogous to >> s->enabled_capabilities[MIGRATION_CAPABILITY_TEST_ONLY] that >> will be initialized according to the migration type at the >> beginning of the migration process >> 2/ Additional hook, presence of implementation of which allows >> to decide whether the migration is true >> > Do we want to name the capability 'x-test-only', since this series is > experimental, to make it obvious that production code should not rely on it? > actually the answer is 'no'. This feature is designated for production. May be the name is just wrong or description is bad :) Yep, I know this for sure... OK. The idea of this feature is to estimate efforts required to perform migration and downtime during that migration. This estimate is necessary to decide whether we are able to automatically move the VM from one node (loaded) to different node with less load. Should we rename 'test' to 'estimate' or something like that to make the situation clearer? On the other hand this 'estimate' state would be very useful for testing that is why I have proposed this code to John. At least we were able to catch recently fixed hang on migration cancel (in pipeline already). I am completely open to any idea. >> +++ b/qapi-schema.json >> @@ -540,11 +540,14 @@ >> # @auto-converge: If enabled, QEMU will automatically throttle down the guest >> # to speed up convergence of RAM migration. (since 1.6) >> # >> +# @test-only: If enabled, QEMU instead of migrating will estimate migration >> +# time basing on given downtime and current dirty page rate > If we do decide to add this to mainline, it would need 'since 2.5' (or > whatever version) documentation. > Sure!