From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: [PATCHv1 0/5] tools: rework VM Generation ID Date: Wed, 21 May 2014 14:21:02 +0100 Message-ID: <1400678467-23559-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.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Wn6SJ-000419-QE for xen-devel@lists.xenproject.org; Wed, 21 May 2014 13:21:15 +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: Andrew Cooper , 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. For xl, a new ID is required when restoring from a saved image (but not after a migration, reboot, pause/unpause). Can someone advise on the best way to implement this in xl? We could put a vm-generation-id variable in the domain configuration file. This would end up in the saved configuration file and would be reused or regenerated on restore depending on whether the domain was migrated or restored from a file. You can download the spec from: http://www.microsoft.com/en-us/download/details.aspx?id=30707 David