[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] save/restore of domU-s different in size from dom0


  • To: Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Wed, 25 Apr 2007 15:23:22 +0100
  • Delivery-date: Wed, 25 Apr 2007 07:22:12 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AceHRUctheEdK/M4EduM1gAX8io7RQ==
  • Thread-topic: [Xen-devel] save/restore of domU-s different in size from dom0

On 25/4/07 15:13, "Jan Beulich" <jbeulich@xxxxxxxxxx> 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



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.