Seems the bwidth calculation is the problem. The code simply does: bwidth = (bytes_transferred - bytes_transferred_last) / timediff but I assume network traffic is buffered, so calculated bwidth is sometimes much too high. - Dietmar > -----Original Message----- > From: kvm-owner@xxxxxxxxxxxxxxx [mailto:kvm-owner@xxxxxxxxxxxxxxx] On > Behalf Of Dietmar Maurer > Sent: Dienstag, 29. September 2009 15:01 > To: kvm > Subject: migrate_set_downtime bug > > using 0.11.0, live migration works as expected, but max downtime does > not seem to work, for example: > > # migrate_set_downtime 1 > > After that tcp migration has much longer downtimes (up to 20 seconds). > > Also, it seems that the 'monitor' is locked (take up to 10 seconds > until I get a monitor prompt). > > Someone else get this behavior? > > - Dietmar > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
