<?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>lukaslang Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>lukaslang Tracker</description>
    <pubDate>Sat, 25 Nov 2023 06:39:45 GMT</pubDate>
    <dc:date>2023-11-25T06:39:45Z</dc:date>
    <item>
      <title>Re: vRealize Operations 8.6 causing VM CPU peaks</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/vRealize-Operations-8-6-causing-VM-CPU-peaks/m-p/2909989#M19097</link>
      <description>&lt;P&gt;Sorry for unburying this thread, but we had the exact same issue in our DEV environment. Disabling the application discovery also solved this for us. I have not seen any specific mention in the release notes from 8.6.3 but maybe someone has already tested it? Analyzing the WMI Logs of the windows machines, it seems that the WMI query is faulty and causes the CPU spikes every 5 minutes.&lt;/P&gt;</description>
      <pubDate>Thu, 19 May 2022 11:27:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/vRealize-Operations-8-6-causing-VM-CPU-peaks/m-p/2909989#M19097</guid>
      <dc:creator>lukaslang</dc:creator>
      <dc:date>2022-05-19T11:27:41Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi and SD-Cards</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-and-SD-Cards/m-p/2868406#M278149</link>
      <description>&lt;P&gt;Sorry for the dumb question, but this article especially says that it is fine (non best practice) for vSAN 7.0?&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.vmware.com/s/article/2129050" target="_blank" rel="noopener"&gt;https://kb.vmware.com/s/article/2129050&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;edit: ok it says that you should not mix RAID and JBOD&lt;/P&gt;</description>
      <pubDate>Fri, 24 Sep 2021 11:33:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-and-SD-Cards/m-p/2868406#M278149</guid>
      <dc:creator>lukaslang</dc:creator>
      <dc:date>2021-09-24T11:33:15Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi and SD-Cards</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-and-SD-Cards/m-p/2868353#M278137</link>
      <description>&lt;P&gt;Well I am no vSAN expert, but from my understanding you should be good to go to create a RAID 1 with two SSDs (directly on the RAID controller) as boot device and let the other 4 SSDs unconfigured to show them to the OS and then use 1 of them as Cache Disk and the 3 others as capacity disks (as long as all of them are on the HCL for vSAN and have the performance/endurance ratings for the different tiers).&lt;/P&gt;</description>
      <pubDate>Fri, 24 Sep 2021 06:30:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-and-SD-Cards/m-p/2868353#M278137</guid>
      <dc:creator>lukaslang</dc:creator>
      <dc:date>2021-09-24T06:30:51Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi and SD-Cards</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-and-SD-Cards/m-p/2868236#M278126</link>
      <description>&lt;P&gt;Using a supported HPE Controller in the VMware HCL should be no problem. Simply create a RAID 1 with 2 of the SSDs and another RAID 5 with the 4 remaining disks. ESXi will then see 2 separate logical disks.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Sep 2021 14:29:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-and-SD-Cards/m-p/2868236#M278126</guid>
      <dc:creator>lukaslang</dc:creator>
      <dc:date>2021-09-23T14:29:38Z</dc:date>
    </item>
    <item>
      <title>Re: SD Boot issue Solution in 7.x</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2868006#M278097</link>
      <description>&lt;P&gt;Seems related to the AHCI integrated driver of ESXi. Today I reinstalled another server which has a RAID setup and there everything installed with normal speed.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Sep 2021 14:19:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2868006#M278097</guid>
      <dc:creator>lukaslang</dc:creator>
      <dc:date>2021-09-22T14:19:59Z</dc:date>
    </item>
    <item>
      <title>Re: SD Boot issue Solution in 7.x</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2867155#M278011</link>
      <description>&lt;P&gt;Has anyone else experienced that U2c slows the local disk extremely down? Installations of the NSX-T or HA agents take a very long time, even on SSDs connect via the chipset SATA controller (Wellsburg oder Lewisburg).&lt;/P&gt;</description>
      <pubDate>Thu, 16 Sep 2021 13:21:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2867155#M278011</guid>
      <dc:creator>lukaslang</dc:creator>
      <dc:date>2021-09-16T13:21:21Z</dc:date>
    </item>
    <item>
      <title>Re: SD Boot issue Solution in 7.x</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2865125#M277840</link>
      <description>&lt;P&gt;Well maybe they call it 7.5 instead of 7.0 U3 - "as in earlier versions, non-persistent storage was considered supported, now, systems with only a SD-Card/USB boot devices are considered unsupported" &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@8159967D7D3CC6D384BA5B938B4FC1AE/emoticons/1f648.png" alt=":see_no_evil_monkey:" title=":see_no_evil_monkey:" /&gt;&lt;/P&gt;&lt;P&gt;Or the upgrade requires a fresh install like they did with the vcsa and for esxi you then need "high endurance fast low latency high iops flash media"&lt;/P&gt;</description>
      <pubDate>Fri, 03 Sep 2021 08:53:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2865125#M277840</guid>
      <dc:creator>lukaslang</dc:creator>
      <dc:date>2021-09-03T08:53:09Z</dc:date>
    </item>
    <item>
      <title>Re: SD Boot issue Solution in 7.x</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2865116#M277838</link>
      <description>&lt;P&gt;Now the link to &lt;A href="https://kb.vmware.com/s/article/85615?lang=en_US" target="_blank"&gt;https://kb.vmware.com/s/article/85615?lang=en_US &lt;/A&gt;shows pagenotfound. Interesting...&lt;/P&gt;</description>
      <pubDate>Fri, 03 Sep 2021 08:14:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2865116#M277838</guid>
      <dc:creator>lukaslang</dc:creator>
      <dc:date>2021-09-03T08:14:20Z</dc:date>
    </item>
    <item>
      <title>Re: SD Boot issue Solution in 7.x</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2864990#M277811</link>
      <description>&lt;P&gt;&amp;nbsp;The biggest problem is, that there, until now, is no 100% clear statement. If you have to plan for the future this course is unacceptible.&lt;/P&gt;&lt;P&gt;The strangest thing is, that my test host with an 8 GB HPE SD-Card is now running for almost two months without a problem on U2a.&lt;/P&gt;&lt;P&gt;For the other hosts, since the B140i controller is unsupported with ESXi 7, I am going to think to disable the RAID functionality and use the Wellsburg SATA controller. Has anyone done that yet on HPE hardware? I was not aware that this is possible.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Sep 2021 14:56:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2864990#M277811</guid>
      <dc:creator>lukaslang</dc:creator>
      <dc:date>2021-09-02T14:56:18Z</dc:date>
    </item>
    <item>
      <title>Re: SD Boot issue Solution in 7.x</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2864974#M277804</link>
      <description>&lt;P&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/2727028"&gt;@vbabic&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Well you have to say, that this article does mention only the problem with non-persistent storage of /scratch which in SD-Card Installations always led to this message. If you redirect the scratch location to persistent storage (like a LUN) the message will not pop up.&lt;/P&gt;&lt;P&gt;The article also says "A system with &lt;U&gt;&lt;STRONG&gt;only&lt;/STRONG&gt;&lt;/U&gt; a SD-Card/USB boot device is operating in an unsupported state with the potential for premature corruption", which in most cases, will not be the case.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Sep 2021 14:07:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2864974#M277804</guid>
      <dc:creator>lukaslang</dc:creator>
      <dc:date>2021-09-02T14:07:19Z</dc:date>
    </item>
    <item>
      <title>Re: SD Boot issue Solution in 7.x</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2858508#M277069</link>
      <description>&lt;P&gt;Status of our SD Card Testserver: 33 days uptime with no problems. It runs along with 19 other servers in a cluster.&lt;/P&gt;&lt;P&gt;Quick question to the HPE owners: Have you updated the firmware with the latest SPP for Gen9 (2021.05.0) and installed ESXi with the U2a customized image? Maybe this prevents or slows down the issue?&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jul 2021 07:30:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2858508#M277069</guid>
      <dc:creator>lukaslang</dc:creator>
      <dc:date>2021-07-21T07:30:08Z</dc:date>
    </item>
    <item>
      <title>Re: SD Boot issue Solution in 7.x</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2858177#M277056</link>
      <description>&lt;P&gt;Seems it got delayed until end of August (only rumors). But since there are no official statements, it is really difficult to tell an exact release date.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jul 2021 12:18:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2858177#M277056</guid>
      <dc:creator>lukaslang</dc:creator>
      <dc:date>2021-07-19T12:18:37Z</dc:date>
    </item>
    <item>
      <title>Re: SD Boot issue Solution in 7.x</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2857869#M277026</link>
      <description>&lt;P&gt;It's a 8 GB HPE SD Card in a BL460c Gen9 Blade. The 8 GB card is not officially supportet by HPE for ESXi 7, but the 32GB is &lt;A href="https://h20195.www2.hpe.com/v2/getpdf.aspx/c04123175.pdf" target="_self"&gt;Quickspecs&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;All we did was relocating scratch, productLocker and LogDump to FC-SAN (which we also did before for many years). Since during the upgrade process we've seen many other strange issues, this Host was fresh installed.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jul 2021 14:53:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2857869#M277026</guid>
      <dc:creator>lukaslang</dc:creator>
      <dc:date>2021-07-16T14:53:23Z</dc:date>
    </item>
    <item>
      <title>Re: SD Boot issue Solution in 7.x</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2857866#M277024</link>
      <description>&lt;P&gt;This is a sad story. On the other hand they show us running ESXi on Raspberries and on the other we have to use "high endurance" flash media to power the hypervisor.&lt;/P&gt;&lt;P&gt;But in the end, U3 will solve this mess. If not, I have to explain my managment that we bought a bunch of useless SD Cards because ESXi 7 does not support the RAID Controller with the existing SSDs in our existing servers because VMware decided to vmotion their QA to the customers.&lt;/P&gt;&lt;P&gt;FYI: Our SD Card Test Blade runs now for 29 days without issues (with heavy workload).&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jul 2021 14:45:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2857866#M277024</guid>
      <dc:creator>lukaslang</dc:creator>
      <dc:date>2021-07-16T14:45:16Z</dc:date>
    </item>
    <item>
      <title>Re: SD Boot issue Solution in 7.x</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2856910#M276943</link>
      <description>&lt;P&gt;But why would the vcls machines write on the SD Cards? 8 or 32 GB Cards do not provide a datastore because they do not have enough space. This little annyoing things are spreading across all datastores but I have never seen one running on SD since this should be impossbile.&lt;/P&gt;&lt;P&gt;Our Testhost with 7.0 U2a on SD runs now for 24 days without issues.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jul 2021 13:45:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2856910#M276943</guid>
      <dc:creator>lukaslang</dc:creator>
      <dc:date>2021-07-12T13:45:21Z</dc:date>
    </item>
    <item>
      <title>Re: SD Boot issue Solution in 7.x</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2854482#M276784</link>
      <description>&lt;P&gt;It is a shame, that such important things are not published properly (but seen from the side of VMware, this is understandable. Imagine the rumor IF they make an official announcement that SD Cards are no longer supported).&lt;/P&gt;&lt;P&gt;At the moment we have a test Host running on HPE SD with redirected ProductLocker, Scratch and syslog. It is running fine for 7 days now. Hope this will stay so.&lt;/P&gt;&lt;P&gt;But this mess does not end, we found out that a bunch of our Hosts are using a Disk Controller that with vSphere 7 is no longer supported: &lt;A href="https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00106849en_us" target="_self"&gt;B140i and vSphere 7&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So we HAD Hosts with "High Endurance Storage" but had to insert SD Cards to be able to install vSphere 7 (clearly HPEs fault). And now VMware is telling us, that with U2a SD Card is no more the best practice? The Hypervisor with the smallest possible footprint? What in Gods name is so important, that you have to read it a million times from local media instead of loading this c*** inside the memory of the Host since we have hundreds of GB of RAM. Get your things together.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Jun 2021 06:39:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/SD-Boot-issue-Solution-in-7-x/m-p/2854482#M276784</guid>
      <dc:creator>lukaslang</dc:creator>
      <dc:date>2021-06-25T06:39:11Z</dc:date>
    </item>
    <item>
      <title>Re: ESXI 7.0.2 Host Hanging after upgrade from 6.5 to 7</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXI-7-0-2-Host-Hanging-after-upgrade-from-6-5-to-7/m-p/2854286#M276761</link>
      <description>&lt;P&gt;Well, HPE lists their 32GB SD Cards as supported for vSphere 7, but who knows if they calculated this through with the behavior of U2.&lt;/P&gt;&lt;P&gt;Redirecting Logs, Scratch, Logdump and VMware Tools to SAN seems to run fine (at the moment).&lt;/P&gt;&lt;P&gt;From what I've seen, an Upgrade to 7.0 U2a cannot be considered. We had so many strange issues upgrading from 6.7 EP15 to U2a that we ditched the upgrade and are going straight to fresh installs.&lt;/P&gt;&lt;P&gt;Issues we have seen so far:&lt;/P&gt;&lt;P&gt;- Hosts are hanging on vmw_satp_alua while booting even we do not have any RDM Disks&lt;/P&gt;&lt;P&gt;- NSX-T Transport Nodes are unable to establish a connection to the managers (and these Hosts were fresh installed with U2 and upgraded to U2a, yes I know U2 got pulled, but none of the mentioned issues "crypto64.efi" happend so there has to be a lot more)&lt;/P&gt;&lt;P&gt;- Remediation stuck or incomplete&lt;/P&gt;&lt;P&gt;All things were resolved by a fresh install. If you have time, I would go that path.&lt;/P&gt;&lt;P&gt;Who knows how many other issues are created in the depths of vSphere during the upgrade path that will show up in the future.&lt;/P&gt;&lt;P&gt;Maybe U3 will resolve many of the mentioned problems, but who knows.&lt;/P&gt;&lt;P&gt;I am really disappointed by this release.&lt;/P&gt;</description>
      <pubDate>Thu, 24 Jun 2021 08:43:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXI-7-0-2-Host-Hanging-after-upgrade-from-6-5-to-7/m-p/2854286#M276761</guid>
      <dc:creator>lukaslang</dc:creator>
      <dc:date>2021-06-24T08:43:45Z</dc:date>
    </item>
    <item>
      <title>Re: Can a Dvswitch with MTU of 9000  host portgroups which use Jumbo frames and some which not use i</title>
      <link>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/Can-a-Dvswitch-with-MTU-of-9000-host-portgroups-which-use-Jumbo/m-p/2854283#M14335</link>
      <description>&lt;P&gt;The MTU setting on vDS level only allows Jumbo Frames to pass (like on any physical switch). As long as your VMs do not send jumbo frames, vSphere won't do it either (for VM traffic). Like written above, you cannot set different MTU values on portgroups, this will only work on vmkernel ports.&lt;/P&gt;&lt;P&gt;So in conclusion: if you want to use jumbo frames you have to do the following things:&lt;/P&gt;&lt;P&gt;- Check (and enable) your physical switch to allow jumbo frames&lt;/P&gt;&lt;P&gt;- Modify the MTU on vDS&lt;/P&gt;&lt;P&gt;- Modify your VM (on OS Level) to send jumbo frames&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Jun 2021 08:27:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-vNetwork-Discussions/Can-a-Dvswitch-with-MTU-of-9000-host-portgroups-which-use-Jumbo/m-p/2854283#M14335</guid>
      <dc:creator>lukaslang</dc:creator>
      <dc:date>2021-06-24T08:27:30Z</dc:date>
    </item>
    <item>
      <title>Re: 7.0.2 - iSCSI name change after upgrade</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/7-0-2-iSCSI-name-change-after-upgrade/m-p/2854282#M276760</link>
      <description>&lt;P&gt;Just another indicator that 7.0 U2(a) is a complete mess. Never had so many issues with previous upgrades.&lt;/P&gt;</description>
      <pubDate>Thu, 24 Jun 2021 08:17:13 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/7-0-2-iSCSI-name-change-after-upgrade/m-p/2854282#M276760</guid>
      <dc:creator>lukaslang</dc:creator>
      <dc:date>2021-06-24T08:17:13Z</dc:date>
    </item>
    <item>
      <title>Re: VR 8.4.0 Plugin in VROPS 8.3 - authentication service infrastructure error</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/VR-8-4-0-Plugin-in-VROPS-8-3-authentication-service/m-p/2853854#M18593</link>
      <description>&lt;P&gt;That totally did the trick, but you have to install 8.4.0.2 first. On another install with 8.4 it kept the error. After updating and using the case sensitive username it started working again.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Big thanks&lt;/P&gt;</description>
      <pubDate>Tue, 22 Jun 2021 07:03:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/VR-8-4-0-Plugin-in-VROPS-8-3-authentication-service/m-p/2853854#M18593</guid>
      <dc:creator>lukaslang</dc:creator>
      <dc:date>2021-06-22T07:03:47Z</dc:date>
    </item>
  </channel>
</rss>

