twit.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
The official Mastodon of the TWiT Podcast Network

Administered by:

Server stats:

1.4K
active users

#vSphere

0 posts0 participants0 posts today
ErikBussink :trekbar:<p><span class="h-card" translate="no"><a href="https://mastodon.infrageeks.social/@erik" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>erik</span></a></span> first NVMe-oF testing between the <span class="h-card" translate="no"><a href="https://mikrotik.social/@mikrotik" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>mikrotik</span></a></span> <a href="https://vmst.io/tags/RDS2216" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RDS2216</span></a> and a nested Linux VM on <a href="https://vmst.io/tags/vSphere" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>vSphere</span></a>.</p>
Dèjì Akọ́mọláfẹ́<p>Attention <a href="https://twit.social/tags/VMware" class="mention hashtag" rel="tag">#<span>VMware</span></a> <a href="https://twit.social/tags/vSphere" class="mention hashtag" rel="tag">#<span>vSphere</span></a> Admins: A new vSphere Update (3k) has been released to address multiple issues in vSphere 7.0.</p><p>This update fixes the issue &quot;PR 3106817: After you install Windows Server 2022 update KB5022842, Windows Server 2022 virtual machines that use UEFI Secure Boot might fail to boot&quot;<br /> <a href="https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-70u3k-release-notes.html" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="ellipsis">docs.vmware.com/en/VMware-vSph</span><span class="invisible">ere/7.0/rn/vsphere-esxi-70u3k-release-notes.html</span></a></p>
Dèjì Akọ́mọláfẹ́<p><a href="https://twit.social/tags/Microsoft" class="mention hashtag" rel="tag">#<span>Microsoft</span></a>&#39;s February 2023 <a href="https://twit.social/tags/PatchTuesday" class="mention hashtag" rel="tag">#<span>PatchTuesday</span></a> Tuesday: Secure Boot issues for <a href="https://twit.social/tags/Windows" class="mention hashtag" rel="tag">#<span>Windows</span></a> <a href="https://twit.social/tags/Server" class="mention hashtag" rel="tag">#<span>Server</span></a> 2022 VMs hosted on <a href="https://twit.social/tags/VMware" class="mention hashtag" rel="tag">#<span>VMware</span></a> <a href="https://twit.social/tags/vSphere" class="mention hashtag" rel="tag">#<span>vSphere</span></a> Platforms (up to, and including 7.0x)</p><p>Workaround:<br />1. Disable Secure Boot on affected VMs, or<br />2. Don&#39;t install Patch yet, or<br />3. Upgrade to vSphere 8.0</p><p><a href="https://twit.social/tags/SecureBoot" class="mention hashtag" rel="tag">#<span>SecureBoot</span></a> <a href="https://twit.social/tags/ESXi" class="mention hashtag" rel="tag">#<span>ESXi</span></a></p><p><a href="https://kb.vmware.com/s/article/90947" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="">kb.vmware.com/s/article/90947</span><span class="invisible"></span></a><br /><a href="https://www.catalog.update.microsoft.com/Search.aspx?q=kb5022842" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://www.</span><span class="ellipsis">catalog.update.microsoft.com/S</span><span class="invisible">earch.aspx?q=kb5022842</span></a></p>
Dèjì Akọ́mọláfẹ́<p>If you are a <a href="https://twit.social/tags/VMware" class="mention hashtag" rel="tag">#<span>VMware</span></a> <a href="https://twit.social/tags/vSphere" class="mention hashtag" rel="tag">#<span>vSphere</span></a> Admin and you have Cluster-on-Die (aka &quot;Sub-NUMA Cluster&quot;) enabled on your <a href="https://twit.social/tags/ESXi" class="mention hashtag" rel="tag">#<span>ESXi</span></a> Hosts, I&#39;d appreciate it if you could please DM me. I&#39;d like to pick your brains.</p><p>If you are reading this on <a href="https://twit.social/tags/Twitter" class="mention hashtag" rel="tag">#<span>Twitter</span></a>, please reach out, too. I still check my DMs periodically.</p><p>Thanks</p>
Dèjì Akọ́mọláfẹ́<p><a href="https://twit.social/tags/VMware" class="mention hashtag" rel="tag">#<span>VMware</span></a> <a href="https://twit.social/tags/vSphere" class="mention hashtag" rel="tag">#<span>vSphere</span></a> 8.0: To HotAdd vCPUs or Not To HotAdd vCPUs?</p><p>&lt;tldr;&gt; Knock Yourself Out &lt;/tldr;&gt;</p><p>One of the toughest configuration decisions that vSphere Administrators have had to make over the last decade is whether or not to enable CPU HotAdd on VMs hosting resource-intensive Business Critical Applications, especially if the Application is NUMA-aware and can benefit from NUMA Topology notifications.</p>
Dèjì Akọ́mọláfẹ́<p>Me, right now. Trying to wrangle <a href="https://twit.social/tags/vSphere" class="mention hashtag" rel="tag">#<span>vSphere</span></a> HA on these Hosts.</p><p>To think that they call me an &quot;Expert&quot; in these things 🤦‍♂️ 🤔 😭</p>