From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: save/restore of domU-s different in size from dom0 Date: Wed, 25 Apr 2007 15:23:22 +0100 Message-ID: References: <462F7E2D.76E4.0078.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <462F7E2D.76E4.0078.0@novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 25/4/07 15:13, "Jan Beulich" wrote: > Looking at the present code in xc_domain_save.c, I take it for granted that > saving a 32-bit domU with a 64-bit dom0 (or vice versa) cannot be expected > to work, yet (since the vcpu context structure layout is different and domctl > returns a context matching the domain being saved, bi-modal code appears > to be necessary here). Am I missing something? Save on 64-bit dom0 and restore on 32-bit dom0 (or vice versa) certainly won't work as longs are used all over the place in the save format. Currently dom0 and domU need to be matched (both 32-bit or both 64-bit). The bitness of Xen itself does not matter. 64-bit domU save/restore with 32-bit dom0 is probably not that interesting. 32-bit domU save/restore with 64-bit dom0 will at least require pt_levels and hvirt_start to be initialised based on domain-specific details. -- Keir