search for: setspeed

Hi all, As I am doing some tests with qemu, I realized that the way it does 'migrate -i tcp:DEST:444' is not the same as 'libvirt migrate --copy-storage-inc'. Basically qemu uses the same stream as RAM migration and libvirt takes advantage of NBD transfer. With virsh migrate-setspeed I observed that one can only control the transfer throughput of RAM, but not disk synchronization. At least this is what I can see in bmon when doing a migration with incremental copy. The question is: Am I missing something or it is not implemented? Thank you guys!

...e) and the actual migration speed was about 100MB/s. now in c6.5 the actual migration speed dropped down to about 25MB/s - 50MB/s, it varies and sometimes during migration of huge machines (36GB) i was at 100MB/s, but only for seconds. i tried also to set speed using this command: virsh migrate-setspeed <domain> --bandwidth 1000 but it seems it has no affect, i remember in c6.3 the default migration speed was 33% of total bandwidth and at that time the above command worked and 100% were used during migration. can anyone confirm this ?? thanks ulrich

...some tests with qemu, I realized that the way it does > 'migrate -i tcp:DEST:444' is not the same as 'libvirt migrate > --copy-storage-inc'. Basically qemu uses the same stream as RAM > migration and libvirt takes advantage of NBD transfer. > > With virsh migrate-setspeed I observed that one can only control the > transfer throughput of RAM, but not disk synchronization. At least this > is what I can see in bmon when doing a migration with incremental copy. > > The question is: Am I missing something or it is not implemented? > > Thank you guys...

Hello, I'd like to know if this is an hypervisor related problem or a libvirt one. I did this experiment: on VM I started watching a video on youtube. While video was in progress I started migration. Migration did not complete until video was not finished. I did another experiment: I installed a web server on VM. I then started an httperf stress test. As before migration did not complete

...realized that the way it does > > 'migrate -i tcp:DEST:444' is not the same as 'libvirt migrate > > --copy-storage-inc'. Basically qemu uses the same stream as RAM > > migration and libvirt takes advantage of NBD transfer. > > > > With virsh migrate-setspeed I observed that one can only control the > > transfer throughput of RAM, but not disk synchronization. At least this > > is what I can see in bmon when doing a migration with incremental copy. > > > > The question is: Am I missing something or it is not implemented? >...