<?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: Capabilities of vSphere VMs Using Hardware Version 7</title>
	<atom:link href="http://vmetc.com/2009/06/17/capabilities-of-vsphere-vms-using-hardware-version-7/feed/" rel="self" type="application/rss+xml" />
	<link>http://vmetc.com/2009/06/17/capabilities-of-vsphere-vms-using-hardware-version-7/</link>
	<description>Go Green with Virtualization. Go UGLY Green with vmetc.com.</description>
	<lastBuildDate>Tue, 17 Apr 2012 03:50:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: T. Davis</title>
		<link>http://vmetc.com/2009/06/17/capabilities-of-vsphere-vms-using-hardware-version-7/comment-page-1/#comment-4306</link>
		<dc:creator>T. Davis</dc:creator>
		<pubDate>Wed, 14 Apr 2010 19:10:34 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=4085#comment-4306</guid>
		<description>Can you recheck this information posted, it appears that Serial Attached SCSI (SAS) virtual device for Microsfot Cluster Service, IDE virtual device and VMXNET Gen 3 require HW v7, not the other items.  Teh other items are not indented under Hw v7.</description>
		<content:encoded><![CDATA[<p>Can you recheck this information posted, it appears that Serial Attached SCSI (SAS) virtual device for Microsfot Cluster Service, IDE virtual device and VMXNET Gen 3 require HW v7, not the other items.  Teh other items are not indented under Hw v7.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anton Zhbankov</title>
		<link>http://vmetc.com/2009/06/17/capabilities-of-vsphere-vms-using-hardware-version-7/comment-page-1/#comment-3686</link>
		<dc:creator>Anton Zhbankov</dc:creator>
		<pubDate>Thu, 18 Jun 2009 16:52:25 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=4085#comment-3686</guid>
		<description>Hot-extending VMDKs are not ver.7 feature, I used them with 3.5.</description>
		<content:encoded><![CDATA[<p>Hot-extending VMDKs are not ver.7 feature, I used them with 3.5.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anton Zhbankov</title>
		<link>http://vmetc.com/2009/06/17/capabilities-of-vsphere-vms-using-hardware-version-7/comment-page-1/#comment-2666</link>
		<dc:creator>Anton Zhbankov</dc:creator>
		<pubDate>Thu, 18 Jun 2009 10:52:25 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=4085#comment-2666</guid>
		<description>Hot-extending VMDKs are not ver.7 feature, I used them with 3.5.</description>
		<content:encoded><![CDATA[<p>Hot-extending VMDKs are not ver.7 feature, I used them with 3.5.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: T@T</title>
		<link>http://vmetc.com/2009/06/17/capabilities-of-vsphere-vms-using-hardware-version-7/comment-page-1/#comment-2664</link>
		<dc:creator>T@T</dc:creator>
		<pubDate>Wed, 17 Jun 2009 18:53:30 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=4085#comment-2664</guid>
		<description>Is there any way to add sound card device to VM version 7?</description>
		<content:encoded><![CDATA[<p>Is there any way to add sound card device to VM version 7?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Boche</title>
		<link>http://vmetc.com/2009/06/17/capabilities-of-vsphere-vms-using-hardware-version-7/comment-page-1/#comment-2663</link>
		<dc:creator>Jason Boche</dc:creator>
		<pubDate>Wed, 17 Jun 2009 17:37:04 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=4085#comment-2663</guid>
		<description>Yes, that is correct, however, for the protection of those with 1MB block sizes (and there are a lot of them in the world), VMware has chosen a &quot;one size fits all&quot; solution. It&#039;s a &quot;If I can&#039;t have a 256GB VM, then nobody can&quot; type scenario.  Doesn&#039;t make it right but scaling memory limits on VMFS block sizes might get difficult from a support standpoint.</description>
		<content:encoded><![CDATA[<p>Yes, that is correct, however, for the protection of those with 1MB block sizes (and there are a lot of them in the world), VMware has chosen a &#8220;one size fits all&#8221; solution. It&#39;s a &#8220;If I can&#39;t have a 256GB VM, then nobody can&#8221; type scenario.  Doesn&#39;t make it right but scaling memory limits on VMFS block sizes might get difficult from a support standpoint.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rbrambley</title>
		<link>http://vmetc.com/2009/06/17/capabilities-of-vsphere-vms-using-hardware-version-7/comment-page-1/#comment-2662</link>
		<dc:creator>rbrambley</dc:creator>
		<pubDate>Wed, 17 Jun 2009 17:23:28 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=4085#comment-2662</guid>
		<description>All,&lt;br&gt;&lt;br&gt;Thanks for the comments and explanations. I&#039;m still confused by the&lt;br&gt;answer to Dracolith&#039;s question  about a 2MB Block size VMFS volume.&lt;br&gt;&lt;br&gt;2MB block size means a file greater than 256 GB is allowed on the VMFS&lt;br&gt; which would allow a 256 GB VMkernel swap file. Right?</description>
		<content:encoded><![CDATA[<p>All,</p>
<p>Thanks for the comments and explanations. I&#39;m still confused by the<br />answer to Dracolith&#39;s question  about a 2MB Block size VMFS volume.</p>
<p>2MB block size means a file greater than 256 GB is allowed on the VMFS<br /> which would allow a 256 GB VMkernel swap file. Right?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Boche</title>
		<link>http://vmetc.com/2009/06/17/capabilities-of-vsphere-vms-using-hardware-version-7/comment-page-1/#comment-2661</link>
		<dc:creator>Jason Boche</dc:creator>
		<pubDate>Wed, 17 Jun 2009 16:57:53 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=4085#comment-2661</guid>
		<description>The limit is 255GB for any configuration.  The sole reason is so that 256GB RAM VMs residing on a 1MB block size VMFS could require (if no reservation is set) a 256GB VMkernel swap file, plus a small amount of overhead for the VM.  This would exceed the 256GB limitation of a 1MB block size VMFS volume.  For this reason, VMware pushed the RAM limit to 255GB so the max file space that could be used is 255GB plus a small chunk for overhead which comes out under the 256GB limit of a 1MB block size.</description>
		<content:encoded><![CDATA[<p>The limit is 255GB for any configuration.  The sole reason is so that 256GB RAM VMs residing on a 1MB block size VMFS could require (if no reservation is set) a 256GB VMkernel swap file, plus a small amount of overhead for the VM.  This would exceed the 256GB limitation of a 1MB block size VMFS volume.  For this reason, VMware pushed the RAM limit to 255GB so the max file space that could be used is 255GB plus a small chunk for overhead which comes out under the 256GB limit of a 1MB block size.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dracolith</title>
		<link>http://vmetc.com/2009/06/17/capabilities-of-vsphere-vms-using-hardware-version-7/comment-page-1/#comment-2660</link>
		<dc:creator>Dracolith</dc:creator>
		<pubDate>Wed, 17 Jun 2009 16:45:52 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=4085#comment-2660</guid>
		<description>Is the limit still 255GB  (and not 256) if I format the VMFS filesystem using a 2MB block size?&lt;br&gt;&lt;br&gt;Or if I use NFS with a backend FS that can handle large files,  or I set a high memory reservation on the VM to avoid making a 256mb swapfile...</description>
		<content:encoded><![CDATA[<p>Is the limit still 255GB  (and not 256) if I format the VMFS filesystem using a 2MB block size?</p>
<p>Or if I use NFS with a backend FS that can handle large files,  or I set a high memory reservation on the VM to avoid making a 256mb swapfile&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

