From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: [PATCHv3 0/6] tools: rework VM Generation ID Date: Tue, 3 Jun 2014 14:15:34 +0100 Message-ID: <1401801340-6196-1-git-send-email-david.vrabel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WroZD-0006C7-TF for xen-devel@lists.xenproject.org; Tue, 03 Jun 2014 13:15:52 +0000 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xenproject.org Cc: Ian Jackson , Ian Campbell , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org This series reworks the VM Generation ID to a) conform to the published spec from Microsoft; b) simplify the save/restore code; and c) extend the libxl API to allow toolstacks to use this feature. The VM Generation ID must be regenerated with a new random ID after certain VM operations. Since xl lacks infrastructure for tracking the life-cycle of snapshots and clones (etc), the safe option of always using a new generation ID is used. You can download the spec from: http://www.microsoft.com/en-us/download/details.aspx?id=30707 Changes in v3: - Specify generation ID in libxl_domain_build_info instead of having to call a function to set it. - Improve docs. Changes in v2: - Use libxl_uuid for the generation ID. - Add "generation_id" option to xl domain configuration file and use this to set a random generation ID every time. David