<?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>rswartz Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>rswartz Tracker</description>
    <pubDate>Tue, 21 Nov 2023 05:01:26 GMT</pubDate>
    <dc:date>2023-11-21T05:01:26Z</dc:date>
    <item>
      <title>Can't find a particular ESXi BIOS setting "Intel Virtualization Technology for Directed I/O (VT-d)"</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Can-t-find-a-particular-ESXi-BIOS-setting-quot-Intel/m-p/2910337#M281794</link>
      <description>&lt;P data-unlink="true"&gt;So I'm trying to connect a PCI HBA card via DirectPath passthrough to one of our VMs. I believe I've found the VMware docs page explaining how to do so:&amp;nbsp;&amp;nbsp;&lt;A href="https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-5B3CAB26-5D06-4A99-92A0-3A04C69CE64B.html" target="_blank"&gt;https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-5B3CAB26-5D06-4A99-92A0-3A04C69CE64B.html&lt;/A&gt;&amp;nbsp; , but I've run into an issue when going through the prerequisites listed there.&lt;/P&gt;&lt;P data-unlink="true"&gt;Basically it says "Intel Virtualization Technology for Directed I/O (VT-d) or AMD I/O Virtualization Technology (IOMMU) must be enabled in the host BIOS". I'm assuming this means the ESXi host, but when I go into it's BIOS settings neither of these settings are listed. There is a setting called "Virtualization Technology" in the "Processor settings" section which is by default enabled, but I'm not sure this is what it's talking about. I was also directed to the setting "SR-IOV Global Enable" under the "Integrated Devices" tab, the information page for which I'll link just below, but which doesn't seem to imply it is what I'm looking for and doesn't mention DirectPath or Passthrough anywhere.&lt;/P&gt;&lt;P data-unlink="true"&gt;&lt;A href="https://www.dell.com/support/kbdoc/en-in/000144029/enabling-sr-iov-technology-on-dell-poweredge-servers" target="_blank"&gt;https://www.dell.com/support/kbdoc/en-in/000144029/enabling-sr-iov-technology-on-dell-poweredge-servers&lt;/A&gt;&lt;/P&gt;&lt;P data-unlink="true"&gt;The ESXi host is running on a PowerEdge R640,&lt;/P&gt;&lt;P data-unlink="true"&gt;ESXi version 7.0.3,&lt;/P&gt;&lt;P data-unlink="true"&gt;with BIOS version 2.12.2&lt;/P&gt;&lt;P data-unlink="true"&gt;----------------------------------------------------------------------------------&lt;/P&gt;&lt;P data-unlink="true"&gt;To clarify, I haven't tried connecting the HBA via DirectPath yet, but I'm creating documentation on how to set this up so I need to make sure that I know what the correct BIOS setting is.&lt;/P&gt;&lt;P data-unlink="true"&gt;I'm going to look through the guest OS BIOS settings to make sure they aren't there and update this post if that's the solution.&lt;/P&gt;</description>
      <pubDate>Fri, 20 May 2022 17:59:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Can-t-find-a-particular-ESXi-BIOS-setting-quot-Intel/m-p/2910337#M281794</guid>
      <dc:creator>rswartz</dc:creator>
      <dc:date>2022-05-20T17:59:53Z</dc:date>
    </item>
    <item>
      <title>Problem giving a unity datastore ESXi host access, and I think the problem is on the ESXi side</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Problem-giving-a-unity-datastore-ESXi-host-access-and-I-think/m-p/2902551#M281013</link>
      <description>&lt;P&gt;ESXi model PowerEdge r640 version 7.0 update 3&lt;/P&gt;&lt;P&gt;Unity 350F version 5.1.2.0&lt;/P&gt;&lt;P&gt;I recently had to remove ESXi host access from a datastore, then add that access back again. Every time I remove or add access, the unity GUI returns an error message that reads "Adding host access to the datastore partially failed (Error Code:0x5c00106)" despite this, access was removed and then added again seemingly without a problem for three of the datastores I did this with. But two of them refuse to be read by the ESXi host for some reason after re-adding access. One of them when being added again reads "Manage host file system using block... failed" now as well. That one doesn't even show up in the ESXi's "Storage" section. The other one not being read does show there, but its capacity says 0B and none of the VMs that run off of it are able to function. Both of these datastores can be added without a problem to the other ESXi host connected to that Unity system, so it must be a problem with either the ESXi host or the connection between that host and the Unity. The physical connection is fine though, and is a Fiber Channel connection.&lt;/P&gt;&lt;P&gt;On that same ESXi host, there is also two DGC Fiber Channel Disk objects under "Storage" &amp;gt; "Devices" which read as "Error, Uknown".&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Apr 2022 16:30:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Problem-giving-a-unity-datastore-ESXi-host-access-and-I-think/m-p/2902551#M281013</guid>
      <dc:creator>rswartz</dc:creator>
      <dc:date>2022-04-05T16:30:18Z</dc:date>
    </item>
    <item>
      <title>vCenter Server v.7 Can't connect to a VASA provider on a Dell EMC Unity array</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vCenter-Server-v-7-Can-t-connect-to-a-VASA-provider-on-a-Dell/m-p/2862040#M92272</link>
      <description>&lt;P&gt;The vCenter and Hosts of the environment are all up to date.&amp;nbsp; It's VCSA version 7.0.2. The vCenter CA manager mode is the default (I think, the vpxd.certmgmt.mode value is set to vmca so...). When I go to add the storage provider however I'm given an error:&lt;/P&gt;&lt;P&gt;"A problem was encountered while provisioning a VMware Certificate Authority (VMCA) signed certificate for the provider."&lt;/P&gt;&lt;P&gt;I tried renewing the hosts certificates to no avail. Anyone know what might be going wrong here or what I should try next?&lt;/P&gt;&lt;P&gt;Picture attached&lt;/P&gt;</description>
      <pubDate>Fri, 13 Aug 2021 20:23:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vCenter-Server-v-7-Can-t-connect-to-a-VASA-provider-on-a-Dell/m-p/2862040#M92272</guid>
      <dc:creator>rswartz</dc:creator>
      <dc:date>2021-08-13T20:23:47Z</dc:date>
    </item>
    <item>
      <title>Re: Changing vCenter 7.0 from tiny to small for VCSA HA compatibility</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Changing-vCenter-7-0-from-tiny-to-small-for-VCSA-HA/m-p/2862036#M43821</link>
      <description>&lt;P&gt;Looks like I just needed to up the vCenters VM vCPUs to 4. It seems to be working fine now.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Aug 2021 19:43:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Changing-vCenter-7-0-from-tiny-to-small-for-VCSA-HA/m-p/2862036#M43821</guid>
      <dc:creator>rswartz</dc:creator>
      <dc:date>2021-08-13T19:43:44Z</dc:date>
    </item>
    <item>
      <title>Changing vCenter 7.0 from tiny to small for VCSA HA compatibility</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Changing-vCenter-7-0-from-tiny-to-small-for-VCSA-HA/m-p/2861511#M43797</link>
      <description>&lt;P&gt;I'm looking to change my demo environments VCSA from a tiny configuration to a small one. I need to do this because having it be at least small is a prerequisite for VCSA HA.&lt;/P&gt;&lt;P&gt;I know there is a thread already for changing the disk space for a vCenter Server (&lt;A href="https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-size-changing/td-p/493584" target="_blank"&gt;https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-size-changing/td-p/493584&lt;/A&gt;) , mostly consisting of links to this kb page (&lt;A href="https://kb.vmware.com/s/article/2145603" target="_blank"&gt;https://kb.vmware.com/s/article/2145603&lt;/A&gt;). I'm not sure if this is enough to actually make the VCSA HA compatible, or if it will also need more CPUs or perhaps some internal code change.&lt;/P&gt;&lt;P&gt;Does anyone know if this is enough and if its not what else I would need to do?&lt;/P&gt;</description>
      <pubDate>Tue, 10 Aug 2021 18:12:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Changing-vCenter-7-0-from-tiny-to-small-for-VCSA-HA/m-p/2861511#M43797</guid>
      <dc:creator>rswartz</dc:creator>
      <dc:date>2021-08-10T18:12:21Z</dc:date>
    </item>
  </channel>
</rss>

