From mboxrd@z Thu Jan 1 00:00:00 1970 From: Uri Lublin Subject: Re: [KVM-AUTOTEST] [PATCH] support for remote migration Date: Wed, 27 May 2009 17:27:19 +0300 Message-ID: <4A1D4DC7.4060005@redhat.com> References: <796594249.90621241466107981.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com> <1473872622.90691241466166259.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Michael Goldish , yogi , kvm@vger.kernel.org To: sudhir kumar Return-path: Received: from mx2.redhat.com ([66.187.237.31]:45321 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758264AbZE0O1W (ORCPT ); Wed, 27 May 2009 10:27:22 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: sudhir kumar wrote: > Michael, > any updates on this patch? Are you going to commit this or you have > any other plans/patch ? > I'm not sure having the inter-host migration is best implemented on the autotest-client side. Actually this is one of the few tests I think belong to the autotest-server side. On the other hand it is pretty simple to implement it here. So I think we'd better try first implementing it as a server test, and apply it to the client side only as a second choice. A few (minor) problems with it running on the client side: 1. We do not know what the other host is running (what version?, kvm-modules loaded? etc.) 2. There may be a conflict between a running local guest running on the remote (if it allowed to run tests while being a migration destination), and the remote guest. 3. There may be a conflict between two remote guests running a migration test on two different hosts. 3. get_free_ports run on the local machine, but expected/assumed to be free on the remote machine too. 4. For a migration to be successful, the image(s) must be shared by both hosts. On the other hand, when installing a guest OS (e.g. Fedora 8) on both hosts (let's assume they both are running fc8_quick) we want different images on different hosts. These are all can be solved easily by non-trivial pretty simple configuration on the server. One can configure the "remote" migration to run as a separate tests to all other tests. Regards, Uri.