Thanx. <div class="gmail_quote">On Mon, Apr 15, 2013 at 8:01 PM, Eric Blake <<a href="mailto:eblake@redhat.com" target="_blank">eblake@redhat.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div class="HOEnZb"><div class="h5">On 04/12/2013 07:28 AM, digvijay chauhan wrote: > Hello, > I am working on live migration of virtual machine using xen and > kvm.If i use qemu+ssh:///system then is the transport protocol used during > live migration tcp or ssh?I mean i want to evaluate the performance of > transport protocil during live migration using wireshark and netperf > tool,so using this command will show tcp performance? > > Orelse i will have to use qemu+tcp:/// ? </div></div>I'd start by reading and understanding this page: <a href="http://libvirt.org/migration.html" target="_blank">http://libvirt.org/migration.html</a> If you do native migration, then it uses whatever protocol the native hypervisor uses (qemu only supports direct tcp), through a separate port. If you use tunnelled migration, then the migration is multiplexed onto libvirt's connection (no additional open port required), and the transport then depends on however you connected to libvirt (whether it is straight TCP or whether it is using SSH depends on the URI of how you connected). Tunnelled migration is inherently slower, since there are more copies involved - qemu -> libvirtd source -> libvirtd destination -> qemu; compared to native migration of qemu -> qemu. But it also provides the possibility of SSH or TLS encryption, if you don't want migration going across the wire unencrypted (since qemu does not yet support encrypted migration natively). -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library <a href="http://libvirt.org" target="_blank">http://libvirt.org</a> </blockquote></div>