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-devel

[Xen-devel] Fwd: Examples for using xl migrate -s ?

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Fwd: Examples for using xl migrate -s ?
From: Florian Heigl <florian.heigl@xxxxxxxxx>
Date: Thu, 27 Oct 2011 22:47:34 +0200
Delivery-date: Thu, 27 Oct 2011 13:48:40 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=0ZCXZI2PYeSkFRBoF/Fxerwo1pBEnHC17NhCWVuhvwg=; b=ZfhTuQxhPk2kFMLq7xdmGeWh5cL9e6EyMrnaMC2FCtI7wOWdowtf8/+1seMlnhI1fi rQAFvO/f1oUYDI+J8xPaLbPrZLv9Au1OEHITp8HRwFqw/tpH83b8pTHpEG4GkBfy0R9t utxk7BtHHWMtnvdZ1zji60wWFEuclL2Yy1LFM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CAFivhPmT1mfzaQbPDviB4jMAUBe5u-cruXtDz7U2Jh7jWrPCcQ@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <CAFivhPmT1mfzaQbPDviB4jMAUBe5u-cruXtDz7U2Jh7jWrPCcQ@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

sorry to disturb, but are there any in-depth docs about migration in xl?
It appears this is not just me not knowing it :>

Greetings,
Florian


---------- Forwarded message ----------
From: Florian Heigl <florian.heigl@xxxxxxxxx>
Date: 2011/10/25
Subject: Examples for using xl migrate -s ?
To: Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>


Hi,

I must find a way around the way live migration now uses ssh. I tested
it and I see high cpu usage by SSH and overall sense of things being
slow.
My prod systems have a dedicated, fast link for live migration, but
with ssh it would be crippled down to a <1Gbit.
Does anyone have a working example of how to not use SSH as the transport layer?

I guess this is what the -s option is for, but I don't really get how
it's intended to be used.

What I can think of ( -s "ssh other box, run netcat listener there;
launch nc locally and receive migration data) sounds absolutely
disgusting...

Thanks for any pointers,
Florian

--
the purpose of libvirt is to provide an abstraction layer hiding all
xen features added since 2006 until they were finally understood and
copied by the kvm devs.



-- 
the purpose of libvirt is to provide an abstraction layer hiding all
xen features added since 2006 until they were finally understood and
copied by the kvm devs.

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

<Prev in Thread] Current Thread [Next in Thread>