<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>VMpros &#187; vMotion</title>
	<atom:link href="http://blog.vmpros.nl/tag/vmotion/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.vmpros.nl</link>
	<description>It&#039;s all about virtualization...</description>
	<lastBuildDate>Mon, 06 Feb 2012 13:32:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>VMware: After upgrade to ESX 4.0 Host is incompatible with the virtual machine&#8217;s requirements</title>
		<link>http://blog.vmpros.nl/2009/07/28/vmware-after-upgrade-to-esx-4-0-host-is-incompatible-with-the-virtual-machines-requirements/#utm_source=feed&#038;utm_medium=feed&#038;utm_campaign=feed</link>
		<comments>http://blog.vmpros.nl/2009/07/28/vmware-after-upgrade-to-esx-4-0-host-is-incompatible-with-the-virtual-machines-requirements/#comments</comments>
		<pubDate>Tue, 28 Jul 2009 09:42:23 +0000</pubDate>
		<dc:creator>Daniel Buonocore</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[3.5]]></category>
		<category><![CDATA[4.0]]></category>
		<category><![CDATA[CPUID]]></category>
		<category><![CDATA[vMotion]]></category>
		<category><![CDATA[vSphere]]></category>

		<guid isPermaLink="false">http://blog.vmpros.nl/?p=1593</guid>
		<description><![CDATA[<br/>After we update ESX3.5 to ESX4.00 we noticed that some vms would not vmotion to a different host. Every time we tried we got the following error message. To solve this problem we changed the following settings 1. In the vSphere client select the vm that has the problem(the vm has to be powered off). [...]]]></description>
		<wfw:commentRss>http://blog.vmpros.nl/2009/07/28/vmware-after-upgrade-to-esx-4-0-host-is-incompatible-with-the-virtual-machines-requirements/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware: VMotion CPU Compatibility Requirements for Intel Processors (1991)</title>
		<link>http://blog.vmpros.nl/2009/06/08/vmware-vmotion-cpu-compatibility-requirements-for-intel-processors-1991/#utm_source=feed&#038;utm_medium=feed&#038;utm_campaign=feed</link>
		<comments>http://blog.vmpros.nl/2009/06/08/vmware-vmotion-cpu-compatibility-requirements-for-intel-processors-1991/#comments</comments>
		<pubDate>Mon, 08 Jun 2009 15:30:11 +0000</pubDate>
		<dc:creator>Daniel Buonocore</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[ESX]]></category>
		<category><![CDATA[ESXI]]></category>
		<category><![CDATA[EVC]]></category>
		<category><![CDATA[vCenter Server]]></category>
		<category><![CDATA[vMotion]]></category>

		<guid isPermaLink="false">http://blog.vmpros.nl/?p=1518</guid>
		<description><![CDATA[<br/>Why am I unable to migrate virtual machines with VMotion across Intel processors? In ESX 3.5 Update 2 and later, VMware recommends using Enhanced VMotion Compatibility (EVC) to eliminate many VMotion CPU compatibility problems. For more information on EVC, see KB 1003212. &#160; To ensure system stability during migration with VMotion, VirtualCenter and vCenter Server [...]]]></description>
		<wfw:commentRss>http://blog.vmpros.nl/2009/06/08/vmware-vmotion-cpu-compatibility-requirements-for-intel-processors-1991/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

