WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Re: Hardware differences for 2 xen servers?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Re: Hardware differences for 2 xen servers?
From: "Tijl Van den Broeck" <subspawn@xxxxxxxxx>
Date: Wed, 21 Jun 2006 15:40:15 +0200
Delivery-date: Wed, 21 Jun 2006 06:40:54 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=HfQSh0oMq0xGlYdeNXAfXjftCTj4k3YaDYzZ2pxlo3uiXZnXtBxuvsKZrv3vjyazU8INxj4vHAtygu8MF6B8e/A/mRhEcvV942VH3O9c9Gr7kuK9BpS4JHsz++uGUZHFIQyUv3l6G4tvdPZpkpVLIhW4TEdzZBl3oLENoYoBTHs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060621101936.GC25520@xxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <5bdb1aa70606202127q65e7422auf27bd21fb48069fb@xxxxxxxxxxxxxx> <20060621051714.GB18430@xxxxxxxxxxx> <4498F932.7090307@xxxxxxxxx> <20060621101936.GC25520@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Live migration does indeed require a CPU from the same family
(architecture and features) but afaik a different chipset doesn't
really matter.

On 6/21/06, Matthew Palmer <mpalmer@xxxxxxxxxxx> wrote:
Seriously?  That sounds like a pretty bad failing of live-migration -- I'd
*really* expect live migration to be robust against this sort of thing,
otherwise you'd need to reboot the VM in order to put it onto upgraded
hardware -- and if you've got to reboot it *any* time, then you have to
design your infrastructure to accomodate that, and hence you have the
capability to reboot it without service failure, so you don't really need
live migration after all...

It would indeed be nice if you didn't have to reboot when moving
towards a new architecture family but as you said... one has to design
the infrastructure to ensure service continuity. I think HA-failover
setups between domU's (on seperate dom0's) are most viable and
live-migration is just a feature for small upgrades, for load
balancing and it's nice for showing off ofcourse ;-)

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