<?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>gork201110141 Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>gork201110141 Tracker</description>
    <pubDate>Tue, 21 Nov 2023 05:02:08 GMT</pubDate>
    <dc:date>2023-11-21T05:02:08Z</dc:date>
    <item>
      <title>Re: VMware ESXi-7.0U3d Nvidia Driver Linux 510 wont load</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/VMware-ESXi-7-0U3d-Nvidia-Driver-Linux-510-wont-load/m-p/2910326#M281793</link>
      <description>&lt;P&gt;This works again with 515.43.04 beta driver, but you must install with the open source kernel module instead of the closed source module. This can be done with: `&lt;SPAN&gt;./NVIDIA-Linux-x86_64-515.43.04.run -m=kernel-open` and by setting the NVreg_OpenRmEnableUnsupportedGpus=1 in the nvidia.ko module. &lt;A href="http://us.download.nvidia.com/XFree86/Linux-x86_64/515.43.04/README/kernel_open.html" target="_self"&gt;See the instructions here.&lt;/A&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 20 May 2022 15:49:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/VMware-ESXi-7-0U3d-Nvidia-Driver-Linux-510-wont-load/m-p/2910326#M281793</guid>
      <dc:creator>gork201110141</dc:creator>
      <dc:date>2022-05-20T15:49:44Z</dc:date>
    </item>
    <item>
      <title>Re: hostupdate.vmware.com does not resolve</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/hostupdate-vmware-com-does-not-resolve/m-p/2852897#M33456</link>
      <description>&lt;P&gt;6 hour global outage. Amazing&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jun 2021 03:23:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/hostupdate-vmware-com-does-not-resolve/m-p/2852897#M33456</guid>
      <dc:creator>gork201110141</dc:creator>
      <dc:date>2021-06-16T03:23:29Z</dc:date>
    </item>
    <item>
      <title>hostupdate.vmware.com does not resolve</title>
      <link>https://communities.vmware.com/t5/vSphere-Upgrade-Install/hostupdate-vmware-com-does-not-resolve/m-p/2852871#M33455</link>
      <description>&lt;P&gt;An update today failed to download a VIB file from hostupdate.vmware.com&lt;/P&gt;&lt;P&gt;Upon testing, this hostname is currently unresolvable. I have tested recursive resolution and resolving through various public DNS providers like cloudflare, google, quad9, etc.&lt;/P&gt;&lt;P&gt;Is there a workaround? When will the hostupdate repository be back online?&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;$ dig A hostupdate.vmware.com @1.1.1.1

; &amp;lt;&amp;lt;&amp;gt;&amp;gt; DiG 9.16.1-Ubuntu &amp;lt;&amp;lt;&amp;gt;&amp;gt; A hostupdate.vmware.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; -&amp;gt;&amp;gt;HEADER&amp;lt;&amp;lt;- opcode: QUERY, status: NXDOMAIN, id: 1912
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;hostupdate.vmware.com.         IN      A

;; ANSWER SECTION:
hostupdate.vmware.com.  25      IN      CNAME   shd-download.vmware.com.edgekey.net.
shd-download.vmware.com.edgekey.net. 21595 IN CNAME shd-download.vmware.com.splitter-eip.akadns.net.
shd-download.vmware.com.splitter-eip.akadns.net. 55 IN CNAME shd-download.vmware.com.eip.akadns.net.
shd-download.vmware.com.eip.akadns.net. 55 IN CNAME eip-ntt.shd-download.vmware.com.akahost.net.

;; AUTHORITY SECTION:
akahost.net.            25      IN      SOA     usw1.akam.net. hostmaster.akamai.com. 1464288323 43200 7200 604800 7200

;; Query time: 30 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Tue Jun 15 16:06:28 CDT 2021
;; MSG SIZE  rcvd: 320&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jun 2021 21:13:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Upgrade-Install/hostupdate-vmware-com-does-not-resolve/m-p/2852871#M33455</guid>
      <dc:creator>gork201110141</dc:creator>
      <dc:date>2021-06-15T21:13:20Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 6.7 Keep Getting PANIC bora/vmkernel/main/dlmalloc.c: 4924 - Usage error in dlmalloc</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/ESXi-6-7-Keep-Getting-PANIC-bora-vmkernel-main-dlmalloc-c-4924/m-p/2735864#M34412</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello; I tried to send you a private message but it seemed to fail. VMware support is tracking this issue for us also; however since the last time it occured the Sr. Solution Engineer who had been working the issue is now on PTO until July 3. Have you received any additional information as to a fix or workaround to avoid? We were told the issue was likely something related to VDR (vsphere replication).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Jun 2018 18:08:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/ESXi-6-7-Keep-Getting-PANIC-bora-vmkernel-main-dlmalloc-c-4924/m-p/2735864#M34412</guid>
      <dc:creator>gork201110141</dc:creator>
      <dc:date>2018-06-12T18:08:26Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 6.7 kernel panic during Heap_Free in dlmalloc</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-7-kernel-panic-during-Heap-Free-in-dlmalloc/m-p/1398990#M133694</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello; I tried to send you a private message but it failed. VMware support is tracking this issue for us also; however since the last time it occured the Sr. Solution Engineer who had been working the issue is now on PTO until July 3. Have you received any additional information as to a fix or workaround to avoid? We were told the issue was likely something related to VDR (vsphere replication).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Jun 2018 18:07:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-6-7-kernel-panic-during-Heap-Free-in-dlmalloc/m-p/1398990#M133694</guid>
      <dc:creator>gork201110141</dc:creator>
      <dc:date>2018-06-12T18:07:47Z</dc:date>
    </item>
  </channel>
</rss>

