<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Performance &amp; VMmark : VMkernel Scheduler : Comments</title>
    <link>http://communities.vmware.com/docs/DOC-5501#comments</link>
    <description>Comments on : VMkernel Scheduler</description>
    <language>en</language>
    <pubDate>Thu, 30 Oct 2008 04:36:12 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-10-30T04:36:12Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>RE: VMkernel Scheduler</title>
      <link>http://communities.vmware.com/docs/DOC-5501#comments-9357</link>
      <description>Scott,&lt;br /&gt;
&lt;br /&gt;
Thanks for this document. I think it will be very helpful over time. Keep up the good work!&lt;br /&gt;
&lt;br /&gt;
KLC&lt;br /&gt;
Ken Cline&lt;br /&gt;
Technical Director, Virtualization&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.wellslanders.com"&gt;Wells Landers&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.tvarsolutions.com"&gt;TVAR Solutions, A Wells Landers Group Company&lt;/a&gt;&lt;br /&gt;
VMware Communities User Moderator</description>
      <pubDate>Thu, 30 Oct 2008 04:36:12 GMT</pubDate>
      <author>Ken.Cline</author>
      <guid>http://communities.vmware.com/docs/DOC-5501#comments-9357</guid>
      <dc:date>2008-10-30T04:36:12Z</dc:date>
      <clearspace:dateToText>1 year, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: VMkernel Scheduler</title>
      <link>http://communities.vmware.com/docs/DOC-5501#comments-11572</link>
      <description>Hi Scott,&lt;br /&gt;
&lt;br /&gt;
Can you please update this docnote to explain how the cell system works in ESX4?&lt;br /&gt;
&lt;br /&gt;
Also this OFFICIAL VMWARE document, &lt;a class="jive-link-external" href="http://www.vmware.com/pdf/tips_tricks_infrastructure_services.pdf,"&gt;http://www.vmware.com/pdf/tips_tricks_infrastructure_services.pdf,&lt;/a&gt; on Page 4, states that there are 1820 ways of scheduling a 4 vCPU workload on a 16 core ESX3 system, can you please confirm that this is patently incorrect.&lt;br /&gt;
&lt;br /&gt;
Regards,&lt;br /&gt;
Alex</description>
      <pubDate>Tue, 23 Jun 2009 10:42:20 GMT</pubDate>
      <author>alex0</author>
      <guid>http://communities.vmware.com/docs/DOC-5501#comments-11572</guid>
      <dc:date>2009-06-23T10:42:20Z</dc:date>
      <clearspace:dateToText>5 months, 6 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: VMkernel Scheduler</title>
      <link>http://communities.vmware.com/docs/DOC-5501#comments-11620</link>
      <description>The count of 1820 possibilities considers individual vCPU mappings to specific cores.  This means that a system with only two cores has two ways to place a 2-way VM.  But there is no performance difference in these two positions so I eliminate the second choice, which flips the vCPU to CPU mapping.  I think that both documents are correct.&lt;br /&gt;
&lt;br /&gt;
I'll update this document for ESX 4 once we release our vSphere scheduler document.  In short, there is no longer a cell with VMware vSphere.&lt;br /&gt;
&lt;br /&gt;
Scott&lt;br /&gt;
&lt;p /&gt;
More information on my communities blog and on Twitter:&lt;br /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/blogs/drummonds"&gt;http://communities.vmware.com/blogs/drummonds&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://twitter.com/drummonds1974"&gt;http://twitter.com/drummonds1974&lt;/a&gt;</description>
      <pubDate>Thu, 25 Jun 2009 10:39:10 GMT</pubDate>
      <author>drummonds</author>
      <guid>http://communities.vmware.com/docs/DOC-5501#comments-11620</guid>
      <dc:date>2009-06-25T10:39:10Z</dc:date>
      <clearspace:dateToText>5 months, 4 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: VMkernel Scheduler</title>
      <link>http://communities.vmware.com/docs/DOC-5501#comments-11678</link>
      <description>Hi Scott,&lt;br /&gt;
&lt;br /&gt;
Do you have an ETA on the vSphere scheduler document?  Something definitive that shows the benefits of vSphere would be very much appreciated.&lt;br /&gt;
&lt;br /&gt;
Many thanks,&lt;br /&gt;
&lt;br /&gt;
Kevin</description>
      <pubDate>Tue, 07 Jul 2009 09:01:48 GMT</pubDate>
      <author>thinks2much2</author>
      <guid>http://communities.vmware.com/docs/DOC-5501#comments-11678</guid>
      <dc:date>2009-07-07T09:01:48Z</dc:date>
      <clearspace:dateToText>4 months, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: VMkernel Scheduler</title>
      <link>http://communities.vmware.com/docs/DOC-5501#comments-11728</link>
      <description>Two weeks.&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
More information on my communities blog and on Twitter:&lt;br /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/blogs/drummonds"&gt;http://communities.vmware.com/blogs/drummonds&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://twitter.com/drummonds1974"&gt;http://twitter.com/drummonds1974&lt;/a&gt;</description>
      <pubDate>Tue, 07 Jul 2009 16:33:10 GMT</pubDate>
      <author>drummonds</author>
      <guid>http://communities.vmware.com/docs/DOC-5501#comments-11728</guid>
      <dc:date>2009-07-07T16:33:10Z</dc:date>
      <clearspace:dateToText>4 months, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: VMkernel Scheduler</title>
      <link>http://communities.vmware.com/docs/DOC-5501#comments-11868</link>
      <description>Where to get information of how VMKernel works if VM  are assigned of more resources than one physical ESX has? For example cluster is 2 ESX each 2ghz quad core and you reserve 10 ghz for VM in a cluster.</description>
      <pubDate>Fri, 31 Jul 2009 11:04:59 GMT</pubDate>
      <author>aurimask</author>
      <guid>http://communities.vmware.com/docs/DOC-5501#comments-11868</guid>
      <dc:date>2009-07-31T11:04:59Z</dc:date>
      <clearspace:dateToText>3 months, 4 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: VMkernel Scheduler</title>
      <link>http://communities.vmware.com/docs/DOC-5501#comments-11880</link>
      <description>A virtual machine can only use 100% of the number of vCPUs provided to it.  Increasing limits above this number--if this is even possible--would not provide a performance gain.&lt;br /&gt;
&lt;br /&gt;
Scott&lt;br /&gt;
&lt;p /&gt;
More information on my communities blog and on Twitter:&lt;br /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/blogs/drummonds"&gt;http://communities.vmware.com/blogs/drummonds&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://twitter.com/drummonds"&gt;http://twitter.com/drummonds&lt;/a&gt;</description>
      <pubDate>Fri, 31 Jul 2009 16:08:59 GMT</pubDate>
      <author>drummonds</author>
      <guid>http://communities.vmware.com/docs/DOC-5501#comments-11880</guid>
      <dc:date>2009-07-31T16:08:59Z</dc:date>
      <clearspace:dateToText>3 months, 4 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>RE: VMkernel Scheduler</title>
      <link>http://communities.vmware.com/docs/DOC-5501#comments-11852</link>
      <description>So it is not possible for virtual machine have more cpu resources than physical ESX server on which VM is residing has?</description>
      <pubDate>Fri, 31 Jul 2009 19:06:44 GMT</pubDate>
      <author>aurimask</author>
      <guid>http://communities.vmware.com/docs/DOC-5501#comments-11852</guid>
      <dc:date>2009-07-31T19:06:44Z</dc:date>
      <clearspace:dateToText>3 months, 4 weeks ago</clearspace:dateToText>
    </item>
  </channel>
</rss>

