<?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>danituga7 Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>danituga7 Tracker</description>
    <pubDate>Sat, 25 Nov 2023 13:13:55 GMT</pubDate>
    <dc:date>2023-11-25T13:13:55Z</dc:date>
    <item>
      <title>ESXi Host can't format new SSDs</title>
      <link>https://communities.vmware.com/t5/Storage-Performance/ESXi-Host-can-t-format-new-SSDs/m-p/2996834#M5602</link>
      <description>&lt;P&gt;Hello together&lt;/P&gt;&lt;P&gt;I have an ESXi cluster consisting of two DL560 G9. I have been able to take 12 SSDs from an HP 3PAR system, which I have now installed in the first disk bay of the respective hosts (6 per host). The SSDs are being recognized, but I cannot format them. When I try to format them with VMFS5/6, I get the following error:&lt;/P&gt;&lt;P&gt;An error occurred during host configuration: . Operation failed, diagnostics report: Unable to create Filesystem, please see VMkernel log for more details: Failed to check device /dev/disks/naa.XXX capable of ATS&lt;/P&gt;&lt;P&gt;I have worked through the instructions in the following articles, but I still get the same error:&lt;BR /&gt;&lt;A href="https://kb.vmware.com/s/article/1036609" target="_blank"&gt;https://kb.vmware.com/s/article/1036609&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://kb.vmware.com/s/article/1014953" target="_blank"&gt;https://kb.vmware.com/s/article/1014953&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://kb.vmware.com/s/article/2146451" target="_blank"&gt;https://kb.vmware.com/s/article/2146451&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://kb.vmware.com/s/article/1033665" target="_blank"&gt;https://kb.vmware.com/s/article/1033665&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://kb.vmware.com/s/article/83249" target="_blank"&gt;https://kb.vmware.com/s/article/83249&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://vmware-forum.de/viewtopic.php?f=40&amp;amp;t=32173" target="_blank"&gt;https://vmware-forum.de/viewtopic.php?f=40&amp;amp;t=32173&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I also noticed that all new disks in the ESXi host under "Configure\Storage Devices" have LUN 0.&lt;/P&gt;&lt;P&gt;Here are some outputs regarding the disks:&lt;/P&gt;&lt;P&gt;Command:&lt;BR /&gt;esxcli storage core device vaai status get&lt;BR /&gt;Output:&lt;BR /&gt;naa.XXX&lt;BR /&gt;VAAI Plugin Name:&lt;BR /&gt;ATS Status: unsupported&lt;BR /&gt;Clone Status: unsupported&lt;BR /&gt;Zero Status: unsupported&lt;BR /&gt;Delete Status: supported&lt;BR /&gt;Ex Clone Status: unsupported&lt;/P&gt;&lt;P&gt;Command:&lt;BR /&gt;esxcli storage core device list&lt;BR /&gt;Output:&lt;BR /&gt;naa.XXX&lt;BR /&gt;Display Name: Local SAMSUNG Disk (naa.XXX)&lt;BR /&gt;Has Settable Display Name: true&lt;BR /&gt;Size: 1831420&lt;BR /&gt;Device Type: Direct-Access&lt;BR /&gt;Multipath Plugin: NMP&lt;BR /&gt;Devfs Path: /vmfs/devices/disks/naa.XXX&lt;BR /&gt;Vendor: SAMSUNG&lt;BR /&gt;Model: AREA1920S5xnNTRI&lt;BR /&gt;Revision: 3P01&lt;BR /&gt;SCSI Level: 6&lt;BR /&gt;Is Pseudo: false&lt;BR /&gt;Status: on&lt;BR /&gt;Is RDM Capable: true&lt;BR /&gt;Is Local: true&lt;BR /&gt;Is Removable: false&lt;BR /&gt;Is SSD: true&lt;BR /&gt;Is VVOL PE: false&lt;BR /&gt;Is Offline: false&lt;BR /&gt;Is Perennially Reserved: false&lt;BR /&gt;Queue Full Sample Size: 0&lt;BR /&gt;Queue Full Threshold: 0&lt;BR /&gt;Thin Provisioning Status: yes&lt;BR /&gt;Attached Filters:&lt;BR /&gt;VAAI Status: unsupported&lt;BR /&gt;Other UIDs: vml.XXX&lt;BR /&gt;Is Shared Clusterwide: false&lt;BR /&gt;Is SAS: true&lt;BR /&gt;Is USB: false&lt;BR /&gt;Is Boot Device: false&lt;BR /&gt;Device Max Queue Depth: 1007&lt;BR /&gt;No of outstanding IOs with competing worlds: 32&lt;BR /&gt;Drive Type: unknown&lt;BR /&gt;RAID Level: unknown&lt;BR /&gt;Number of Physical Drives: unknown&lt;BR /&gt;Protection Enabled: false&lt;BR /&gt;PI Activated: false&lt;BR /&gt;PI Type: 0&lt;BR /&gt;PI Protection Mask: NO PROTECTION&lt;BR /&gt;Supported Guard Types: NO GUARD SUPPORT&lt;BR /&gt;DIX Enabled: false&lt;BR /&gt;DIX Guard Type: NO GUARD SUPPORT&lt;BR /&gt;Emulated DIX/DIF Enabled: true&lt;/P&gt;</description>
      <pubDate>Wed, 22 Nov 2023 15:23:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Storage-Performance/ESXi-Host-can-t-format-new-SSDs/m-p/2996834#M5602</guid>
      <dc:creator>danituga7</dc:creator>
      <dc:date>2023-11-22T15:23:24Z</dc:date>
    </item>
    <item>
      <title>VMware Horizon - force Blast h.264 codec with high color accuracy (YUV 4:4:4)</title>
      <link>https://communities.vmware.com/t5/VMware-Horizon-Discussions/VMware-Horizon-force-Blast-h-264-codec-with-high-color-accuracy/m-p/2951491#M17633</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;I have a Horizon 8 environment with NVIDIA Tesla T4 cards, where lots of BYOD (Windows 10/11 + Mac OS), Windows 10 Clients (domain joined) and Linux ThinClients connect to. The virtual machines are installed with Windows 10 (LTSC 2019)&lt;/P&gt;&lt;P&gt;At the moment we are using the Blast protocol with h.264 coded (YUV 4:2:0). I am searching for a global setting to enforce YUV 4:4:4 on the Blast protocol. I tried the VMware Blast settings from the ADMX templates, but the high color accuracy setting only enables the setting - it won't enforce it.&lt;/P&gt;&lt;P&gt;Could it maybe be possible to disable YUV 4:2:0?&lt;/P&gt;&lt;P&gt;Thank you and kind regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 07:03:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Horizon-Discussions/VMware-Horizon-force-Blast-h-264-codec-with-high-color-accuracy/m-p/2951491#M17633</guid>
      <dc:creator>danituga7</dc:creator>
      <dc:date>2023-01-30T07:03:26Z</dc:date>
    </item>
  </channel>
</rss>

