From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33564) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZjXGF-0000Dw-IE for qemu-devel@nongnu.org; Tue, 06 Oct 2015 14:46:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZjXG7-00038G-NY for qemu-devel@nongnu.org; Tue, 06 Oct 2015 14:46:51 -0400 Received: from mx1.redhat.com ([209.132.183.28]:37418) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZjXG7-000389-GR for qemu-devel@nongnu.org; Tue, 06 Oct 2015 14:46:43 -0400 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (Postfix) with ESMTPS id 1F00733F792 for ; Tue, 6 Oct 2015 18:46:43 +0000 (UTC) From: John Snow Message-ID: <56141712.1010202@redhat.com> Date: Tue, 6 Oct 2015 14:46:42 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Debugging Migration List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel Cc: "Dr. David Alan Gilbert" Is there a convenient way of "pausing" or stalling a live migration to allow methodical testing of race conditions? I'd like to instrument something along the lines of: (1) Live migration begins. (2) migration is artificially halted or paused, but QEMU is allowed to run. (3) Some additional qtest/QMP commands are received and processed. (4) migration is allowed to resume. Does anyone have perhaps even test patches to instrument this sort of thing, or is it up to detective john to add it if he wants it? Thanks, --js