<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: VMware: BUG in ESX 3.5 Update 2</title>
	<atom:link href="http://ict-freak.nl/2008/08/12/bug-in-esx-35-update-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://ict-freak.nl/2008/08/12/bug-in-esx-35-update-2/</link>
	<description>VMware, Linux, Scripting...</description>
	<lastBuildDate>Thu, 02 Feb 2012 13:00:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Gilson Soares</title>
		<link>http://ict-freak.nl/2008/08/12/bug-in-esx-35-update-2/comment-page-1/#comment-9013</link>
		<dc:creator><![CDATA[Gilson Soares]]></dc:creator>
		<pubDate>Wed, 13 Aug 2008 03:40:25 +0000</pubDate>
		<guid isPermaLink="false">http://ictfreak.wordpress.com/2008/08/12/bug-in-esx-35-update-2/#comment-9013</guid>
		<description><![CDATA[Patch Available:

http://kb.vmware.com/selfservice/dynamickc.do?externalId=1006721&amp;sliceId=1&amp;command=show&amp;forward=nonthreadedKC&amp;kcId=1006721

-Gilson Soares]]></description>
		<content:encoded><![CDATA[<p>Patch Available:</p>
<p><a href="http://kb.vmware.com/selfservice/dynamickc.do?externalId=1006721&#038;sliceId=1&#038;command=show&#038;forward=nonthreadedKC&#038;kcId=1006721" rel="nofollow">http://kb.vmware.com/selfservice/dynamickc.do?externalId=1006721&#038;sliceId=1&#038;command=show&#038;forward=nonthreadedKC&#038;kcId=1006721</a></p>
<p>-Gilson Soares</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Top Posts &#171; WordPress.com</title>
		<link>http://ict-freak.nl/2008/08/12/bug-in-esx-35-update-2/comment-page-1/#comment-9011</link>
		<dc:creator><![CDATA[Top Posts &#171; WordPress.com]]></dc:creator>
		<pubDate>Wed, 13 Aug 2008 00:06:52 +0000</pubDate>
		<guid isPermaLink="false">http://ictfreak.wordpress.com/2008/08/12/bug-in-esx-35-update-2/#comment-9011</guid>
		<description><![CDATA[[...]  VMware: BUG in ESX 3.5 Update 2 [image] De Bug: Starting this morning, we could not power on nor VMotion any of our Virtual Machines. The VI Client [...] [...]]]></description>
		<content:encoded><![CDATA[<p>[...]  VMware: BUG in ESX 3.5 Update 2 [image] De Bug: Starting this morning, we could not power on nor VMotion any of our Virtual Machines. The VI Client [...] [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Update 1: BUG in ESX 3.5 Update 2 &#171; ICT-Freak</title>
		<link>http://ict-freak.nl/2008/08/12/bug-in-esx-35-update-2/comment-page-1/#comment-9007</link>
		<dc:creator><![CDATA[Update 1: BUG in ESX 3.5 Update 2 &#171; ICT-Freak]]></dc:creator>
		<pubDate>Tue, 12 Aug 2008 19:57:50 +0000</pubDate>
		<guid isPermaLink="false">http://ictfreak.wordpress.com/2008/08/12/bug-in-esx-35-update-2/#comment-9007</guid>
		<description><![CDATA[[...] Post 1: [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Post 1: [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

