similar to: comparion between xen n kvm :Performance analysis of transport protocol(TCP) during live migration

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:/// ?

Hello, I want to do live migration of virtual machine on xen using fedora.SO what are the steps to have the live migration possible. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

Hello, I want to carry out the performance analysis of transport protocol i.e sctp so how can we achieve it.Instead of using tcp if we have to use sctp how to do that? regards, DigvijaySingh _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

Hello, I want to carry out the performance analysis of transport protocol i.e sctp so how can we achieve it.Instead of using tcp if we have to use sctp how to do that? regards, DigvijaySingh _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

Hello all, I want to optimize the pre copy algorithm.So in which file can I find the implementation of algorithm.And how to understand the working of code? Which part causes the live migration in code? regards, DigvijaySingh _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

On Wed, Mar 16, 2016 at 05:05:19PM +0200, Michael S. Tsirkin wrote: > > > > NFS and netperf are the first two protocols I looked > > > > at and both transmit address information across the connection... > > > > > > > > > Does netperf really attempt to get local IP > > > and then send that inline within the connection? > >

On Wed, Mar 16, 2016 at 05:05:19PM +0200, Michael S. Tsirkin wrote: > > > > NFS and netperf are the first two protocols I looked > > > > at and both transmit address information across the connection... > > > > > > > > > Does netperf really attempt to get local IP > > > and then send that inline within the connection? > >

On Wed, Mar 16, 2016 at 02:32:00PM +0000, Stefan Hajnoczi wrote: > On Tue, Mar 15, 2016 at 06:12:55PM +0200, Michael S. Tsirkin wrote: > > On Tue, Mar 15, 2016 at 03:15:29PM +0000, Stefan Hajnoczi wrote: > > > On Mon, Mar 14, 2016 at 01:13:24PM +0200, Michael S. Tsirkin wrote: > > > > On Thu, Mar 03, 2016 at 03:37:37PM +0000, Stefan Hajnoczi wrote: > > > >

On Tue, Mar 15, 2016 at 03:15:29PM +0000, Stefan Hajnoczi wrote: > On Mon, Mar 14, 2016 at 01:13:24PM +0200, Michael S. Tsirkin wrote: > > On Thu, Mar 03, 2016 at 03:37:37PM +0000, Stefan Hajnoczi wrote: > > > Michael pointed out that the virtio-vsock draft specification does not > > > address live migration and in fact currently precludes migration. > > > >

On Tue, Mar 15, 2016 at 06:12:55PM +0200, Michael S. Tsirkin wrote: > On Tue, Mar 15, 2016 at 03:15:29PM +0000, Stefan Hajnoczi wrote: > > On Mon, Mar 14, 2016 at 01:13:24PM +0200, Michael S. Tsirkin wrote: > > > On Thu, Mar 03, 2016 at 03:37:37PM +0000, Stefan Hajnoczi wrote: > > > > Michael pointed out that the virtio-vsock draft specification does not > >

On Tue, Mar 15, 2016 at 06:12:55PM +0200, Michael S. Tsirkin wrote: > On Tue, Mar 15, 2016 at 03:15:29PM +0000, Stefan Hajnoczi wrote: > > On Mon, Mar 14, 2016 at 01:13:24PM +0200, Michael S. Tsirkin wrote: > > > On Thu, Mar 03, 2016 at 03:37:37PM +0000, Stefan Hajnoczi wrote: > > > > Michael pointed out that the virtio-vsock draft specification does not > >

On Mon, Mar 14, 2016 at 01:13:24PM +0200, Michael S. Tsirkin wrote: > On Thu, Mar 03, 2016 at 03:37:37PM +0000, Stefan Hajnoczi wrote: > > Michael pointed out that the virtio-vsock draft specification does not > > address live migration and in fact currently precludes migration. > > > > Migration is fundamental so the device specification at least mustn't > >

On Mon, Mar 14, 2016 at 01:13:24PM +0200, Michael S. Tsirkin wrote: > On Thu, Mar 03, 2016 at 03:37:37PM +0000, Stefan Hajnoczi wrote: > > Michael pointed out that the virtio-vsock draft specification does not > > address live migration and in fact currently precludes migration. > > > > Migration is fundamental so the device specification at least mustn't > >

Hello, I have been trying to livemigrate one of our KVM machines that has a local storage device, but it's failing. With error: error: internal error: unable to execute QEMU command 'migrate': this feature or command is not currently supported . After a bit of indepths look. I found out that local disk migration is not enabled with qemu-kvm-ev package. I have also tried to save

Le 16/08/2010 19:20, Rick Jones a écrit : > Klein Stéphane wrote: >> Hi, >> >> I''ve two computer : >> * A : it''s a server with a firewall >> * B : an computer on internet >> >> I''ve installed netserver on host A. >> I use netperf on host B. >> >> On host B, I launch : >> >> $ netperf -H

Hello, I am now testing XEN live migration on 3 physical hosts with XEN 4.0.1 pvops Ubuntu 10.10 (2.6.35-22). The kernel is compiled and built with default selections plus the support for ext4 file system as well as the support for network file system server. The three hosts are connected by one D-link gigabit switch (DGS-2205). I find that: 1) If the 3 hosts are booted about the same time, the

box. I'll send an updated KVM tools patch in a bit as well. Before: # netperf -H 192.168.33.4,ipv4 -t TCP_RR MIGRATED TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.33.4 (192.168.33.4) port 0 AF_INET : first burst 0 Local /Remote Socket Size Request Resp. Elapsed Trans. Send Recv Size Size Time Rate bytes Bytes bytes bytes

box. I'll send an updated KVM tools patch in a bit as well. Before: # netperf -H 192.168.33.4,ipv4 -t TCP_RR MIGRATED TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.33.4 (192.168.33.4) port 0 AF_INET : first burst 0 Local /Remote Socket Size Request Resp. Elapsed Trans. Send Recv Size Size Time Rate bytes Bytes bytes bytes

> Subject: Re: [PATCH v3 kernel 0/7] Extend virtio-balloon for fast (de)inflating > & fast live migration > > 2016-08-08 14:35 GMT+08:00 Liang Li <liang.z.li at intel.com>: > > This patch set contains two parts of changes to the virtio-balloon. > > > > One is the change for speeding up the inflating & deflating process, > > the main idea of this

> Subject: Re: [PATCH v3 kernel 0/7] Extend virtio-balloon for fast (de)inflating > & fast live migration > > 2016-08-08 14:35 GMT+08:00 Liang Li <liang.z.li at intel.com>: > > This patch set contains two parts of changes to the virtio-balloon. > > > > One is the change for speeding up the inflating & deflating process, > > the main idea of this