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

RE: [Xen-users] about migration betweendifferents architecture


  • To: "Javier Guerra" <javier@xxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
  • Date: Wed, 26 Apr 2006 19:06:09 +0200
  • Delivery-date: Wed, 26 Apr 2006 10:07:06 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcZpUogkU7+umQC2Tx6k5nAtADpV/QAAQECQ
  • Thread-topic: [Xen-users] about migration betweendifferents architecture

 

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Javier Guerra
> Sent: 26 April 2006 17:56
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] about migration betweendifferents 
> architecture
> 
> Quoting Mark Williamson <mark.williamson@xxxxxxxxxxxx>: 
>  
> > > I always thought that on a x86-64-system only 64 bit-domU's will 
> > > work and on i386 only 32 bit. Is this not true anymore?
> >  
> > Right now it's still true. 
>  
> i think the mantra is something like "the memory model of a 
> paravirtualized kernel must match that of the hypervisor" 
>  
> > So, folks, no migrating between 64 and 32 bit architectures.  It's 
> > naughty,
> >  
> > yall hear?  ;-)
>  
> in this particular case, it might be a solution to just use 
> the x86-64 in totally 32 bit mode, with 32bit xen hypervisor. 
>  would that work? 
Yes, that would be the way to work it. Since the 64-bit processor is
100% 32-bit compatible, it shouldn't make any difference (except you're
not wearing down the upper 32-bits of the registers ;-) ). 

--
Mats
>  
> ------
> Javier 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 
> 


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


 


Rackspace

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