This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Domain save/migrate issue

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Domain save/migrate issue
From: "Noam Taich" <noam.taich@xxxxxxxxxxxx>
Date: Tue, 14 Feb 2006 05:45:16 -0800
Delivery-date: Tue, 14 Feb 2006 16:33:33 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcYxbOMnCzCJKWnPQdiwvJ3prGfrSA==
Thread-topic: Domain save/migrate issue

As it stands now, when a domain is saved to disk it is suspended in the process, and then destroyed. This is done by the checkpointing code in Xend.
However, it's a good idea to leave the option open to the user whether or not the saved domain should be kept alive or be suspended,
as it is very possible this feature may be used in real checkpointing of a working domain state, just in order to not lose everything should something go wrong.

if you have a guest which does some heavy calculations, or one which handles many customer's connection this may be a good idea even in migration (which calls the checkpointing code anyway.), although in the latter case, of course the network interfaces of the new domain will be taken down, and it may be used as a hot spare ready for a quick hook-up...

So what do you think?

I'm thinking of either using pause/unpause instead of suspend and manually save the info the suspend record would have contained,
OR recreating the vcpu after HYPERVISOR_suspend() is done with it, remapping the necessary fns.

Xen-devel mailing list