<div class="gmail_quote">On Tue, Aug 11, 2009 at 10:21 AM, Benjamin M. Schwartz <span dir="ltr"><<a href="mailto:bmschwar@fas.harvard.edu">bmschwar@fas.harvard.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div class="im">Christoph Derndorfer wrote:<br> > * there seems to be quite an issue with syncing collaboration because<br> > initially the activities on both virtual machines were off by maybe half a<br> > second or so but after leaving them running for 10 minutes the difference<br> > had increased to more than 6 seconds.<br> <br> </div>Hmm...<br> <br> Virtual machines have notoriously unstable system clocks, which is<br> probably why you observed this. 狢'll have to think about what to do about it.</blockquote><div><br></div><div>I'm also seeing this issue when collaborating between a VirtualBox instance (with SoaS Strawberry) and an XO (running 802). Though do note that both on this and the VM & VM setup I was connected via <a href="http://jabber.sugarlabs.org">jabber.sugarlabs.org</a> so this might introduce some latency as well (thanks to Daniel for pointing this out to me).</div> <div><br></div><div>Now with two XOs, one of them running Nepal's custom NEXO build, the other one on 802, connected via the Mesh the difference between the two machines seems to be ~1 second. I'll leave them running for a bit to see whether it stays that way or increases.</div> <div><br></div><div>Christoph</div></div><br>-- <br>Christoph Derndorfer<br>co-editor, olpcnews<br>url: <a href="http://www.olpcnews.com">www.olpcnews.com</a><br>e-mail: <a href="mailto:christoph@olpcnews.com">christoph@olpcnews.com</a><br>