<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Virtual Machine clocksource issue</title>
	<atom:link href="http://blog.jolexa.net/2010/03/05/virtual-machine-clocksource-issue/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jolexa.net/2010/03/05/virtual-machine-clocksource-issue/</link>
	<description>Random thoughts and rants...mostly Linux</description>
	<lastBuildDate>Tue, 07 Feb 2012 16:46:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jeremy Olexa</title>
		<link>http://blog.jolexa.net/2010/03/05/virtual-machine-clocksource-issue/comment-page-1/#comment-1996</link>
		<dc:creator>Jeremy Olexa</dc:creator>
		<pubDate>Mon, 08 Mar 2010 16:23:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jolexa.net/?p=638#comment-1996</guid>
		<description>Spot on, it was modified after my ticket was submitted asking for help. :)</description>
		<content:encoded><![CDATA[<p>Spot on, it was modified after my ticket was submitted asking for help. <img src='http://blog.jolexa.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://blog.jolexa.net/2010/03/05/virtual-machine-clocksource-issue/comment-page-1/#comment-1982</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Sat, 06 Mar 2010 20:09:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jolexa.net/?p=638#comment-1982</guid>
		<description>Hi,

Thanks for mentioning this! You can also see our recommendations on http://www.vr.org/support/index.php?action=kb&amp;article=38 regarding time drift. It looks like you discovered changing the default clocksource on your own.

Thanks!</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Thanks for mentioning this! You can also see our recommendations on <a href="http://www.vr.org/support/index.php?action=kb&#038;article=38" rel="nofollow">http://www.vr.org/support/index.php?action=kb&#038;article=38</a> regarding time drift. It looks like you discovered changing the default clocksource on your own.</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eliasp</title>
		<link>http://blog.jolexa.net/2010/03/05/virtual-machine-clocksource-issue/comment-page-1/#comment-1968</link>
		<dc:creator>eliasp</dc:creator>
		<pubDate>Fri, 05 Mar 2010 20:10:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jolexa.net/?p=638#comment-1968</guid>
		<description>Timekeeping in virtual systems is a really tricky topic.
A really great document with a lot of details &amp; background information about why common timesyncing methods often just don&#039;t work or make the issue even worse in VM is the VMware Timekeeping guide - IMHO an absolutely recommended read - not only for VMware users: http://www.vmware.com/pdf/vmware_timekeeping.pdf

Regards, Elias P.</description>
		<content:encoded><![CDATA[<p>Timekeeping in virtual systems is a really tricky topic.<br />
A really great document with a lot of details &amp; background information about why common timesyncing methods often just don&#8217;t work or make the issue even worse in VM is the VMware Timekeeping guide &#8211; IMHO an absolutely recommended read &#8211; not only for VMware users: <a href="http://www.vmware.com/pdf/vmware_timekeeping.pdf" rel="nofollow">http://www.vmware.com/pdf/vmware_timekeeping.pdf</a></p>
<p>Regards, Elias P.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

