<?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>GaelV Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>GaelV Tracker</description>
    <pubDate>Tue, 21 Nov 2023 10:25:38 GMT</pubDate>
    <dc:date>2023-11-21T10:25:38Z</dc:date>
    <item>
      <title>Re: Physical RDM broken after 7U3 update</title>
      <link>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/Physical-RDM-broken-after-7U3-update/m-p/2878714#M6893</link>
      <description>&lt;P&gt;I got a "solution" and an answer from VMware support.&lt;/P&gt;&lt;P&gt;They advised to not install the last ESXi version but the second to last.&lt;/P&gt;&lt;P&gt;In my case i roll back to 7.0.1 (cause i had a config backup) then upgrade to 7.0.2 and i don't have any issues.&lt;/P&gt;&lt;P&gt;According VMWare, they're working on a new patch to fix the current issue but there's no release date at the moment.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Nov 2021 07:01:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/Physical-RDM-broken-after-7U3-update/m-p/2878714#M6893</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2021-11-18T07:01:41Z</dc:date>
    </item>
    <item>
      <title>Re: how upgrade to ESXI 7.0.3</title>
      <link>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/how-upgrade-to-ESXI-7-0-3/m-p/2876308#M6879</link>
      <description>&lt;P&gt;Hi, if you have VM with RDM disks be very careful, the 7.0.3 fails any vMotion with RDM disks (i'm in that case since this morning)&lt;/P&gt;&lt;P&gt;=&amp;gt;&amp;nbsp;&lt;A href="https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/Physical-RDM-broken-after-7U3-update/m-p/2876291/highlight/false#M6876" target="_blank"&gt;https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/Physical-RDM-broken-after-7U3-update/m-p/2876291/highlight/false#M6876&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Nov 2021 14:45:03 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/how-upgrade-to-ESXI-7-0-3/m-p/2876308#M6879</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2021-11-04T14:45:03Z</dc:date>
    </item>
    <item>
      <title>Re: Physical RDM broken after 7U3 update</title>
      <link>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/Physical-RDM-broken-after-7U3-update/m-p/2876306#M6878</link>
      <description>&lt;P&gt;I exactly got the same issue since this morning after migration from 7.0.1 build&amp;nbsp;&lt;SPAN&gt;17325551&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;to 7.0.3 build&amp;nbsp;&lt;SPAN&gt;18825058.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Any VM with RDM shared disks failed to migrate to another host. I opened an incident at our VMWare support but they seems to not be aware yet.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Nov 2021 14:42:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Hypervisor-Discussions/Physical-RDM-broken-after-7U3-update/m-p/2876306#M6878</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2021-11-04T14:42:48Z</dc:date>
    </item>
    <item>
      <title>Re: Vsphere 6.7 problems on installation</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Vsphere-6-7-problems-on-installation/m-p/2215083#M25745</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did you use the last Service Pack for ProLiant (Gen8 and after) iso to update all firmware/drivers of your server's devices ? Maybe it can improves the behaviour with ESXi 6.7&lt;/P&gt;&lt;P&gt;I recently had issues with new ProLiant Gen10 and ESXi 6.7 and the Service Pack resolved some stuffs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Be careful to download the Service Pack for Pre Gen 8 if you have Gen 8 or less, or Gen9plus if you have Gen 9 or Gen 10.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here's the link for the latest SPP for Gen 9Plus version : &lt;A href="http://h17007.www1.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx" title="http://h17007.www1.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx"&gt;Service Pack for ProLiant | Hewlett Packard Enterprise&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Here's the link for the Gen8 version : &lt;A href="http://h17007.www1.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx?version=Gen8.1" title="http://h17007.www1.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx?version=Gen8.1"&gt;Service Pack for ProLiant | Hewlett Packard Enterprise&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Aug 2019 11:29:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/Vsphere-6-7-problems-on-installation/m-p/2215083#M25745</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2019-08-20T11:29:17Z</dc:date>
    </item>
    <item>
      <title>Re: unable to upgrade esxi 5.1</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/unable-to-upgrade-esxi-5-1/m-p/494072#M6237</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;To be sure of what you're doing when you want to upgrade, check if your material, devices are compliant with the ESXi version wanted on the below site :&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.vmware.com/resources/compatibility/search.php" title="https://www.vmware.com/resources/compatibility/search.php"&gt;VMware Compatibility Guide - System Search&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If it's not supported (in your case you have a warning about your CPU) , it could have a lot of misfunction thereafter...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;About licences, you can ask evaluation licence for a while then only buy it to a reseller. I don't think you can cumulate evaluations licences&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Aug 2019 08:03:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/unable-to-upgrade-esxi-5-1/m-p/494072#M6237</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2019-08-20T08:03:58Z</dc:date>
    </item>
    <item>
      <title>Re: Export Esxi information</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Export-Esxi-information/m-p/493008#M14751</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can try this, the display is not very good but you got all the information :&lt;/P&gt;&lt;P&gt;You have to write your cluster or * in the $esx line&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;$esx = Get-Cluster "YourCluster or * " | Get-VMHost&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;foreach ($esx in $esxHosts) {&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; $esx | Select Name,ProcessorType,NumCpu,MemoryTotalGB,Version,Build&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; $esx | Get-View | Select @{N="Uptime"; E={(Get-Date) - $_.Summary.Runtime.BootTime}}| fl&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; $esx | Select @{Name="NTPServers"; Expression = {($esx | Get-VMHostNTPServer)} } | fl&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; $esx | Get-VMHostNetwork | Select DnsAddress | fl &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; $esx | Get-VMHostHardware | Select BiosVersion | fl&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;}&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It only misses&amp;nbsp;&amp;nbsp; ID CPU and&amp;nbsp;&amp;nbsp; Bios Date, i'm working on this..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Aug 2019 08:32:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Export-Esxi-information/m-p/493008#M14751</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2019-08-19T08:32:36Z</dc:date>
    </item>
    <item>
      <title>Re: Export Esxi information</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Export-Esxi-information/m-p/493006#M14749</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Most of the informations you need can be provided by the software RVTools (you can export in a .csv /excel file any informations)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here's the link&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.robware.net/rvtools/download/" title="https://www.robware.net/rvtools/download/"&gt;https://www.robware.net/rvtools/download/&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Aug 2019 07:36:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Export-Esxi-information/m-p/493006#M14749</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2019-08-19T07:36:30Z</dc:date>
    </item>
    <item>
      <title>Re: /vmfs/volumes # esxcli storage vmfs unmap -l  UNITY027_SSD_20TB  ERROR</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vmfs-volumes-esxcli-storage-vmfs-unmap-l-UNITY027-SSD-20TB-ERROR/m-p/1861877#M182297</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't think you'll be able to monitor it only with esxcli command...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Someone succeed to automate it using PowerCLI , you can monitor the action using PowerCLI so :&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.enterprisedaddy.com/2017/03/perform-vmfs-unmap-using-powercli/" title="http://www.enterprisedaddy.com/2017/03/perform-vmfs-unmap-using-powercli/"&gt;http://www.enterprisedaddy.com/2017/03/perform-vmfs-unmap-using-powercli/&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Else, take a look at the step 7 in this link, &lt;A href="https://blogs.vmware.com/vsphere/2012/04/vaai-thin-provisioning-block-reclaimunmap-in-action.html" title="https://blogs.vmware.com/vsphere/2012/04/vaai-thin-provisioning-block-reclaimunmap-in-action.html"&gt;VAAI Thin Provisioning Block Reclaim/UNMAP In Action - VMware vSphere Blog&lt;/A&gt; &lt;/P&gt;&lt;P&gt;It explain you how you can "monitor" the process via ESXTOP command (you can see the quantity of MB deleted)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But i didn't find any tools or cli to monitor the action as you can monitor the progress of anything in vCenter, sorry..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Aug 2019 13:42:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vmfs-volumes-esxcli-storage-vmfs-unmap-l-UNITY027-SSD-20TB-ERROR/m-p/1861877#M182297</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2019-08-14T13:42:21Z</dc:date>
    </item>
    <item>
      <title>Re: VM Deployment with OS Customization Specification</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/VM-Deployment-with-OS-Customization-Specification/m-p/1854186#M21903</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Alessandro,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just did the tutorial on the link you posted, but still got an issue :&lt;/P&gt;&lt;P&gt;My win2016 template got only 1 nic, my OSCustomizationNicMapping one too, but when I want to deploy my VM it ends at 97% with this error&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_0.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/13125iEB2991DC624C1695/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_0.png" alt="pastedImage_0.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Any idea ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Aug 2019 13:28:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/VM-Deployment-with-OS-Customization-Specification/m-p/1854186#M21903</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2019-08-14T13:28:31Z</dc:date>
    </item>
    <item>
      <title>Re: /vmfs/volumes # esxcli storage vmfs unmap -l  UNITY027_SSD_20TB  ERROR</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vmfs-volumes-esxcli-storage-vmfs-unmap-l-UNITY027-SSD-20TB-ERROR/m-p/1861875#M182295</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think you should check those 2 links about lockfiles :&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/1008728?other.KM_Utility.getArticleMetadata=2&amp;amp;CoveoV2.ContentHandler.getLoader=1&amp;amp;other.KM_Utility.getUser=1&amp;amp;other.KM_Utility.getAllTranslatedLanguages=2&amp;amp;other.KM_Utility.getContentdocument=1&amp;amp;ui-comm-runtime-components-aura-components-siteforce-qb.Quarterback.validateRoute=1&amp;amp;other.KM_Utility.getViewCount=1&amp;amp;r=1&amp;amp;other.KM_Utility.getKnowDetails=1&amp;amp;ui-communities-components-aura-components-forceCommunity-seoAssistant.SeoAssistant.getSeoData=1&amp;amp;CoveoV2.EndpointHandler.getEndpoint=1&amp;amp;other.KM_Utility.getUrl=1&amp;amp;other.KM_Utility.getPRNumberLinks=1&amp;amp;other.KM_Utility.getCaseLike=1" title="https://kb.vmware.com/s/article/1008728?other.KM_Utility.getArticleMetadata=2&amp;amp;CoveoV2.ContentHandler.getLoader=1&amp;amp;other.KM_Utility.getUser=1&amp;amp;other.KM_Utility.getAllTranslatedLanguages=2&amp;amp;other.KM_Utility.getContentdocument=1&amp;amp;ui-comm-runtime-components-aura-components-siteforce-qb.Quarterback.validateRoute=1&amp;amp;other.KM_Utility.getViewCount=1&amp;amp;r=1&amp;amp;other.KM_Utility.getKnowDetails=1&amp;amp;ui-communities-components-aura-components-forceCommunity-seoAssistant.SeoAssistant.getSeoData=1&amp;amp;CoveoV2.EndpointHandler.getEndpoint=1&amp;amp;other.KM_Utility.getUrl=1&amp;amp;other.KM_Utility.getPRNumberLinks=1&amp;amp;other.KM_Utility.getCaseLike=1"&gt;VMware Knowledge Base&lt;/A&gt; (&lt;SPAN class="uiOutputText slds-align-middle article_title slds-wrap slds-page-header__title" data-aura-class="uiOutputText" data-aura-rendered-by="37:134;a" style="font-size: 10pt;"&gt;Manipulating a file on a Datastore fails with the error: device or resource busy / file is locked (1008728)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/10051?other.KM_Utility.getArticleMetadata=2&amp;amp;CoveoV2.ContentHandler.getLoader=1&amp;amp;other.KM_Utility.getUser=1&amp;amp;other.KM_Utility.getAllTranslatedLanguages=2&amp;amp;other.KM_Utility.getContentdocument=1&amp;amp;ui-comm-runtime-components-aura-components-siteforce-qb.Quarterback.validateRoute=1&amp;amp;other.KM_Utility.getViewCount=1&amp;amp;r=1&amp;amp;other.KM_Utility.getKnowDetails=1&amp;amp;ui-communities-components-aura-components-forceCommunity-seoAssistant.SeoAssistant.getSeoData=1&amp;amp;CoveoV2.EndpointHandler.getEndpoint=1&amp;amp;other.KM_Utility.getUrl=1&amp;amp;other.KM_Utility.getPRNumberLinks=1&amp;amp;other.KM_Utility.getCaseLike=1" title="https://kb.vmware.com/s/article/10051?other.KM_Utility.getArticleMetadata=2&amp;amp;CoveoV2.ContentHandler.getLoader=1&amp;amp;other.KM_Utility.getUser=1&amp;amp;other.KM_Utility.getAllTranslatedLanguages=2&amp;amp;other.KM_Utility.getContentdocument=1&amp;amp;ui-comm-runtime-components-aura-components-siteforce-qb.Quarterback.validateRoute=1&amp;amp;other.KM_Utility.getViewCount=1&amp;amp;r=1&amp;amp;other.KM_Utility.getKnowDetails=1&amp;amp;ui-communities-components-aura-components-forceCommunity-seoAssistant.SeoAssistant.getSeoData=1&amp;amp;CoveoV2.EndpointHandler.getEndpoint=1&amp;amp;other.KM_Utility.getUrl=1&amp;amp;other.KM_Utility.getPRNumberLinks=1&amp;amp;other.KM_Utility.getCaseLike=1"&gt;VMware Knowledge Base&lt;/A&gt;​ &lt;SPAN class="uiOutputText slds-align-middle article_title slds-wrap slds-page-header__title" data-aura-class="uiOutputText" data-aura-rendered-by="37:174;a"&gt;(&lt;SPAN class="uiOutputText slds-align-middle article_title slds-wrap slds-page-header__title" data-aura-class="uiOutputText" data-aura-rendered-by="37:174;a"&gt;Investigating virtual machine file locks on ESXi (10051))&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Else, have you checked if the volume is in use ? If you can , temporarly remove any links between your VMs and the datastore then unmap -l the datastore then rebuild links.&lt;/P&gt;&lt;P&gt;If you use HA check if your datastore is not used for heartbeat (let me know if you need help)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Aug 2019 09:25:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vmfs-volumes-esxcli-storage-vmfs-unmap-l-UNITY027-SSD-20TB-ERROR/m-p/1861875#M182295</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2019-08-14T09:25:22Z</dc:date>
    </item>
    <item>
      <title>Re: SAN Storage share to ESXI hosts</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/SAN-Storage-share-to-ESXI-hosts/m-p/1862153#M22933</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can run different VM on the same datastore but not on the same volume except if you use RDM disks. (else it's advised to use a replication software)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In your case, i'd say it seems preferable to map .rdm in cross-way to avoid path conflicts..&lt;/P&gt;&lt;P&gt;Take a look at the image below :&lt;/P&gt;&lt;P&gt;&lt;IMG alt="http://vcloud-lab.com/files/images/vmware-vsphere-raw-device-mapping-rdm-storage-lun-datastore-rdm-disk-shared-physical-and-virtual-esxi-storage-raw-lun.png" class="transparent shrinkToFit jive-image" height="346" src="http://vcloud-lab.com/files/images/vmware-vsphere-raw-device-mapping-rdm-storage-lun-datastore-rdm-disk-shared-physical-and-virtual-esxi-storage-raw-lun.png" style="width: 484px; height: 345.714px;" width="484" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Aug 2019 09:15:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/SAN-Storage-share-to-ESXI-hosts/m-p/1862153#M22933</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2019-08-14T09:15:24Z</dc:date>
    </item>
    <item>
      <title>Re: Running out of pseudo terminals on ESXi 6.5u2 - "error: openpty: No such file or directory"</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Running-out-of-pseudo-terminals-on-ESXi-6-5u2-quot-error-openpty/m-p/486433#M5343</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, and can you provide the ssh config from ESXi side&lt;/P&gt;&lt;P&gt;use "cat /etc/ssh/sshd_config"&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Aug 2019 09:06:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Running-out-of-pseudo-terminals-on-ESXi-6-5u2-quot-error-openpty/m-p/486433#M5343</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2019-08-14T09:06:33Z</dc:date>
    </item>
    <item>
      <title>Re: Running out of pseudo terminals on ESXi 6.5u2 - "error: openpty: No such file or directory"</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Running-out-of-pseudo-terminals-on-ESXi-6-5u2-quot-error-openpty/m-p/486431#M5341</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry, yes on the server side&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Aug 2019 05:18:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Running-out-of-pseudo-terminals-on-ESXi-6-5u2-quot-error-openpty/m-p/486431#M5341</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2019-08-13T05:18:18Z</dc:date>
    </item>
    <item>
      <title>Re: Running out of pseudo terminals on ESXi 6.5u2 - "error: openpty: No such file or directory"</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Running-out-of-pseudo-terminals-on-ESXi-6-5u2-quot-error-openpty/m-p/486429#M5339</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yeah that's weird...&amp;nbsp; you start and end a ssh session it's logged so we can trust the connection close well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have you tried to set a timeout for ssh sessions ? (even though the starting/ending of your ssh sessions are logged so it means they close well, we can verify if a timeout change anything.)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Aug 2019 05:28:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Running-out-of-pseudo-terminals-on-ESXi-6-5u2-quot-error-openpty/m-p/486429#M5339</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2019-08-12T05:28:56Z</dc:date>
    </item>
    <item>
      <title>Re: Running out of pseudo terminals on ESXi 6.5u2 - "error: openpty: No such file or directory"</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Running-out-of-pseudo-terminals-on-ESXi-6-5u2-quot-error-openpty/m-p/486427#M5337</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi thanks for your logs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just on august 08th there's around 100 ssh connection initiated by these 2 IPs :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;10.1.36.58&lt;/P&gt;&lt;P&gt;10.33.158.183&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a script running or something like that ? Because the following commands are launched every 15min along the night and day and it creates SSH connections... :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;2019-08-08T00:20:22Z sshd[133943]: User 'root' running command '/opt/lsi/storcli/storcli show J'&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;2019-08-08T00:20:22Z sshd[133943]: User 'root' running command 'ls /opt/lsi/storcli/storcli'&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;2019-08-08T00:20:22Z sshd[133943]: User 'root' running command '/opt/lsi/storcli/storcli /c0 show J'&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can correlate every time those commands are launched (in auth.log) it add an entry to shell.log, and there's exactly the same time..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Aug 2019 14:58:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Running-out-of-pseudo-terminals-on-ESXi-6-5u2-quot-error-openpty/m-p/486427#M5337</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2019-08-09T14:58:02Z</dc:date>
    </item>
    <item>
      <title>Re: Intel C620 chipset</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Intel-C620-chipset/m-p/1849188#M21246</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That's weird...&lt;/P&gt;&lt;P&gt;I have had that kind of issues about sensors in HPE Gen10 servers, finally vmware has developped a patch to resolve my issue..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't know what to say more except trying to know if the issue remains with ESXi 6.7 U2 ? else working with Dell and VMware support, or opening a ticket, i'm so sorry...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Aug 2019 07:46:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Intel-C620-chipset/m-p/1849188#M21246</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2019-08-09T07:46:25Z</dc:date>
    </item>
    <item>
      <title>Re: Using Dell Custom image for ESXi 6.7 Update 2</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Using-Dell-Custom-image-for-ESXi-6-7-Update-2/m-p/1853433#M21839</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you succeed ? &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>Fri, 09 Aug 2019 06:53:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Using-Dell-Custom-image-for-ESXi-6-7-Update-2/m-p/1853433#M21839</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2019-08-09T06:53:31Z</dc:date>
    </item>
    <item>
      <title>Re: Running out of pseudo terminals on ESXi 6.5u2 - "error: openpty: No such file or directory"</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Running-out-of-pseudo-terminals-on-ESXi-6-5u2-quot-error-openpty/m-p/486424#M5334</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;Did you change anything in sshd_config ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you can, check if you can correlate the pty/tX session with any world ID with this command :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;grep -i pty /var/log/auth.log&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: calibri, verdana, arial, sans-serif;"&gt;it will raise a results like : &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;2018-10-10T08:44:20Z sshd[2989715]: Session opened for 'root' on /dev/char/pty/t0&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;where 2989715 is the current world id of the session pty/t0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then if you retrieves all the World ID, then we can check from where it comes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS : Can you put your shell.log and auth.log as an attached files (or private message if you want), i'll check it out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Aug 2019 14:31:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Running-out-of-pseudo-terminals-on-ESXi-6-5u2-quot-error-openpty/m-p/486424#M5334</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2019-08-08T14:31:02Z</dc:date>
    </item>
    <item>
      <title>Re: VM Deployment with OS Customization Specification</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/VM-Deployment-with-OS-Customization-Specification/m-p/1854184#M21901</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;B&gt;AlessandroRomeo68&lt;/B&gt;​&amp;nbsp; any ideas ? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've tried other settings but still the same error..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Aug 2019 11:46:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/VM-Deployment-with-OS-Customization-Specification/m-p/1854184#M21901</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2019-08-08T11:46:34Z</dc:date>
    </item>
    <item>
      <title>Re: Intel C620 chipset</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Intel-C620-chipset/m-p/1849186#M21244</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Alright i found some stuff, i don't know if this is the root cause or not :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There's conflicts between some VIBs &lt;SPAN&gt;(&lt;SPAN style="color: #e23d39;"&gt;misc-drivers and &lt;SPAN style="color: #e23d39;"&gt;native-misc-drivers)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #303030;"&gt;At this point, i would say to check with Dell if it's safe to try to delete both VIBs and re-update sensors to check if there's still an issue or not.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #303030;"&gt;Also i think something is weird because the only dell-vib installed are about Support Information and Idrac only, there's nothing about specific dell material.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;VMware_bootbank_esx-base_6.7.0-1.28.10302608&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp; Name: esx-base&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp; Version: 6.7.0-1.28.10302608&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp; Type: bootbank&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp; Vendor: VMware&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp; Acceptance Level: VMwareCertified&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp; Summary: ESXi base system&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp; Description: VMware ESXi is a thin hypervisor integrated into server hardware. The compact, hardware embedded architecture of VMware ESXi raises the bar for security and reliability and lays the foundation for a dynamic, automated datacenter.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp; ReferenceURLs: &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp; Creation Date: 2018-10-03&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp; Depends: vsan &amp;gt;= 6.7.0-1.28, vsan &amp;lt;&amp;lt; 6.7.0-1.29, esx-update &amp;gt;= 6.7.0-1.28, esx-update &amp;lt;&amp;lt; 6.7.0-1.29&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&lt;STRONG&gt;&amp;nbsp; &lt;SPAN style="color: #e23d39;"&gt; Conflicts: misc-drivers &amp;lt;&amp;lt; 5.5.0, native-misc-drivers &amp;lt;&amp;lt; 6.1.0&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp; Replaces: esx-xlibs, esx-tboot&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp; Provides: cim.CMPI = 1.0, cim.CMPI = 2.0, cim.DMTF.DSP1004 = 1.0.0-1.0, cim.DMTF.DSP1030 = 1.0.0-1.0, cim.DMTF.DSP1022 = 1.0.0-1.0, cim.DMTF.DSP1013 = 1.0.1-1.0, cim.DMTF.DSP1054 = 1.1.0-0.5, cim.DMTF.DSP1025 = 1.0.0-1.0, cim.SNIA.DSP1025.Job_Control = 1.1.0-0.5, cim.DMTF.DSP1075 = 1.0.0-0.5, cim.DMTF.DSP1011 = 1.0.2-1.0, cim.DMTF.DSP1027 = 1.0.1-1.0, cim.DMTF.DSP1015 = 1.0.1-1.0, cim.DMTF.DSP1033 = 1.0.0-1.0, cim.DMTF.DSP1010 = 1.0.0-1.0, cim.DMTF.DSP1009 = 1.0.0-1.0, cim.DMTF.DSP1023 = 1.0.0-1.0, cim.DMTF.DSP1026 = 1.0.0-1.0, jumpstart = 1, jumpstart = 2, jumpstart = 3, jumpstart = 4, esxcli = 1.0.0, hostprofile = 5.0.0, hostprofile = 5.1.0, nicmgmt = 0.1, nsx-api = 2.1, com.vmware.dvfilter-2.0.0.0, com.vmware.vds-2.0.0.0, uwglibc-2.5-34-1, uwglibc-2.5-81-1, uwglibc-2.12.2-1, uwglibc64-2.5-34-1, uwglibc64-2.5-81-1, uwglibc64-2.12.2-1, libvmkuser-5.0.0-1, libvmkuser-5.1.0-1, libvmkuser-5.5.0-1, libvmkuser-6.0.0-1, libvmkuser-6.5.0-1, libvmkuser-6.7.0-1, uwvmkcall-5.0.0-1, uwvmkcall-5.1.0-1, uwvmkcall-5.5.0-1, uwvmkcall-6.0.0-1, uwvmkcall-6.5.0-1, uwvmkcall-6.7.0-1, vmkepsecapi_2.0.0.0, vmkapi_2_5_0_0, vmkapi_2_4_0_0, vmkapi_2_3_0_0, vmkapi_2_2_0_0, vmkapi_incompat_2_5_0_0, vmiof_2_5_0_0, vmiof_2_0_0_0, vmiof_1_1_0_0, vmiof_1_0_0_0, esx-version = 6.7.0-1.28.10302608&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp; Maintenance Mode Required: True&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp; Hardware Platforms Required: &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp; Live Install Allowed: False&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp; Live Remove Allowed: False&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp; Stateless Ready: True&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp; Overlay: False&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp; Tags: &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new, courier;"&gt;&amp;nbsp;&amp;nbsp; Payloads: BOOTIA32.EFI, BOOTx64.EFI, README, b, btldr, chardevs, efiboot.img, esximage.zip, extlinux, features, isoinfo, isolinux.bin, jumpstrt, k, mboot.c32, mbr.bin, mcopy, menu.c32, metadata.xml, osl.txt, precheck.py, prep.py, procfs, s, safeboot.c32, sb, user, useropts, vim, vmx&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Aug 2019 11:04:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Intel-C620-chipset/m-p/1849186#M21244</guid>
      <dc:creator>GaelV</dc:creator>
      <dc:date>2019-08-08T11:04:07Z</dc:date>
    </item>
  </channel>
</rss>

