<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Alistar Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>Alistar Tracker</description>
    <pubDate>Tue, 21 Nov 2023 05:41:23 GMT</pubDate>
    <dc:date>2023-11-21T05:41:23Z</dc:date>
    <item>
      <title>Re: ESXI 5.5 - Share a local storage</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXI-5-5-Share-a-local-storage/m-p/494931#M41580</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you can mount the VMFS via NFS on a Unix/Linux system quite easily - for Windows, try this walkthrough at: &lt;A href="http://www.serverlab.ca/tutorials/windows/storage-file-systems/connect-windows-server-2012-r2-nfs-shares/" title="http://www.serverlab.ca/tutorials/windows/storage-file-systems/connect-windows-server-2012-r2-nfs-shares/"&gt;http://www.serverlab.ca/tutorials/windows/storage-file-systems/connect-windows-server-2012-r2-nfs-shares/&lt;/A&gt;‌ with the mountpoint being /vmfs/volumes/pt-092vh01_local/ connecting as a highest privileged user (try root at first to test it out)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 May 2016 15:56:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXI-5-5-Share-a-local-storage/m-p/494931#M41580</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2016-05-20T15:56:26Z</dc:date>
    </item>
    <item>
      <title>Re: Upgraded to ESXi 5.5 from 5.0</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Upgraded-to-ESXi-5-5-from-5-0/m-p/949017#M82598</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please try downloading your client version here: &lt;A href="https://kb.vmware.com/kb/2089791" title="https://kb.vmware.com/kb/2089791"&gt;VMware KB: Download URLs for VMware vSphere Client&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Mar 2016 07:49:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Upgraded-to-ESXi-5-5-from-5-0/m-p/949017#M82598</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2016-03-03T07:49:48Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with NVidia GRID K2 Card</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Problem-with-NVidia-GRID-K2-Card/m-p/935243#M80293</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hmm is your ESXi host up-to-date with the latest patches? Also, if the issue occurs again could you try posting ESXtop with expanded VM ('e' key, navigate to the VM and press enter) - maybe there is a world in the group which has some sort of resource leak which can cause locking up and misbehaving.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also /vmfs/volumes/&amp;lt;vmname&amp;gt;/vmware.log, vmkernel.log and vmkwarning.log from /var/log would be very helpful in the time of occurrence.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Dec 2015 08:58:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Problem-with-NVidia-GRID-K2-Card/m-p/935243#M80293</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2015-12-04T08:58:21Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with NVidia GRID K2 Card</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Problem-with-NVidia-GRID-K2-Card/m-p/935241#M80291</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;driver freezes happen most often with bad drivers for your GPU - is the driver version consistent across these two VMs? Have you tried making a clone of the 1st, nonproblematic VM (provided you customize it afterwards with let's say sysprep of course) and running some stresstests on the 2nd GPU?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Dec 2015 14:59:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Problem-with-NVidia-GRID-K2-Card/m-p/935241#M80291</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2015-12-03T14:59:07Z</dc:date>
    </item>
    <item>
      <title>Re: the system show my VM was running without any snapshots but there are multiple delta files in data stores.</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/the-system-show-my-VM-was-running-without-any-snapshots-but/m-p/2281331#M222569</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;for logging in to the web client, are you using &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://vcenter-hostname:9443" rel="nofollow"&gt;https://vcenter-hostname:9443&lt;/A&gt;&lt;SPAN&gt; ? Once I was entering &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://" rel="nofollow"&gt;http://&lt;/A&gt;&lt;SPAN&gt; instead of &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://" rel="nofollow"&gt;https://&lt;/A&gt;&lt;SPAN&gt; and nothing displayed for me. Can you capture a screenshot of this error for us? Also the newest "Thick" vSphere client should allow you to edit higher VM Versions.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Dec 2015 14:54:52 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/the-system-show-my-VM-was-running-without-any-snapshots-but/m-p/2281331#M222569</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2015-12-03T14:54:52Z</dc:date>
    </item>
    <item>
      <title>Re: Is it recommended to upgrade VMware Vsphere 5.5 to Vsphere 6 now?</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Is-it-recommended-to-upgrade-VMware-Vsphere-5-5-to-Vsphere-6-now/m-p/1787882#M20705</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the best thing you could do is to update your test&amp;amp;dev / pre-production environment to vSphere 6 if you have any provided that you check first all of your servers' components in the VMware's Hardware Compatibility List. This way you can find out what would work out and what wouldn't - it is important to test out features like that first before migrating everything at once and running into issues later.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also sometimes it is feasible to wait for Update 1 or Update 2 which would have many stability and performance fixes, etc. - it all depends on what support contract you have with VMware or if you are using a Free version where you'd troubleshoot issues on your own (or with the help of community forum) &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://communities.vmware.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Aug 2015 10:44:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Is-it-recommended-to-upgrade-VMware-Vsphere-5-5-to-Vsphere-6-now/m-p/1787882#M20705</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2015-08-05T10:44:54Z</dc:date>
    </item>
    <item>
      <title>Re: esxi 5.1 windows 7 serial passthrough</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/esxi-5-1-windows-7-serial-passthrough/m-p/986850#M89284</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;do you have serial port(s) enabled in your VM's BIOS? Sometimes these are turned off in virtualized environment to help save on resources because the overhead it incurs.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Aug 2015 07:01:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/esxi-5-1-windows-7-serial-passthrough/m-p/986850#M89284</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2015-08-05T07:01:00Z</dc:date>
    </item>
    <item>
      <title>Re: Seeing hard crashes, any known issues or troubleshooting for a Cisco USC-E blade?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Seeing-hard-crashes-any-known-issues-or-troubleshooting-for-a/m-p/451383#M37305</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi again,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;unfortunately I really can't see anything in the logs &lt;img id="smileysad" class="emoticon emoticon-smileysad" src="https://communities.vmware.com/i/smilies/16x16_smiley-sad.png" alt="Smiley Sad" title="Smiley Sad" /&gt; Anyways a BIOS upgrade is a great way to stabilize things, so fingers crossed here. Also, has anyone done a physical inspection of the hardware itself? We had one fellow on this forum in the past that had his server reset at random and eventually he found out that it was overheating - cleaning the internals helped.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You're welcome and hopefully the crashes will stop appearing! &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://communities.vmware.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Aug 2015 06:47:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Seeing-hard-crashes-any-known-issues-or-troubleshooting-for-a/m-p/451383#M37305</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2015-08-05T06:47:51Z</dc:date>
    </item>
    <item>
      <title>Re: Vmware for ProLiant ML310e Gen8</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Vmware-for-ProLiant-ML310e-Gen8/m-p/1310238#M119300</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it is best to pre-configure your raid before you make a datastore and place your VMs there - you can not expand a 1-disk "array" further. The least amount disks is 2 for RAID1, 3 for RAID5 and 4 for RAID10. You need to have some redundancy in a case of a disk failure (which will happen sooner or later). So I'd recommend getting at least one other disk, create a RAID array and start using it as a datastore.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Aug 2015 06:34:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Vmware-for-ProLiant-ML310e-Gen8/m-p/1310238#M119300</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2015-08-05T06:34:15Z</dc:date>
    </item>
    <item>
      <title>Re: VMware 5.x &amp; 512e HDD</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/VMware-5-x-512e-HDD/m-p/2262208#M220578</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ken,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;unfortunately I think that the 512e might really be an issue - when you are performing writes and your I/O requests get segmented (because of a misalignment) you get a performance deterioration - more so when it's "just" 7,2k RPM drives in RAID1 - could you try getting disk(s) with native 512 sector format, doing a storage vMotion there and compare the performance?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Aug 2015 06:30:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/VMware-5-x-512e-HDD/m-p/2262208#M220578</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2015-08-05T06:30:25Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 5.5 went in to not responding status on vCenter</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-5-5-went-in-to-not-responding-status-on-vCenter/m-p/451249#M37256</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;according to the message it seems someone might have played with the memory reservations for the ESXi services to "free up some memory" - particularly it seems snmpd daemon is affected. It can be found under the Thick client in Configuration -&amp;gt; Software -&amp;gt; System Resource Allocation -&amp;gt; Advanced -&amp;gt; and there try searching for "snmpd". If you do not use SNMP you can try to disable it with the use of this KB: &lt;A href="https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.privileges.doc_50%2FGUID-37EC4802-F974-4CCC-BC19-60A64BAB35B6.html" title="https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.privileges.doc_50%2FGUID-37EC4802-F974-4CCC-BC19-60A64BAB35B6.html"&gt;vSphere Documentation Center&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, it could be a bug in an ESXi version you are using - perhaps updating to the latest patch could help. Either that or your host is running out of memory pretty quick, but in that case it would start to swap out virtual memory to disk and not hanging.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you please post vmkernel.log and vmkwarning.log from /var/log that you can retrieve via WinSCP after connecting to the affected ESXi host?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Aug 2015 06:28:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-5-5-went-in-to-not-responding-status-on-vCenter/m-p/451249#M37256</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2015-08-05T06:28:27Z</dc:date>
    </item>
    <item>
      <title>Re: Vsphere 5.5 and Emulex OneConnect 10Gb NIC trouble</title>
      <link>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/Vsphere-5-5-and-Emulex-OneConnect-10Gb-NIC-trouble/m-p/417435#M688</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Emulex NICs are nothing but trouble - after fruitless calls between HP &amp;amp; Cisco we moved to Broadcomm for or new ESXi deployments and are happy ever since.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Aug 2015 06:14:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/Vsphere-5-5-and-Emulex-OneConnect-10Gb-NIC-trouble/m-p/417435#M688</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2015-08-05T06:14:26Z</dc:date>
    </item>
    <item>
      <title>Re: Seeing hard crashes, any known issues or troubleshooting for a Cisco USC-E blade?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Seeing-hard-crashes-any-known-issues-or-troubleshooting-for-a/m-p/451381#M37303</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we can gain more insight if you provide vmkernel.log and vmkwarning.log from /var/log - use WinSCP to connect to your ESXi host and gather these files from there. It is highly improbable that the ESXi is crashing solely because it is deployed on hard drives and not on SD cards because the whole hypervisor gets loaded into memory on boot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good luck!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Aug 2015 06:07:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Seeing-hard-crashes-any-known-issues-or-troubleshooting-for-a/m-p/451381#M37303</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2015-08-05T06:07:12Z</dc:date>
    </item>
    <item>
      <title>Re: VMWare hosted system with e1000e virtual NICs encounters a kernel panic within "e1000e_cyclecounter_read+0xa7/0xc0 [e1000e]"</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/VMWare-hosted-system-with-e1000e-virtual-NICs-encounters-a/m-p/450284#M37130</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Therefore this needs to be directed to VMware support so that they can inspect vmnic firmware / &lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;3.10.0-229.7.2.el7 &lt;/SPAN&gt;kernel incompatibility.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Aug 2015 06:02:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/VMWare-hosted-system-with-e1000e-virtual-NICs-encounters-a/m-p/450284#M37130</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2015-08-05T06:02:51Z</dc:date>
    </item>
    <item>
      <title>Re: host in cluster not the same build number</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/host-in-cluster-not-the-same-build-number/m-p/1784885#M173132</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The only exception is Disaster Recovery where your protected VMs must have the VMware Tools version consistent across the board.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Aug 2015 10:53:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/host-in-cluster-not-the-same-build-number/m-p/1784885#M173132</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2015-08-04T10:53:38Z</dc:date>
    </item>
    <item>
      <title>Re: esxi 5.5 sometimes slow performance on VM</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/esxi-5-5-sometimes-slow-performance-on-VM/m-p/2213263#M214872</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you checked the CPU Ready time while this was happening? It is possible that your CPU cores / NUMA nodes (if the vCPUs span across) were getting overcomitted.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Aug 2015 10:52:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/esxi-5-5-sometimes-slow-performance-on-VM/m-p/2213263#M214872</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2015-08-04T10:52:28Z</dc:date>
    </item>
    <item>
      <title>Re: VMWare hosted system with e1000e virtual NICs encounters a kernel panic within "e1000e_cyclecounter_read+0xa7/0xc0 [e1000e]"</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/VMWare-hosted-system-with-e1000e-virtual-NICs-encounters-a/m-p/450281#M37127</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Seems a new kernel has caused an incompatibility with the hypervisor, which is odd but happens nevertheless. Have you tried raising a support case with VMware? I think a bug report from this situation would help them avoid such issues in the future.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also have you tried swapping your virtual nic for vmxnet3 or just plain e1000 to see how that goes?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Aug 2015 10:43:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/VMWare-hosted-system-with-e1000e-virtual-NICs-encounters-a/m-p/450281#M37127</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2015-08-04T10:43:57Z</dc:date>
    </item>
    <item>
      <title>Re: CPU Ratio with Haswell</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/CPU-Ratio-with-Haswell/m-p/1313242#M119822</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Tom,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this all depends on the workload you are planning to introduce to your ESXi servers. Even then the answer needs to be refined further - will you need to cluster the ESXi hosts in order to have application dependency? (e.g. SQL Cluster &amp;amp; Generic Cluster). You will also need one or two ESXi hosts more in order to satisfy HA Failover so that your failed VMs can reboot on a host with enough capacity (governed by DRS).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So it all boils down how used are the application servers during peak times (business hours), how much frequency and vCPU they need, and if you can combine them with servers like DNS, AD, and further lightweight services. You need to talk to your app owners in terms of what they requires.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sizing an ESXi host for 4000vCores would mean you should be able to put 400VMs on a cluster. This large scale seems it would be used for VDI?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Aug 2015 10:42:03 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/CPU-Ratio-with-Haswell/m-p/1313242#M119822</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2015-08-04T10:42:03Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade vmware tools from 5.5 to 6.0 on AD Controllers</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Upgrade-vmware-tools-from-5-5-to-6-0-on-AD-Controllers/m-p/1296325#M116434</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this might be due to some patch that was installed recently to need a reboot before VMware Tools can be successfully installed, according to the line below:&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px; line-height: 1.5em;"&gt;2015-07-15 10:32:58| BootStrapper-build-2791197| Util_NeedReboot: Reboot required!&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px; line-height: 1.5em;"&gt;If not, the error's description states: "&lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;This is a generic installer error that could be due to not being able to overwrite previously installed components or being unable to load the drivers&lt;/SPAN&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px; line-height: 1.5em;"&gt;" - try running a cleanup for all leftover components of the old VMware Tools.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px; line-height: 1.5em;"&gt;Refer here for more info: &lt;A href="http://www.msigeek.com/715/how-to-troubleshoot-the-error-1603-fatal-error-during-installation" title="http://www.msigeek.com/715/how-to-troubleshoot-the-error-1603-fatal-error-during-installation"&gt;Troubleshoot the error 1603 “Fatal Error During Installation”&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px; line-height: 1.5em;"&gt;Good luck!&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Aug 2015 10:36:03 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Upgrade-vmware-tools-from-5-5-to-6-0-on-AD-Controllers/m-p/1296325#M116434</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2015-08-04T10:36:03Z</dc:date>
    </item>
    <item>
      <title>Re: After upgrade of Esxi 5.5 to 6.0 servers lock up every other day</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/After-upgrade-of-Esxi-5-5-to-6-0-servers-lock-up-every-other-day/m-p/1313461#M119895</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;can you please upload vmkernel.log and vmkwarning.log from /var/log? If you would point out what was the time that the host stopped responding so that we could correlate, we could gain some more insight into the issue &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://communities.vmware.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Aug 2015 10:26:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/After-upgrade-of-Esxi-5-5-to-6-0-servers-lock-up-every-other-day/m-p/1313461#M119895</guid>
      <dc:creator>Alistar</dc:creator>
      <dc:date>2015-08-04T10:26:20Z</dc:date>
    </item>
  </channel>
</rss>

