<?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>kjdfhaueiase Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>kjdfhaueiase Tracker</description>
    <pubDate>Tue, 21 Nov 2023 05:17:54 GMT</pubDate>
    <dc:date>2023-11-21T05:17:54Z</dc:date>
    <item>
      <title>Re: Slow boot time after upgrading to ESXI 7 from 6.7 - hang on "mw_satp_alua loaded successful</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Slow-boot-time-after-upgrading-to-ESXI-7-from-6-7-hang-on-quot/m-p/2943523#M285283</link>
      <description>&lt;P&gt;Everyone on this thread should read this KB.&lt;BR /&gt;&lt;BR /&gt;I was seeing this problem but only on the server with a different brand USB drive.&lt;BR /&gt;&lt;BR /&gt;Are you seeing "All Paths Down" in your syslog.log? This means you lost access to the boot drive.&amp;nbsp; The problem in this KB could be the culprit. The step for me that was slowing down boot was setting up the swap file. This now makes perfect sense.&lt;BR /&gt;&lt;BR /&gt;What I find to be absolutely shocking: This has been a bug for 2 years. Not only is it not fixed, but they are carrying on as though it's no big deal because ESX still works. They are saying both "this is not a problem with the vmlinux driver", and "have a conversation with your USB/SD manufacturer about dropouts".&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;And now we're hearing booting from USB profiles is getting deprecated. Gee, is it because you don't know how to write a driver?&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://kb.vmware.com/s/article/83450" target="_blank" rel="noopener"&gt;https://kb.vmware.com/s/article/83450&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Dec 2022 23:29:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Slow-boot-time-after-upgrading-to-ESXI-7-from-6-7-hang-on-quot/m-p/2943523#M285283</guid>
      <dc:creator>kjdfhaueiase</dc:creator>
      <dc:date>2022-12-12T23:29:12Z</dc:date>
    </item>
    <item>
      <title>Re: NSX Manager install failing</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-Manager-install-failing/m-p/2939612#M15703</link>
      <description>&lt;P&gt;Got some help on the internet. Here's what I found out so far:&lt;BR /&gt;&lt;BR /&gt;-OVA deployment fails to set NSX manager password&lt;BR /&gt;-Log in with the most basic and dangerous set of credentials you can imagine at the console. Luckily, ssh is blocked until you change the password. That doesn't stop a lower role vsphere administrator from taking advantage if they want to; more of a problem in a larger organization&lt;BR /&gt;-Services do start after you've done that.&amp;nbsp; But the console login does seem different than the Web Login password.&lt;BR /&gt;&lt;BR /&gt;I'm sort of thinking of logging a security bug.&lt;BR /&gt;&lt;BR /&gt;I would appreciate you bringing this to their attention however I'm sure someone has done so already.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Nov 2022 09:01:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-Manager-install-failing/m-p/2939612#M15703</guid>
      <dc:creator>kjdfhaueiase</dc:creator>
      <dc:date>2022-11-21T09:01:20Z</dc:date>
    </item>
    <item>
      <title>Re: NSX Manager install failing</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-Manager-install-failing/m-p/2939604#M15702</link>
      <description>&lt;P&gt;Looking at the name of the download, it seems you are correct.&lt;BR /&gt;&lt;BR /&gt;Unfortunately, the only 3 downloads I see for "unified appliance" are 3.2 on the VMUG download page; is one of the 3.1 bundles good?&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;DIV&gt;&lt;PRE&gt;File: nsx-lcp-3.1.2.0.0.17884003-rhel77_x86_64-le.tar.gz
Size: 59 MB
File: nsx-lcp-3.1.2.0.0.17884003-rhel79_x86_64-le.tar.gz
Size: 62 MB
File: nsx-lcp-3.1.2.0.0.17884003-rhel82_x86_64-le.tar.gz
Size: 60 MB
File: nsx-lcp-3.1.2.17884003-baremetal-server-win32_vs2017-le.zip
Size: 115 MB
File: nsx-edge-3.2.0.1.0.19232600-le.iso
Size: 2 GB
File: nsx-edge-3.2.0.1.0.19232600-le.ova
Size: 2 GB
File: nsx-lcp-3.2.0.1.0.19232595-baremetal-container-rhel76_x86_64-le.tar.gz
Size: 69 MB
File: nsx-lcp-3.2.0.1.0.19232595-baremetal-container-rhel77_x86_64-le.tar.gz
Size: 66 MB
File: nsx-lcp-3.2.0.1.0.19232595-baremetal-container-rhel78_x86_64-le.tar.gz
Size: 66 MB
File: nsx-lcp-3.2.0.1.0.19232595-baremetal-server-linux64-bionic_amd64-le.tar.gz
Size: 84 MB
File: nsx-lcp-3.2.0.1.0.19232595-baremetal-server-linux64-sles12sp3-le.tar.gz
Size: 71 MB
File: nsx-lcp-3.2.0.1.0.19232595-baremetal-server-linux64-sles12sp4-le.tar.gz
Size: 69 MB
File: nsx-lcp-3.2.0.1.0.19232595-baremetal-server-rhel76_x86_64-le.tar.gz
Size: 69 MB
File: nsx-lcp-3.2.0.1.0.19232595-baremetal-server-rhel77_x86_64-le.tar.gz
Size: 66 MB
File: nsx-lcp-3.2.0.1.0.19232595-baremetal-server-rhel78_x86_64-le.tar.gz
Size: 66 MB
File: nsx-lcp-3.2.0.1.0.19232595-baremetal-server-rhel79_x86_64-le.tar.gz
Size: 69 MB
File: nsx-lcp-3.2.0.1.0.19232595-baremetal-server-rhel80_x86_64-le.tar.gz
Size: 67 MB
File: nsx-lcp-3.2.0.1.0.19232595-baremetal-server-rhel83_x86_64-le.tar.gz
Size: 67 MB
File: nsx-lcp-3.2.0.1.0.19232595-esx65-le.zip
Size: 31 MB
File: nsx-lcp-3.2.0.1.0.19232595-esx67-le.zip
Size: 31 MB
File: nsx-lcp-3.2.0.1.0.19232595-esx70-le.zip
Size: 45 MB
File: nsx-lcp-3.2.0.1.0.19232595-linux64-bionic_amd64-le.tar.gz
Size: 84 MB
File: nsx-lcp-3.2.0.1.0.19232595-linux64-focal_amd64-le.tar.gz
Size: 84 MB
File: nsx-lcp-3.2.0.1.0.19232595-rhel79_x86_64-le.tar.gz
Size: 69 MB
File: nsx-lcp-3.2.0.1.0.19232595-rhel82_x86_64-le.tar.gz
Size: 67 MB
File: nsx-lcp-3.2.0.19232595-baremetal-server-win32_vs2017-le
Size: 112 MB
File: nsx-unified-appliance-3.2.0.1.0.19232597-le.ova
Size: 9 GB
File: nsx-unified-appliance-3.2.0.1.0.19232597-le.qcow2
Size: 12 GB
File: nsx-unified-appliance-secondary-3.2.0.1.0.19232597-le.qcow2
Size: 193 KB
File: VMware-CC-upgrade-bundle-3.2.0.1.0.19232594-le.mub
Size: 6 GB
File: VMware-NSX-edge-3.2.0.1.0.19232600-le.nub
Size: 2 GB
File: VMware-NSX-upgrade-bundle-3.2.0.1.0.19232594-le.mub
Size: 8 GB
File: nsx-lcp-3.2.0.1.0.19232595-baremetal-server-ubuntu-xenial_amd64-le.tar.gz
Size: 84 MB
File: nsx-lcp-3.2.0.19232595-baremetal-server-win32_vs2017-le.zip
Size: 112 MB &lt;/PRE&gt;&lt;/DIV&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Mon, 21 Nov 2022 08:18:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-Manager-install-failing/m-p/2939604#M15702</guid>
      <dc:creator>kjdfhaueiase</dc:creator>
      <dc:date>2022-11-21T08:18:02Z</dc:date>
    </item>
    <item>
      <title>Re: NSX Manager install failing</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-Manager-install-failing/m-p/2938476#M15684</link>
      <description>&lt;P&gt;I am sort of surprised not to see any responses as this seems like something everyone would hit.&lt;BR /&gt;&lt;BR /&gt;Are people at the point where they have a pattern of working around these issues and it's well known? Maybe downloading the previous version of NSX?&lt;BR /&gt;&lt;BR /&gt;I am pretty surprised how hard it is to get this OVA to deploy.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Nov 2022 04:46:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-Manager-install-failing/m-p/2938476#M15684</guid>
      <dc:creator>kjdfhaueiase</dc:creator>
      <dc:date>2022-11-16T04:46:46Z</dc:date>
    </item>
    <item>
      <title>NSX Manager install failing</title>
      <link>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-Manager-install-failing/m-p/2937785#M15671</link>
      <description>&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P class=""&gt;Using nsx-unified-appliance-3.2.0.1.0.19232597-le.ova ...&lt;/P&gt;&lt;P class=""&gt;It took an exact combination of datastore2, medium size, thick provision lazy zeroed to even get the VM to deploy without saying it could not take the OVF parameters.&lt;/P&gt;&lt;P class=""&gt;Unfortunately booting showed an error as the very first line, then a failure to accept any of the passwords from the OVF ....&lt;BR /&gt;setting root password failed (use default)&lt;BR /&gt;setting local administrator password failed (use default)&lt;BR /&gt;setting audit password failed (user is disabled)&lt;/P&gt;&lt;P class=""&gt;which of course resulted in "use default". I trust and hope VMware does not publish that lol.&lt;/P&gt;&lt;P class=""&gt;what secret landmines should I avoid?&lt;/P&gt;&lt;P class=""&gt;Machine pings but....&lt;/P&gt;&lt;P class=""&gt;&lt;EM&gt;nmap nsxmanager Starting Nmap 7.80 ( &lt;/EM&gt;&lt;A class="" href="https://nmap.org" target="_blank" rel="noopener nofollow ugc"&gt;&lt;EM&gt;https://nmap.org&lt;/EM&gt;&lt;/A&gt;&lt;EM&gt; ) at 2022-11-09 15:05 JSTNote: Host seems down. If it is really up, but blocking our ping probes, try -PnNmap done: 1 IP address (0 hosts up) scanned in 3.15 seconds&lt;BR /&gt;&lt;/EM&gt;&lt;BR /&gt;So looks like no services running either.&lt;BR /&gt;Attempting login at the console failed.&lt;BR /&gt;&lt;BR /&gt;vCenter&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN class=""&gt;7.0.3 &lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN class=""&gt;Build:&lt;/SPAN&gt; &lt;SPAN class=""&gt;20395099&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN class=""&gt;ESX&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; VMware ESXi, 7.0.3, 20328353&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Hardware:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN class=""&gt;Processor Type:&lt;/SPAN&gt; &lt;SPAN class=""&gt;&lt;SPAN&gt;Intel(R) Xeon(R) W-3275M CPU @ 2.50GHz&lt;/SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN class=""&gt;Logical Processors:&lt;/SPAN&gt; &lt;SPAN class=""&gt;&lt;SPAN&gt;56&lt;/SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN class=""&gt;NICs:&lt;/SPAN&gt; &lt;SPAN class=""&gt;&lt;SPAN&gt;3&lt;/SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN class=""&gt;Virtual Machines:&lt;/SPAN&gt; &lt;SPAN class=""&gt;&lt;SPAN&gt;18&lt;/SPAN&gt; &lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN class=""&gt;CPU: Using 2.59 out of 68.83 Ghz&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;Memory Using 108.89 GB out of 1.5 TB&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;Storage: Used 3.89 TB out of 13.97 TB (local storage)&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;Attaching VM log. Not sure what vsphere log I should attach; however, from the vcenter perspective, the deployment seemed to have succeeded.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 11 Nov 2022 08:27:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-NSX-Discussions/NSX-Manager-install-failing/m-p/2937785#M15671</guid>
      <dc:creator>kjdfhaueiase</dc:creator>
      <dc:date>2022-11-11T08:27:19Z</dc:date>
    </item>
    <item>
      <title>Re: "Resource Deadlock Avoided"  - A cautionary tale...</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/quot-Resource-Deadlock-Avoided-quot-A-cautionary-tale/m-p/2937784#M180093</link>
      <description>&lt;P&gt;The UUID is accessible.&lt;BR /&gt;Apple's API is unstable&lt;BR /&gt;VMware wants to work on apple, and didn't use the UUID instead of the drive manufacturer, then they completely screwed up on a support case related to this.&lt;BR /&gt;&lt;BR /&gt;No one is without fault. Including us.&lt;BR /&gt;&lt;BR /&gt;Fool me once...&lt;/P&gt;</description>
      <pubDate>Fri, 11 Nov 2022 08:10:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/quot-Resource-Deadlock-Avoided-quot-A-cautionary-tale/m-p/2937784#M180093</guid>
      <dc:creator>kjdfhaueiase</dc:creator>
      <dc:date>2022-11-11T08:10:34Z</dc:date>
    </item>
    <item>
      <title>Re: NSX Manager is crashed and How do I uninstall the NSX manger on vCenter/Esxi Host</title>
      <link>https://communities.vmware.com/t5/Networking-Members/NSX-Manager-is-crashed-and-How-do-I-uninstall-the-NSX-manger-on/m-p/2912117#M153</link>
      <description>&lt;P&gt;What was the error message in the console when you attempted to boot ? It's hard to see what's failing in the boot process.&lt;BR /&gt;&lt;BR /&gt;Also, In theme with the others answering questions you didn't ask &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&amp;nbsp; It's not usually necessary for scaling to have multiple nsx managers unless you have a huge deployment, unlike the NSX network controllers. You will always need a few of those.&lt;BR /&gt;&lt;BR /&gt;Therefore you need to do your own redundancy. &lt;A href="https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.4/com.vmware.nsx.upgrade.doc/GUID-2A75A102-518D-4D6C-B23D-877C421B1536.html" target="_blank"&gt;https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.4/com.vmware.nsx.upgrade.doc/GUID-2A75A102-518D-4D6C-B23D-877C421B1536.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Snapshots and backups are also of course a good thing. For the future that is.&lt;BR /&gt;&lt;BR /&gt;My guess is that you're trying to get NSX manager removed so you can get a "working one" going again. Risky, but if you can access the drive through ubuntu, you can also access the database, etc. It would be unsupported, but perhaps grabbing that and restoring it into the working NSX manager could work for you. It all depends on how much effort you put into setting up NSX as to how important it is to recover the configuration.&lt;BR /&gt;&lt;BR /&gt;Bummer that happened!&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jun 2022 09:50:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Networking-Members/NSX-Manager-is-crashed-and-How-do-I-uninstall-the-NSX-manger-on/m-p/2912117#M153</guid>
      <dc:creator>kjdfhaueiase</dc:creator>
      <dc:date>2022-06-01T09:50:33Z</dc:date>
    </item>
    <item>
      <title>Re: Recovered VM's - No network</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Recovered-VM-s-No-network/m-p/2912104#M42628</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; We are seeing some VMs randomly dropped off the network as well on 6.7.&amp;nbsp; I am not sure what triggers it but sometimes it happens after a vmotion.&amp;nbsp;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; In fact, we vmotioned the VM to 7 machines in our cluster and continued to ping the VM. On 4 out of 7 we got ping; the other 3 no dice.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Yet later one of the machines we had successful testing on also dropped the machine from the network.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; DRS is on... and backup recovery automation is happening too ( I can see snapshots occurring in the events pane).&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; This machine is linux while the other machines are windows based.&amp;nbsp; We were going to move the machine to a non DRS cluster but we know now it happens without vmotioning.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; What didn't work:&lt;BR /&gt;&lt;BR /&gt;-Upgrading hardware version of the VM&lt;BR /&gt;-Updating NIC from e1000 to VMNET3&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; We are at a loss at how to keep this machine up.&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Another thing we noticed which may or may not be related: Someone who is given explicit rights to the machine (and no other rights) can not solve the problem with a reboot or restart; however, Cluster admins CAN remedy the problem with a reboot. So there could be some permissioning failures related to what's happening in the background. That's just a hunch, as nothing is showing up in the VM's log.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jun 2022 07:43:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Recovered-VM-s-No-network/m-p/2912104#M42628</guid>
      <dc:creator>kjdfhaueiase</dc:creator>
      <dc:date>2022-06-01T07:43:57Z</dc:date>
    </item>
    <item>
      <title>Re: Can anyone suggest a PCIE USB3 controller that is compatible with esxi?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Can-anyone-suggest-a-PCIE-USB3-controller-that-is-compatible/m-p/2910458#M281821</link>
      <description>&lt;P&gt;I would love to see an answer to this.&lt;BR /&gt;&lt;BR /&gt;The &lt;A title="HW compatibility guide" href="https://web.archive.org/web/20220309070931/https://www.vmware.com/resources/compatibility/pdf/vi_io_guide.pdf" target="_self"&gt;100s of pages long&lt;/A&gt; HW compatibility guide does not have the word "USB" in the entire document.&lt;BR /&gt;(note the link is to the web archives version since VMware didn't see fit to keep this online).&lt;BR /&gt;&lt;BR /&gt;I'm running a mac hypervisor but it has PCI slots so I can expand. If I choose wisely, and use the force.&lt;/P&gt;</description>
      <pubDate>Sun, 22 May 2022 09:11:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Can-anyone-suggest-a-PCIE-USB3-controller-that-is-compatible/m-p/2910458#M281821</guid>
      <dc:creator>kjdfhaueiase</dc:creator>
      <dc:date>2022-05-22T09:11:24Z</dc:date>
    </item>
    <item>
      <title>Re: Slow upload speed when using vmxnet3 with macOS Mojave</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Slow-upload-speed-when-using-vmxnet3-with-macOS-Mojave/m-p/2907860#M178469</link>
      <description>&lt;P&gt;I too am curious if you solved this. However, I have discovered something pretty interesting.&lt;BR /&gt;&lt;BR /&gt;The Mac OS VMware tools (darwin.iso) does NOT include the VMXNET3 driver. In fact, it only contains the graphics driver and the uninstaller. It is extremely light (2.7Mb!) compared to the other vmware tools sets.&lt;BR /&gt;&lt;BR /&gt;The only vmxnet3 driver as far as I can tell comes from Apple, and its copyright date is 2017. I have dug through all the darwin.iso files and I have attached the packageinfo.&lt;BR /&gt;&lt;BR /&gt;Who created the driver is unclear to me, and who is responsible for bug fixes is also unclear.&lt;BR /&gt;&lt;BR /&gt;I am getting "decent" speeds but not "excellent" speeds. The kind of speeds I'd impose on VMware users if... you know.. I wanted to sell more hardware instead of letting them concentrate multiple Mac OS instances onto a &lt;EM&gt;single&lt;/EM&gt; apple hardware device.&lt;BR /&gt;&lt;BR /&gt;But even assuming the best intentions, the support of this driver is unclear.&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screen Shot 2022-05-07 at 8.52.58 PM.png" style="width: 999px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/95164iA7C392BED08CA033/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="Screen Shot 2022-05-07 at 8.52.58 PM.png" alt="Screen Shot 2022-05-07 at 8.52.58 PM.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 08 May 2022 01:09:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Slow-upload-speed-when-using-vmxnet3-with-macOS-Mojave/m-p/2907860#M178469</guid>
      <dc:creator>kjdfhaueiase</dc:creator>
      <dc:date>2022-05-08T01:09:18Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to create new virtual switch message when I try to create a new vSwitch</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Failed-to-create-new-virtual-switch-message-when-I-try-to-create/m-p/2906433#M281311</link>
      <description>&lt;P&gt;Thanks for the solution.&lt;BR /&gt;&lt;BR /&gt;I think honestly it's pathetic that we have to do this. When the cloud is looming and on-prem data centers are going to soon be a thing of the past, why create this abysmal user experience where you can only do things from the CLI?&lt;/P&gt;</description>
      <pubDate>Thu, 28 Apr 2022 11:07:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Failed-to-create-new-virtual-switch-message-when-I-try-to-create/m-p/2906433#M281311</guid>
      <dc:creator>kjdfhaueiase</dc:creator>
      <dc:date>2022-04-28T11:07:16Z</dc:date>
    </item>
    <item>
      <title>Re: "Resource Deadlock Avoided"  - A cautionary tale...</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/quot-Resource-Deadlock-Avoided-quot-A-cautionary-tale/m-p/2894952#M177599</link>
      <description>&lt;P&gt;About .. 7? Years ago VMware fired their entire engineering staff for Fusion and workstation and moved the effort to India. It was an overnight thing, so even if you disagree with the business of migrating the work, there could not have been a reasonable transition plan.&lt;BR /&gt;&lt;BR /&gt;So... If you think about the quality of fusion lately, with this bug, fusion kind of "losing" the vmdk file in the same folder, spotty support for Metal, and a bunch of other problems you've no doubt worked around over past 7 years... do you think this is a coincidence?&lt;BR /&gt;&lt;BR /&gt;I don't think it's reasonable to ask 3rd world people to solve first world problems. Having to buy a new hard drive to make your software work- Sorry but that's a 1st world problem.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://www.loopinsight.com/2016/01/28/vmware-abruptly-fires-fusion-dev-team-outsources-to-china/" target="_blank"&gt;https://www.loopinsight.com/2016/01/28/vmware-abruptly-fires-fusion-dev-team-outsources-to-china/&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Feb 2022 06:01:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/quot-Resource-Deadlock-Avoided-quot-A-cautionary-tale/m-p/2894952#M177599</guid>
      <dc:creator>kjdfhaueiase</dc:creator>
      <dc:date>2022-02-23T06:01:21Z</dc:date>
    </item>
    <item>
      <title>ssageRe: "Resource Deadlock Avoided"  - A cautionary tale...</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/quot-Resource-Deadlock-Avoided-quot-A-cautionary-tale/m-p/2886894#M177056</link>
      <description>&lt;P&gt;Really sorry- The support case dragged on for a long time. Months. They never said anything about a fix but I missed a message about a workaround discussion... and then they closed the case.&lt;BR /&gt;&lt;BR /&gt;I am now in a different support case about a windows guest crashing only on Big Sur (works great in Catelina) due to Metal. The support engineer asked me to turn on OpenCL rendering in Fusion 12 through the VMX.&lt;BR /&gt;&lt;BR /&gt;If you're with the in kids, you know that VMware removed non-metal rendering in Fusion 12. So .. so much for a qualified support staff.&lt;BR /&gt;&lt;BR /&gt;I think VMware has moved on to M1 for fusion, and us recent customers are screwed.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jan 2022 05:42:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/quot-Resource-Deadlock-Avoided-quot-A-cautionary-tale/m-p/2886894#M177056</guid>
      <dc:creator>kjdfhaueiase</dc:creator>
      <dc:date>2022-01-07T05:42:40Z</dc:date>
    </item>
    <item>
      <title>Re: "Resource Deadlock Avoided"  - A cautionary tale...</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/quot-Resource-Deadlock-Avoided-quot-A-cautionary-tale/m-p/2843327#M173805</link>
      <description>&lt;P&gt;I have a support case opened now; Will keep you posted.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Apr 2021 14:05:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/quot-Resource-Deadlock-Avoided-quot-A-cautionary-tale/m-p/2843327#M173805</guid>
      <dc:creator>kjdfhaueiase</dc:creator>
      <dc:date>2021-04-22T14:05:17Z</dc:date>
    </item>
    <item>
      <title>Re: VMware Fusion 12 running on Apple Silicon</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/VMware-Fusion-12-running-on-Apple-Silicon/m-p/2809909#M170110</link>
      <description>&lt;P&gt;Of course it is a reasonable response.&amp;nbsp; So now we are down to what would be a reasonable expectation.&lt;BR /&gt;&lt;BR /&gt;The VMware team has ESXi running on ARM and had been working on that for a long time to get so far. This means that critical monitor code - at least for type 1 hypervisors- is code complete.&lt;BR /&gt;&lt;BR /&gt;In theory, the Fusion Type 2 hypervisor (depends on Mac OS to interface with much of the hardware) is mostly a recompile, but clearly VMware is working hard on this.&lt;BR /&gt;&lt;BR /&gt;Now the most important question: Given that Apple has full support for running Intel instructions via Rosetta 2 (which most likely CANT be reused by VMware)&amp;nbsp; AND Geekbench numbers being posted on M1 machines are proving that &lt;EM&gt;the M1 chip is emulating x86 instructions FASTER than Apple's own most powerful Macbooks...&lt;/EM&gt; Will VMware support x86 VMs? Which in theory unlocks the CPU and GPU performance of the M1 for gamers (now that there is no bootcamp)?&lt;BR /&gt;&lt;BR /&gt;Well. Methinks they will at least try.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Nov 2020 02:53:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/VMware-Fusion-12-running-on-Apple-Silicon/m-p/2809909#M170110</guid>
      <dc:creator>kjdfhaueiase</dc:creator>
      <dc:date>2020-11-17T02:53:56Z</dc:date>
    </item>
    <item>
      <title>Re: Email notification using Google account "gmail"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Email-notification-using-Google-account-quot-gmail-quot/m-p/2746620#M90584</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I almost feel like you're trying to torment other users by posting the same erroneous information, so I'll un-torment them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The gmail settings above are useless unless you know where to type them. They are buried in "Advanced Settings".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is an interface for typing the settings by "key" (they are key/value pairs); however, the interface is &lt;EM&gt;broken&lt;/EM&gt; so you will have to scroll to page 65. Not kidding.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is how to get to the advanced settings, from the html5 client:&lt;/P&gt;&lt;P&gt;1) from the template or cluster views, select the vcenter on the left hand side. This allows you to enter vcenter settings such as email.&lt;BR /&gt;2) On the left, after you have entered the email server in the General settings,&amp;nbsp; click "Advanced Settings".&lt;/P&gt;&lt;P&gt;3) On the top right click the box that says "edit settings" (on my browser this is displaying over a couple other words so don't freak out if you see that)&lt;/P&gt;&lt;P&gt;4) There are 70 pages of settings today. Click the number 70, and then click the left arrow a few times to find the mail settings on page 65. (even this is not easy as the left arrow will keep moving with each scroll).&lt;BR /&gt;5) Here you can adjust the port, password, and user name for the email sends using gmail settings above or other ones.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These are the settings:&lt;/P&gt;&lt;P&gt;mail.smtp.password&lt;/P&gt;&lt;P&gt;mail.smtp.port&lt;/P&gt;&lt;P&gt;mail.smtp.username &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my screen shot you can see where I tried to type the key "mail.smtp.password" and failed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Enjoy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Screen Shot 2020-02-21 at 12.30.56 PM.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/17560i823C504487E6CF6F/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screen Shot 2020-02-21 at 12.30.56 PM.png" alt="Screen Shot 2020-02-21 at 12.30.56 PM.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Feb 2020 04:08:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Email-notification-using-Google-account-quot-gmail-quot/m-p/2746620#M90584</guid>
      <dc:creator>kjdfhaueiase</dc:creator>
      <dc:date>2020-02-21T04:08:21Z</dc:date>
    </item>
    <item>
      <title>Re: Email notification using Google account "gmail"</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Email-notification-using-Google-account-quot-gmail-quot/m-p/2746618#M90582</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you haven't figured it out yet, you can't.&lt;/P&gt;&lt;P&gt;Seems like the only way today to do this is with a dangerous open SMTP server- pretty big fail on vmware's part.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Feb 2020 01:50:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Email-notification-using-Google-account-quot-gmail-quot/m-p/2746618#M90582</guid>
      <dc:creator>kjdfhaueiase</dc:creator>
      <dc:date>2020-02-10T01:50:36Z</dc:date>
    </item>
    <item>
      <title>Re: Disable/Remove specific hardware fan alarm</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Disable-Remove-specific-hardware-fan-alarm/m-p/2181901#M29505</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The answer to this problem should be simple. Disable the fan alarm for this particular host.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since it is not getting detected correctly, the solution is to disable the alarm, or your host will have the "Check Engine Light" on at all times, blinding the administrator to &lt;EM&gt;real issues &lt;/EM&gt;that may have cropped up outside of the bogus fan alert.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is no way I see how this can be done for a single host, although I see you can do it at the vcenter level. The attached screen shot shows you how you can edit, and then disable the alarm. It would probably not be wise to disable this particular alarm for all the hosts in the vcenter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In our case we have a bad sensor, so I have to live with the check engine light, unfortunately. I am guessing I could probably right a script to constantly look for and disable the warning.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="CheckEngineLightDisable.JPG"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/13980iDE18D639C481CF2F/image-size/large?v=v2&amp;amp;px=999" role="button" title="CheckEngineLightDisable.JPG" alt="CheckEngineLightDisable.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Sep 2019 04:55:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Disable-Remove-specific-hardware-fan-alarm/m-p/2181901#M29505</guid>
      <dc:creator>kjdfhaueiase</dc:creator>
      <dc:date>2019-09-19T04:55:31Z</dc:date>
    </item>
    <item>
      <title>Re: Can't install VMware Tools on Windows 2012 Server R2 guest</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Player/Can-t-install-VMware-Tools-on-Windows-2012-Server-R2-guest/m-p/1407064#M16870</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am hitting this, and it's pathetic on VMware's part.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Because I'm required to install windows updates on 2012 before having vmware tools be able to update, I am blocked from using the vmware tools network driver to install windows updates. Using the vm is extremely cumbersome. This means the whole process takes over an hour.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I actually tried to create an iso that I can mount from ESX with some of the software on it but I bumped into this problem as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is a REALLY bad decision to not make vmware tools contain the Visual C++ executables. I realize there may be some newer features in tools that take advantage of advanced windows features, but a KEY point of vmware is being able to support older operating systems on new hardware.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is a complete failure of that mission.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Jun 2019 10:56:13 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Player/Can-t-install-VMware-Tools-on-Windows-2012-Server-R2-guest/m-p/1407064#M16870</guid>
      <dc:creator>kjdfhaueiase</dc:creator>
      <dc:date>2019-06-05T10:56:13Z</dc:date>
    </item>
    <item>
      <title>VM Desktop screens do not automatically resize when Workstation (or VMRC) application window "snaps" to full screen</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/VM-Desktop-screens-do-not-automatically-resize-when-Workstation/m-p/1869073#M111347</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This usability issue is not present on VMware Fusion.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I drag a running virtual machine window to the top of the Windows 10 (Host OS) screen, The workstation screen resizes itself, but the virtual machine doesn't reset its resolution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Somewhere there is a missing notification in Workstation that is not telling the virtual machine that it should change screen resolution (using vmware tools), &lt;EM&gt; but only when it snaps to a new size.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This ONLY happens when the screen "snaps" to a size by dragging it to an edge of the Host OS windows system. &lt;EM&gt;If you slowly drag each corner of the workstation application to the size you want, vmware tools gets notified and readjusts the size of the desktop&lt;/EM&gt; (Unless you disable that feature). This is also a problem with VMRC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are really only two conditions when this should not work:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) You have a low default video ram size in the VMX file (Virtual machine settings). This can be adjusted to 8Mb and you will have no problems&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) At some point you were running the virtual machine and it asked if you wanted to keep the virtual machine screen resolution from adjusting. This is especially possible if you are using Windows 10 and it tells you it's set your virtual machine to a custom scaling factor and it asks if you would like it to continue to do that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I actually do not like the custom scaling factor, however at the same time vmware tools is resetting the screen resolution which is what I want. So I leave that ON.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;None of these issues is present when I snap workstation to occupy all of my monitor and it's really annoying and actually not easily possible to right click on the virtual machine desktop and get it to size exactly to the size of my new window because VMware tools makes this match EXACTLY. Take the same exact VM and run it in fusion (mac product) and all this works perfectly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone who has a solid workaround to make this &lt;EM&gt;automatically happen when the workstation window snaps to full screen&lt;/EM&gt; ... you're a god.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 May 2019 01:46:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/VM-Desktop-screens-do-not-automatically-resize-when-Workstation/m-p/1869073#M111347</guid>
      <dc:creator>kjdfhaueiase</dc:creator>
      <dc:date>2019-05-24T01:46:11Z</dc:date>
    </item>
  </channel>
</rss>

