Re: [sami] First SAMI email in the new year, can we go further? Look forward to your opinions.

Thomas Narten <narten@us.ibm.com> Thu, 01 March 2012 16:16 UTC

Return-Path: <narten@us.ibm.com>
X-Original-To: sami@ietfa.amsl.com
Delivered-To: sami@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6498521F8850 for <sami@ietfa.amsl.com>; Thu, 1 Mar 2012 08:16:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.468
X-Spam-Level:
X-Spam-Status: No, score=-109.468 tagged_above=-999 required=5 tests=[AWL=1.131, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WszNOZCI+jd2 for <sami@ietfa.amsl.com>; Thu, 1 Mar 2012 08:16:37 -0800 (PST)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id 8D92621F87AD for <sami@ietf.org>; Thu, 1 Mar 2012 08:16:37 -0800 (PST)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <sami@ietf.org> from <narten@us.ibm.com>; Thu, 1 Mar 2012 11:16:35 -0500
Received: from d01dlp01.pok.ibm.com (9.56.224.56) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Thu, 1 Mar 2012 11:16:23 -0500
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 9437038C827E for <sami@ietf.org>; Thu, 1 Mar 2012 11:14:09 -0500 (EST)
Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q21GE8ma293230 for <sami@ietf.org>; Thu, 1 Mar 2012 11:14:08 -0500
Received: from d03av06.boulder.ibm.com (loopback [127.0.0.1]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q21GEAix024233 for <sami@ietf.org>; Thu, 1 Mar 2012 09:14:10 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-65-232-28.mts.ibm.com [9.65.232.28]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q21GE8Sw024144 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Mar 2012 09:14:09 -0700
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q21GDAob025552; Thu, 1 Mar 2012 11:13:11 -0500
Message-Id: <201203011613.q21GDAob025552@cichlid.raleigh.ibm.com>
To: Melinda Shore <melinda.shore@gmail.com>
In-reply-to: <4F4F9DA3.5030901@gmail.com>
References: <A27496C192613C44A82D819E1B98DB5721DAE9A6@SZXEML511-MBS.china.huawei.com> <201203011329.q21DTbkD023885@cichlid.raleigh.ibm.com> <4F4F9DA3.5030901@gmail.com>
Comments: In-reply-to Melinda Shore <melinda.shore@gmail.com> message dated "Thu, 01 Mar 2012 07:02:43 -0900."
Date: Thu, 01 Mar 2012 11:13:10 -0500
From: Thomas Narten <narten@us.ibm.com>
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12030116-7182-0000-0000-000000F03AFA
Cc: "Yingjie Gu(yingjie)" <guyingjie@huawei.com>, "sami@ietf.org" <sami@ietf.org>
Subject: Re: [sami] First SAMI email in the new year, can we go further? Look forward to your opinions.
X-BeenThere: sami@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: State Migration <sami.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sami>, <mailto:sami-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sami>
List-Post: <mailto:sami@ietf.org>
List-Help: <mailto:sami-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sami>, <mailto:sami-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 16:16:38 -0000

Hmm. Maybe I misunderstand.

Live migration happens today.  You start transferring the VM, but it
continues running. At some point, you have to freeze the VM, finish
transferring state (and any "dirty" pages) and enable the transferred
VM at the new location and resume it.

That does mean that an active VM in one place is migrated "live" (with
a short downtime of sub seconds) to another place.

This is not a case where the VM shuts down and new one is instantiated
(i.e., started from scratch) elsewhere.

Isn't this what VM migration means?

Thomas