On Thu, Apr 23, 2015 at 11:18:08AM +0200, Jiri Denemark wrote:
virDomainGetJobStats is able to report statistics of a completed
migration, however to get usable downtime and total time statistics both
hosts have to keep synchronized time. To provide at least some
estimation of the times even
On Mon, Apr 27, 2015 at 09:31:30 +0200, Martin Kletzander wrote:
On Thu, Apr 23, 2015 at 11:18:08AM +0200, Jiri Denemark wrote:
virDomainGetJobStats is able to report statistics of a completed
migration, however to get usable downtime and total time statistics both
hosts have to keep
On 23.04.2015 15:25, Jiri Denemark wrote:
On Thu, Apr 23, 2015 at 11:40:11 +0200, Michal Privoznik wrote:
On 23.04.2015 11:18, Jiri Denemark wrote:
virDomainGetJobStats is able to report statistics of a completed
migration, however to get usable downtime and total time statistics both
hosts
On Fri, Apr 24, 2015 at 11:53:46 +0200, Michal Privoznik wrote:
On 23.04.2015 15:25, Jiri Denemark wrote:
On Thu, Apr 23, 2015 at 11:40:11 +0200, Michal Privoznik wrote:
On 23.04.2015 11:18, Jiri Denemark wrote:
virDomainGetJobStats is able to report statistics of a completed
migration,
virDomainGetJobStats is able to report statistics of a completed
migration, however to get usable downtime and total time statistics both
hosts have to keep synchronized time. To provide at least some
estimation of the times even when NTP daemons are not running on both
hosts we can just ignore
On 23.04.2015 11:18, Jiri Denemark wrote:
virDomainGetJobStats is able to report statistics of a completed
migration, however to get usable downtime and total time statistics both
hosts have to keep synchronized time. To provide at least some
estimation of the times even when NTP daemons are
On Thu, Apr 23, 2015 at 11:40:11 +0200, Michal Privoznik wrote:
On 23.04.2015 11:18, Jiri Denemark wrote:
virDomainGetJobStats is able to report statistics of a completed
migration, however to get usable downtime and total time statistics both
hosts have to keep synchronized time. To
