On Thu, 2013-09-05 at 11:58 +0200, Alexander Graf wrote: > > Yes. I do not really understand the problem here (and I am not > playing > > dump). Do you suggest sending just the guest timebase and do not > send the > > host timebase and the offset (one number instead of two)? I can do > that, > > makes sense, no problem, thanks for the idea. > > Yup, pretty much :). The receiving end should have no business in > knowing how far off the guest and the host timebase were skewed on the > sending end :).
Well, yes and no ... we'd like to account for the migration latency on the timebase or the guest view of real time will get skewed since it uses the TB to maintain it's clock. So assuming both hosts are reasonably synchronized with NTP, we want a correlation guest TB / TOD in order to properly make the adjustment on the target. This may not be what Alexey implemented but I think that's what Paulus and I asked for :-) Cheers, Ben.
