<?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>DerekShaw Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>DerekShaw Tracker</description>
    <pubDate>Tue, 21 Nov 2023 11:34:43 GMT</pubDate>
    <dc:date>2023-11-21T11:34:43Z</dc:date>
    <item>
      <title>Re: ESXI 6.7U2 ignores virtual machine swap location</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/ESXI-6-7U2-ignores-virtual-machine-swap-location/m-p/2968357#M45216</link>
      <description>&lt;P&gt;for anyone else using a stand-alone ESXi host... This is the first thing that half-worked with ESXi 7.0U3, BUT...&lt;STRONG&gt; I have only found a way to do it on a per-VM basis. I suspect the author of the question (PCPixel) got there in the end, too, but just didn't tell us. Lalegre spells it out in the troubleshooting -&amp;nbsp; I've just bundled it all in one place. I have been unable to find a way (or find anyone else who has found a way) to configure the host itself to have the VMs put their swap files any place other than its own host directory.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I say half-worked, because when the below is completed, it only moves one of the two .vswp files created at power on in each VM's host directory. Half a loaf is better than none! Still trying to prevent ESXi 7.0U3 creating a file with a name like this in the VM's host directory:&lt;/P&gt;&lt;P&gt;/vmfs/volumes/datastore0/vmx-VMNAME-e89b7c4137b860d2a496191ccaf49bcc2f7727d2-1.vswp&lt;/P&gt;&lt;P&gt;Chip in if you have any experience with actually getting this (stand-alone esxi 7.0u3, no vCenter) working as one would expect.&lt;/P&gt;&lt;P&gt;Assumptions:&lt;BR /&gt;- you can ssh to the esxi host and that you know how to use vi&lt;BR /&gt;- you have a vmfs volume suitable for your needs mounted as [SWAP_DATASTORE_NAME]&lt;BR /&gt;- you are using the web-ui interface to the stand-alone esxi host&lt;/P&gt;&lt;P class="lia-align-left"&gt;power-down the VM&lt;BR /&gt;This clickpath in the ESXI host's web UI (as of 2023-05-13):&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;virtual machines --&amp;gt; Rt Click [name of VM] to be modified --&amp;gt; edit settings&lt;BR /&gt;VM Options (button) --&amp;gt; Advanced --&amp;gt; scroll down&lt;BR /&gt;IN "Swap file location" --&amp;gt; Datastore specified by host (radio button)&lt;BR /&gt;Save (button)&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ESXi01.png" style="width: 717px;"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/101551iAD2C261F7E6B5CDB/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="ESXi01.png" alt="ESXi01.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Un-register the VM&lt;/P&gt;&lt;P&gt;in the esxi shell (logged on via ssh)&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;mkdir /vmfs/volumes/[SWAP_DATASTORE_NAME]/[VM_NAME]&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Next, edit &lt;FONT face="terminal,monaco"&gt;/vmfs/volumes/VMStorage_DATASTORE_NAME/[VM_HOST_DIR]/vmname.vmx&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;make sure this line is present (created by editing settings per above screen shot)&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;sched.swap.hostLocal = "enabled"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;remove this line (comment it out):&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;#sched.swap.derivedName = "/vmfs/volumes/VMStorage_DATASTORE_NAME/VM_NAME/VM_NAME-a8d4e531.vswp"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;add this line, making suitable substitutions:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;sched.swap.dir = "/vmfs/volumes/[SWAP_DATASTORE_NAME]/[VM_NAME]/"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;NB - this is the directory created above, no filename.&lt;BR /&gt;- this is a different variable than the one removed by comment, and must be manually typed into the .vmx file.&lt;/P&gt;&lt;P&gt;re-register the VM&lt;/P&gt;&lt;P&gt;-- have confirmed the same behaviour with esxi 6.&lt;/P&gt;</description>
      <pubDate>Tue, 16 May 2023 00:02:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/ESXI-6-7U2-ignores-virtual-machine-swap-location/m-p/2968357#M45216</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2023-05-16T00:02:08Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating Fusion to a new MacBook:  Time Machine and "Windows 7 x64.vmwarevm"</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Migrating-Fusion-to-a-new-MacBook-Time-Machine-and-quot-Windows/m-p/2817079#M171222</link>
      <description>&lt;P&gt;ah, no.&amp;nbsp; Emulation would be required to host x86 guests.&amp;nbsp; Arm guests would not need the extra translation layer.&lt;/P&gt;&lt;P&gt;&lt;A href="https://osxdaily.com/2020/12/04/how-install-rosetta-2-apple-silicon-mac/" target="_blank"&gt;https://osxdaily.com/2020/12/04/how-install-rosetta-2-apple-silicon-mac/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Dec 2020 01:43:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Migrating-Fusion-to-a-new-MacBook-Time-Machine-and-quot-Windows/m-p/2817079#M171222</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2020-12-15T01:43:59Z</dc:date>
    </item>
    <item>
      <title>Re: Best way to shrink a VMDK file (D Drive) of a VM ?</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Best-way-to-shrink-a-VMDK-file-D-Drive-of-a-VM/m-p/501834#M7197</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;after wrestling with a similar issue, for far too long (deriving from a P2V, originally badly-configured server 2012 R2 server), and working through several different methods, I eventually found success by paying $180 for casper server edition, creating a correctly-sized VMDK (120GB) and cloning the 60 GB of data from the 880GB vmdk (Dell OEM partition, recovery partition, and OS partition) to the new VMDK.&amp;nbsp; After a quick rename of the old and new VMDKs, I was booting up with the 120GB VMDK.&amp;nbsp; I estimate I spent about&amp;nbsp; 10x as much in (un-)billable time as the cost of casper.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unfortunately Casper Server Edition does not work with dynamic disks, so if you have a simple layout with already-existing dynamic disk(s), the method describe in reply 5 would probably work for you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Aug 2020 20:26:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Best-way-to-shrink-a-VMDK-file-D-Drive-of-a-VM/m-p/501834#M7197</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2020-08-07T20:26:44Z</dc:date>
    </item>
    <item>
      <title>Re: new esxi 6.7.0 host will not connect to the same nfs server the esxi 6.0.0 host it is replacing.  How to troubleshoot?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/new-esxi-6-7-0-host-will-not-connect-to-the-same-nfs-server-the/m-p/2244313#M218695</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;well, I don't know if it qualifies as an answer, but after upgrading the freebsd NFS server from 11.2p0 to 11.2p9 the esxi 6.7.0 host can now mount the NFS shares that I could previously mount only with esxi 6.0.0&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 09 Mar 2019 17:51:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/new-esxi-6-7-0-host-will-not-connect-to-the-same-nfs-server-the/m-p/2244313#M218695</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2019-03-09T17:51:08Z</dc:date>
    </item>
    <item>
      <title>Re: new esxi 6.7.0 host will not connect to the same nfs server the esxi 6.0.0 host it is replacing.  How to troubleshoot?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/new-esxi-6-7-0-host-will-not-connect-to-the-same-nfs-server-the/m-p/2244312#M218694</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;H6&gt;&lt;B&gt;ThompsG&lt;/B&gt; &lt;/H6&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;yes -- these are two different NFS servers being mounted from the same host (at slightly different times). It was a troubleshooting step to narrow the troubleshooting scope.&amp;nbsp; You can see a certain similarity in the way I set things up at different clients (in this case the .254.3 address is at my office), which makes it maybe not so obvious what I have done.&amp;nbsp; The .3 is mostly random chance, but fixed IPs typically get assigned in the first 50 addresses, and NFS servers typically get set up pretty early in the process.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After getting some much-needed sleep (and a weekend, when time demands are not so intense), I am going to try patching up the local NFS server (.42.3) to current freeBSD 11.2 levels ( I think it is p9), and if that doesn't work, then to 12.0pX.&amp;nbsp; I can do those without having to down the esxi box, and they are relatively reliable operations.&amp;nbsp; I'll post the results when I've done it. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ghettoVCB would normally run on sunday night, so I'm still withing normal "failure paramaters".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 09 Mar 2019 02:33:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/new-esxi-6-7-0-host-will-not-connect-to-the-same-nfs-server-the/m-p/2244312#M218694</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2019-03-09T02:33:35Z</dc:date>
    </item>
    <item>
      <title>new esxi 6.7.0 host will not connect to the same nfs server the esxi 6.0.0 host it is replacing.  How to troubleshoot?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/new-esxi-6-7-0-host-will-not-connect-to-the-same-nfs-server-the/m-p/2244310#M218692</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have seen many of the unanswered questions about esxi mysteriously not mounting NFS shares.&amp;nbsp; This one provides perhaps a chance to track down what is going on.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The situation:&amp;nbsp; I have built a new esxi 6.7.0 host to move some VMs to while we upgrade the hardware on a host currently running esxi 6.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The plan was simple, and I've done this numerous times before (with earlier versions of esxi) --&amp;nbsp; use a manual&amp;nbsp; ghettoVCB run to capture the VMs to the long-running NFS server then use cp and vmkfstools to move them on to the new box (running esxi 6.7.0). (ghettoVmotion....)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But the esxi 6.7.0 throws the maddeningly vague error&lt;/P&gt;&lt;P&gt;2019-03-07T03:44:12.632Z cpu7:2098551 opID=7457c6f4)NFS: 171: NFS mount 192.168.42.3:/somepool/esxi_backupstore0 failed: Unable to connect to NFS server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This NFS server is v3, FreeBSD 11.2 p0.&amp;nbsp; It is used every week by ghettoVCB to make copies of the VMs.&amp;nbsp; It also used to host the linux home dirs for the machines on the LAN ('til we virtualized that to a FreeBSD VM on the esxi host).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, off I go and find all the&amp;nbsp; variants of this problem (mostly unsolved).&amp;nbsp; Salient points -- no firewall on any of the 3 hosts, I can vmkping the NFS server, and netcat to it.&amp;nbsp; I can mount an NFS store on a different FreeBSD server (running 9.1 p0) from the esxi 6.7.0 box, across the internet via a VPN tunnel.&amp;nbsp; I can mount the FreeBSD 11.2 NFS store from linux boxes, (and obviously from the esxi 6.0.0 box).&amp;nbsp; NFS is all v3.&amp;nbsp; The exports on both NFS machines are virtually identical (no pun intended).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so, here are the vmkernel log excerpts showing the failing mount and the successful mounts. If anybody knows how to make these appear as code blocks, please let me know.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;esxi 6.7.0 failure on 192.168.42.3&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:43:40.836Z cpu0:2098551 opID=7457c6f4)World: 11942: VC opID b1067550 maps to vmkernel opID 7457c6f4&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:43:40.836Z cpu0:2098551 opID=7457c6f4)NFS: 160: Command: (mount) Server: (192.168.42.3) IP: (192.168.42.3) Path: (/somepool/esxi_backupstore0) Label: (backupstore0) Options: (None)&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:43:40.836Z cpu0:2098551 opID=7457c6f4)StorageApdHandler: 977: APD Handle be94838e-79e611ed Created with lock[StorageApd-0x430e2a0d6700]&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:43:40.836Z cpu0:2098551 opID=7457c6f4)CpuSched: 693: user latency of 2099586 RPC-tx-192.168.42.3.0.111 0 changed by 2098551 hostd-worker -6&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:43:40.837Z cpu0:2098551 opID=7457c6f4)SunRPC: 1099: Destroying world 0x200982&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:43:40.837Z cpu0:2098551 opID=7457c6f4)CpuSched: 693: user latency of 2099587 RPC-tx-192.168.42.3.3.245 0 changed by 2098551 hostd-worker -6&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:43:51.633Z cpu0:2098551 opID=7457c6f4)SunRPC: 3303: Synchronous RPC abort for client 0x4304551ec120 IP 192.168.42.3.3.245 proc 1 xid 0x2907a083 attempt 1 of 3&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:44:01.633Z cpu2:2098551 opID=7457c6f4)SunRPC: 3303: Synchronous RPC abort for client 0x4304551ec120 IP 192.168.42.3.3.245 proc 1 xid 0x2907a084 attempt 2 of 3&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:44:12.632Z cpu0:2098551 opID=7457c6f4)SunRPC: 3303: Synchronous RPC abort for client 0x4304551ec120 IP 192.168.42.3.3.245 proc 1 xid 0x2907a085 attempt 3 of 3&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:44:12.632Z cpu0:2098551 opID=7457c6f4)SunRPC: 1099: Destroying world 0x200983&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:44:12.632Z cpu7:2098551 opID=7457c6f4)StorageApdHandler: 1063: Freeing APD handle 0x430e2a0d6700 [be94838e-79e611ed]&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:44:12.632Z cpu7:2098551 opID=7457c6f4)StorageApdHandler: 1147: APD Handle freed!&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:44:12.632Z cpu7:2098551 opID=7457c6f4)NFS: 171: NFS mount 192.168.42.3:/somepool/esxi_backupstore0 failed: Unable to connect to NFS server.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;esxi 6.7.0 success on 192.168.254.3&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.012Z cpu2:2098619 opID=2a84b29f)World: 11942: VC opID b1067619 maps to vmkernel opID 2a84b29f&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.012Z cpu2:2098619 opID=2a84b29f)NFS: 160: Command: (mount) Server: (192.168.254.3) IP: (192.168.254.3) Path: (/otherpool/esxi_backupstore0) Label: (backupstore0) Options: (None)&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.012Z cpu2:2098619 opID=2a84b29f)StorageApdHandler: 977: APD Handle c02083a6-ef60d04d Created with lock[StorageApd-0x430e2a0d6700]&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.012Z cpu2:2098619 opID=2a84b29f)CpuSched: 693: user latency of 2099848 RPC-tx-192.168.254.3.0.111 0 changed by 2098619 hostd-worker -6&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.059Z cpu2:2098619 opID=2a84b29f)SunRPC: 1099: Destroying world 0x200a88&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.059Z cpu2:2098619 opID=2a84b29f)CpuSched: 693: user latency of 2099849 RPC-tx-192.168.254.3.2.216 0 changed by 2098619 hostd-worker -6&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.101Z cpu2:2098619 opID=2a84b29f)SunRPC: 1099: Destroying world 0x200a89&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.101Z cpu2:2098619 opID=2a84b29f)CpuSched: 693: user latency of 2099850 RPC-tx-192.168.254.3.0.111 0 changed by 2098619 hostd-worker -6&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.144Z cpu2:2098619 opID=2a84b29f)SunRPC: 1099: Destroying world 0x200a8a&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.144Z cpu2:2098619 opID=2a84b29f)CpuSched: 693: user latency of 2099851 RPC-tx-192.168.254.3.8.1 0 changed by 2098619 hostd-worker -6&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.212Z cpu2:2098619 opID=2a84b29f)NFS: 346: Restored connection to the server 192.168.254.3 mount point /otherpool/esxi_backupstore0, mounted as c02083a6-ef60d04d-0000-000000000000 ("backupstore0")&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.212Z cpu2:2098619 opID=2a84b29f)NFS: 221: NFS mount 192.168.254.3:/otherpool/esxi_backupstore0 status: Success&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;seen and tried the suggestions in these&lt;BR /&gt;&lt;A href="https://kb.vmware.com/s/article/1003967?CoveoV2.CoveoLightningApex.getInitializationData=1&amp;amp;r=3&amp;amp;ui-communities-components-aura-components-forceCommunity-seoAssistant.SeoAssistant.getSeoData=1&amp;amp;other.KM_Utility.getArticleDetails=1&amp;amp;other.KM_Utility.getArticleMetadata=2&amp;amp;other.KM_Utility.getUrl=1&amp;amp;other.KM_Utility.getUser=1&amp;amp;other.KM_Utility.getAllTranslatedLanguages=2&amp;amp;ui-comm-runtime-components-aura-components-siteforce-qb.Quarterback.validateRoute=1" title="https://kb.vmware.com/s/article/1003967?CoveoV2.CoveoLightningApex.getInitializationData=1&amp;amp;r=3&amp;amp;ui-communities-components-aura-components-forceCommunity-seoAssistant.SeoAssistant.getSeoData=1&amp;amp;other.KM_Utility.getArticleDetails=1&amp;amp;other.KM_Utility.getArticleMetadata=2&amp;amp;other.KM_Utility.getUrl=1&amp;amp;other.KM_Utility.getUser=1&amp;amp;other.KM_Utility.getAllTranslatedLanguages=2&amp;amp;ui-comm-runtime-components-aura-components-siteforce-qb.Quarterback.validateRoute=1"&gt;VMware Knowledge Base&lt;/A&gt; &lt;SPAN class="uiOutputText slds-align-middle article_title slds-wrap slds-page-header__title" data-aura-class="uiOutputText" data-aura-rendered-by="34:81;a"&gt;Troubleshooting connectivity issues to an NFS datastore on ESX and ESXi hosts (1003967)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/message/2684697"&gt;NFS mount failed: Unable to connect to NFS server.&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/thread/600747"&gt;Strange Issue : NFS datastore can't be mounted only to several ESXi hosts&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/thread/597018"&gt;Unable to add NFS datastore in ESXI 6.5&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Mar 2019 05:34:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/new-esxi-6-7-0-host-will-not-connect-to-the-same-nfs-server-the/m-p/2244310#M218692</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2019-03-07T05:34:16Z</dc:date>
    </item>
    <item>
      <title>Re: Importing VMTools 10.1.0 into vCenter 5.5U3e</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Importing-VMTools-10-1-0-into-vCenter-5-5U3e/m-p/1380546#M18151</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;that kb article is gone.&amp;nbsp; anybody know where it went?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Feb 2019 07:33:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Importing-VMTools-10-1-0-into-vCenter-5-5U3e/m-p/1380546#M18151</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2019-02-25T07:33:48Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere ESXi 6.5 a Autostart order issue</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-ESXi-6-5-a-Autostart-order-issue/m-p/1395340#M133262</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks to both of you for posting your workaround!&amp;nbsp; I was experiencing the same randomness of results, and wondering how to describe the behaviour.&amp;nbsp; This is a freshly-deployed esxi 6.5 server.&amp;nbsp; We migrated VMs from an esxi 6.0 server because of (RAID) hardware issues on the 6.0 server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had attempted to fix this by using the old-style Windows vSphere Client, where we still have the old-style "tiered" startup order&lt;/P&gt;&lt;P&gt;(Configuration -&amp;gt; Virtual Machine Startup/Shutdown -&amp;gt; Properties)&lt;/P&gt;&lt;P&gt;Automatic startup (in priority order)&lt;/P&gt;&lt;P&gt;&amp;nbsp; 1 - dns host&lt;/P&gt;&lt;P&gt;&amp;nbsp; 2 - mail server&lt;/P&gt;&lt;P&gt;&amp;nbsp; 3 - file server&lt;/P&gt;&lt;P&gt;&amp;nbsp; 4 - accounting db server&lt;/P&gt;&lt;P&gt;Any Order (like it says, I guess)&lt;/P&gt;&lt;P&gt;&amp;nbsp; print server&lt;/P&gt;&lt;P&gt;&amp;nbsp; wiki host&lt;/P&gt;&lt;P&gt;Manual Startup&lt;/P&gt;&lt;P&gt;&amp;nbsp; some utility machines&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But upon power up, only four machines started up, in a seemingly random order (all of them in the two "autostart" classes).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, I powered everything down, unregistered all the machines, then registered all of them again (and not in the order that I wanted them to boot).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I then used the web UI to "increase priority" of the machines, and the list built as intuition would expect, contrary to the first go-round. &lt;/P&gt;&lt;P&gt;Next, a reboot of the esxi host (without powering up the VMs), and the machines came up in the desired order&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So in order for the autostart to work as expected, when working with a standalone esxi 6.5 box, it is clearly necessary, after you have each VM working, to unregister each VM, then re-register it.&amp;nbsp; Not sure if that applies to "all machines" or to "each machine".&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Apr 2017 23:21:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-ESXi-6-5-a-Autostart-order-issue/m-p/1395340#M133262</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2017-04-02T23:21:00Z</dc:date>
    </item>
    <item>
      <title>Re: LSI VMware driver: "MN" versus "OP" ???</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/LSI-VMware-driver-quot-MN-quot-versus-quot-OP-quot/m-p/2655492#M255503</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;it is now september 2015&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are faced with MN and NDS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are attempting to install to esxi 6.0.0.whatever&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are guessing that NDS is the v6 version.&amp;nbsp; If it works, we won't be posting. If it fails, we'll let you know the next step&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Sep 2015 22:23:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/LSI-VMware-driver-quot-MN-quot-versus-quot-OP-quot/m-p/2655492#M255503</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2015-09-23T22:23:46Z</dc:date>
    </item>
    <item>
      <title>Re: vmrun getting close to useless with Player</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Player/vmrun-getting-close-to-useless-with-Player/m-p/857030#M9459</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;still the only workaround I could find with player 7.1.2 and vix (VMware-VIX-1.14.2-2780323.x86_64.bundle)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;basically, download the vmware-workstation bundle, install it with your vmware player "pro" key (assuming you have one) and vix will work (after its fashion) with the VMs in player.&amp;nbsp; vmrun reports version 1.14.2 build-2780323 (same as standalone)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vdisk-manager still throws bogus errors with this version &lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;"VixDiskLib: Invalid configuration file parameter. Failed to read configuration files"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sure hope someone at vmware who develops vix / vmplayer wakes up the QA team -- they are obviously missing some test units in their routines&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Sep 2015 01:16:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Player/vmrun-getting-close-to-useless-with-Player/m-p/857030#M9459</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2015-09-14T01:16:51Z</dc:date>
    </item>
    <item>
      <title>Re: Vmrun fails with VMware Player</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Player/Vmrun-fails-with-VMware-Player/m-p/1324891#M16024</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;this did not work for me using vmplayer (paid-for "pro" version) and vix on ubuntu 14.04&lt;/P&gt;&lt;P&gt;The only solution I found was to uninstall both, then download and install the vmware-workstation 11.1.2 bundle, (it accepted the vmware player key, and registered the vm-player portion).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;removed the vmware-worrkstation choices from the menus to prevent the end-user from blundering into trouble.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sure hope someone looks at the testing procedures for vix soon....&amp;nbsp; This has been going on a long time.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Sep 2015 01:00:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Player/Vmrun-fails-with-VMware-Player/m-p/1324891#M16024</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2015-09-14T01:00:58Z</dc:date>
    </item>
    <item>
      <title>Re: safe to ignore vmware-vdiskmanager VixDiskLib: Invalid configuration file parameter</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/safe-to-ignore-vmware-vdiskmanager-VixDiskLib-Invalid/m-p/1295696#M73568</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;issue still arises with vix from vmware workstation pro 11.1.2 running on ubuntu 14.04.x&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;just resized a vmdk on an existing vm&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;vmware-vdiskmanager -x 65GB sysdrive.vmdk -t 0&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&amp;nbsp; Grow: 100% done.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;Disk expansion completed successfully&lt;/SPAN&gt;.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Sep 2015 00:23:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/safe-to-ignore-vmware-vdiskmanager-VixDiskLib-Invalid/m-p/1295696#M73568</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2015-09-14T00:23:34Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual SAN and vSphere Essentials Plus?</title>
      <link>https://communities.vmware.com/t5/vSphere-Storage-Discussions/Virtual-SAN-and-vSphere-Essentials-Plus/m-p/2664170#M23503</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;and it appears VSA was discontinued as of April 1, 2014, anyway&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.vmware.com/products/vsphere-storage-appliance/" title="http://www.vmware.com/products/vsphere-storage-appliance/"&gt;VMware vSphere Storage Appliance (VSA) for Shared Storage | United States&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 27 Jun 2015 03:33:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Storage-Discussions/Virtual-SAN-and-vSphere-Essentials-Plus/m-p/2664170#M23503</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2015-06-27T03:33:53Z</dc:date>
    </item>
    <item>
      <title>Re: Download vmware-vdiskmanager.exe separately? Show version?</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Download-vmware-vdiskmanager-exe-separately-Show-version/m-p/2596731#M155664</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;'cause I keep having to find it again and again&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can now (2015-03-29) get it at:&lt;/P&gt;&lt;P&gt;&lt;A href="https://developercenter.vmware.com/web/sdk/60/vddk" title="https://developercenter.vmware.com/web/sdk/60/vddk"&gt;VDDK for vSphere 6.0 - VMware Developer Center&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://developercenter.vmware.com/web/sdk/60/vddk"&gt;https://developercenter.vmware.com/web/sdk/60/vddk&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;found it by searching for "VDDK Documentation"&lt;/P&gt;&lt;P&gt;or&lt;/P&gt;&lt;P&gt;Virtual Disk Development Kit 6.0 site:vmware.com&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;at duckduckgo.com&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it is in the SDK file download (linux file name: VMware-vix-disklib-6.0.0-2498720.x86_64.tar.gz)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 29 Mar 2015 23:05:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Download-vmware-vdiskmanager-exe-separately-Show-version/m-p/2596731#M155664</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2015-03-29T23:05:45Z</dc:date>
    </item>
    <item>
      <title>Re: player 4.0.1 "switching arrows" missing (vs 3.1.x)</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Player/player-4-0-1-quot-switching-arrows-quot-missing-vs-3-1-x/m-p/2581631#M32553</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;2014-09-11&lt;/P&gt;&lt;P&gt;still broken&lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/message/2425890"&gt;Re: Switch between guest VMs in full screen mode in Vmware Player v5 and v6&lt;/A&gt;&lt;/P&gt;&lt;P&gt;highly unimpressed. &lt;/P&gt;&lt;P&gt;productivity-reducing anti-features are a trademark of the Evil Empire.&amp;nbsp; Looks like VMware has joined them.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Sep 2014 22:24:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Player/player-4-0-1-quot-switching-arrows-quot-missing-vs-3-1-x/m-p/2581631#M32553</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2014-09-11T22:24:00Z</dc:date>
    </item>
    <item>
      <title>Re: Switch between guest VMs in full screen mode in Vmware Player v5 and v6</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Player/Switch-between-guest-VMs-in-full-screen-mode-in-Vmware-Player-v5/m-p/369577#M3469</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;2014-09-11&lt;/P&gt;&lt;P&gt;still does not work (paid version of vmplayer 6.0.2, Xubuntu 14.04)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/message/1887799"&gt;player 4.0.1 "switching arrows" missing (vs 3.1.x)&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Sep 2014 22:00:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Player/Switch-between-guest-VMs-in-full-screen-mode-in-Vmware-Player-v5/m-p/369577#M3469</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2014-09-11T22:00:37Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere 5.5 - I'm I wrong in feeling cheated?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-5-5-I-m-I-wrong-in-feeling-cheated/m-p/982585#M88492</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm with you in the "feeling cheated" category.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That being said, I am in the smallest of small business markets, but the benefits of virtualization have been tremendous for them. The biggest client runs two esxi servers (and numerous desktops). I can only describe my use of esxi as "ghettoVMware" (with apologies to Willam Lam).&amp;nbsp; Nobody in my client base has needed anything more than the free esxi hypervisor, and some ingenuity (like William's) and general sysadmin skills.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My gripe is not about not being able to access the hardware version 10 features, it's how the vm's become unmanageable if they get upgraded.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are no meaningful benefits for my clients to have all those features, so the cost of acquiring them is a complete waste, &lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;except&lt;/STRONG&gt;&lt;/SPAN&gt; that we may end up painted into a corner.&amp;nbsp; We could end up with a system where we can't manage a VM, and we can't license our way out of the problem either, apparently.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I understand all that I've read (which is doubtful), even if we license a vCenter whatever (if that's what we need to get the "vSphere web client"), we won't actually be able to manage the esxi 5.5 host with it -- we'd have to do some downtime/migration/rebuild activity to bring them into the licensed whatever.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is a variant of Hanlon's Razor at play here -- "Never attribute to malice that which is adequately explained by stupidity".&amp;nbsp; At first it just seemed stupid. It's now been more than a year, and a second "point release" of esxi (5.1 -&amp;gt; 5.5) without a change, despite some extensive commentary and requests from the community, so stupidity is losing its explanatory power.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Although, VMware is getting to be more and more like Microsoft/Oracle et al. so, &lt;A href="http://onlinelibrary.wiley.com/doi/10.1111/j.1467-6486.2012.01072.x/abstract"&gt;perhaps it is just stupidity&lt;/A&gt;. PDF available &lt;A href="http://www.europe-solidarity.eu/documents/ES_stupidity.pdf"&gt;here&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In any event, the situation pushes this extensive user of vmware products to look at other, less dangerous tools.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Apr 2014 22:51:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/vSphere-5-5-I-m-I-wrong-in-feeling-cheated/m-p/982585#M88492</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2014-04-16T22:51:23Z</dc:date>
    </item>
    <item>
      <title>vmware workstation 7.1.6 on ubuntu 12.04 - modules won't compile</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/vmware-workstation-7-1-6-on-ubuntu-12-04-modules-won-t-compile/m-p/1774205#M104428</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I upgraded from ubuntu desktop 10.04 (since it's now no longer supported, and there are viable alternatives to unity).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;have tried various patches from &lt;A href="http://weltall.heliohost.org/wordpress/" title="http://weltall.heliohost.org/wordpress/"&gt;http://weltall.heliohost.org/wordpress/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;who seems to be the go-to person for these problems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but I haven't been able to find a set of patches that work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can't use workstation 8 because the hardware is an older 64-bit 3 GHz Pentium D, and I expect that I will find that workstation 8 / player 4 will complain that the bios/CPU lacks some necessary capabilities.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kernel is the stock ubuntu 12.04 desktop (3.2.0-60 SMP amd64, from&amp;nbsp; memory)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the closest I've come is the patch from the above site for workstation 7.1.x with kernel 3.4. The patches apply without error.&amp;nbsp; The process fails on compiling the vmblock module, like this:&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;...&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;Built vmnet module&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;Using 2.6.x kernel build system.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;make: Entering directory `/tmp/vmware-root/modules/vmblock-only'&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;make -C /lib/modules/3.2.0-60-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MODULEBUILDDIR= modules&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;make[1]: Entering directory `/usr/src/linux-headers-3.2.0-60-generic'&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&amp;nbsp; CC [M]&amp;nbsp; /tmp/vmware-root/modules/vmblock-only/linux/block.o&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&amp;nbsp; CC [M]&amp;nbsp; /tmp/vmware-root/modules/vmblock-only/linux/control.o&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&amp;nbsp; CC [M]&amp;nbsp; /tmp/vmware-root/modules/vmblock-only/linux/dbllnklst.o&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&amp;nbsp; CC [M]&amp;nbsp; /tmp/vmware-root/modules/vmblock-only/linux/dentry.o&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&amp;nbsp; CC [M]&amp;nbsp; /tmp/vmware-root/modules/vmblock-only/linux/file.o&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&amp;nbsp; CC [M]&amp;nbsp; /tmp/vmware-root/modules/vmblock-only/linux/filesystem.o&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;/tmp/vmware-root/modules/vmblock-only/linux/filesystem.c: In function ‘FsOpReadSuper’:&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;/tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:534:4: error: implicit declaration of function ‘d_make_root’ [-Werror=implicit-function-declaration]&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;/tmp/vmware-root/modules/vmblock-only/linux/filesystem.c:534:15: warning: assignment makes pointer from integer without a cast [enabled by default]&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;cc1: some warnings being treated as errors&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;make[2]: *** [/tmp/vmware-root/modules/vmblock-only/linux/filesystem.o] Error 1&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;make[1]: *** [_module_/tmp/vmware-root/modules/vmblock-only] Error 2&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-60-generic'&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;make: *** [vmblock.ko] Error 2&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;make: Leaving directory `/tmp/vmware-root/modules/vmblock-only'&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;Unable to install vmblock&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;All done, you can now run VMWare WorkStation.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;except that, of course, Workstation does not run.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm guessing my best option is to install a non-standard (for ubuntu) kernel 3.4 and see what happens.&amp;nbsp; But since this is one machine at a company, I really don't want to do it, if there's a better way.&amp;nbsp; A patch on vmware running on a non-standard kernel is going to come back to bite me at some point, and probably sooner than I want.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks in advance for any help!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 29 Mar 2014 05:06:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/vmware-workstation-7-1-6-on-ubuntu-12-04-modules-won-t-compile/m-p/1774205#M104428</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2014-03-29T05:06:47Z</dc:date>
    </item>
    <item>
      <title>Re: how to get esxi 4.1 license to be accepted on newly-reinstalled host (OEM HP Proliant)</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/how-to-get-esxi-4-1-license-to-be-accepted-on-newly-reinstalled/m-p/2157578#M203464</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;this HP link&lt;/P&gt;&lt;DIV class="paragraphHeader"&gt;&lt;A class="textLink" href="https://h50203.www5.hp.com/wclweb/WCLKMView.aspx?uri=http%3a%2f%2fh20628.www2.hp.com%2fkm-ext%2fcontent-webapp%2fdocument%3fdocId%3demr_na-c01609734%26dtd%3ddefault%26locale%3den%26details%3dno&amp;amp;LinkClass=SAWDOCUMENT&amp;amp;LinkKey=emr_na-c01609734" target="_blank"&gt;HP Integrated VMware &lt;STRONG&gt;ESXi&lt;/STRONG&gt; 4.0 and Updates Getting Started Guide&lt;/A&gt;&lt;SPAN&gt; &lt;IMG src="https://h50203.www5.hp.com/wclweb/App_Themes/HP_Black/Images/pdficon_small.png" /&gt; 190KB&lt;/SPAN&gt;&lt;DIV&gt;...Upgrading to a full &lt;STRONG&gt;license&lt;/STRONG&gt; (on page 7...virtualization software such as &lt;STRONG&gt;ESXi&lt;/STRONG&gt;. Hosts provide processor...solution without the &lt;STRONG&gt;need&lt;/STRONG&gt; for separate external...the correct function &lt;STRONG&gt;key&lt;/STRONG&gt; when prompted to...&lt;/DIV&gt;&lt;DIV class="paragraphHeader"&gt;Last Update: Apr 15, 2010&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class="paragraphHeader"&gt;(a.k.a. &lt;STRONG&gt;&lt;A class="jive-link-external-small" href="http://tinyurl.com/ma9m7kz"&gt;http://tinyurl.com/ma9m7kz&lt;/A&gt;&lt;/STRONG&gt;) is a pdf that leads me to the vmware site, which, when I Log in, shows me my esxi 4.1 license key -- which is not accepted by the "Assign License" process.&lt;/DIV&gt;&lt;DIV class="paragraphHeader"&gt; &lt;/DIV&gt;&lt;DIV class="paragraphHeader"&gt;So in desperation I decided to type it again, after a good night's sleep, and PRESTO, it worked.&lt;/DIV&gt;&lt;DIV class="paragraphHeader"&gt; &lt;/DIV&gt;&lt;DIV class="paragraphHeader"&gt;Which is weird, 'cause yesterday I was cutting and pasting it from the website - and pasting it into notepad first to strip out any stray/unacceptable characters, and had somebody read it back to me.&lt;/DIV&gt;&lt;DIV class="paragraphHeader"&gt; &lt;/DIV&gt;&lt;DIV class="paragraphHeader"&gt;Thanks for the help!&lt;/DIV&gt;&lt;DIV class="paragraphHeader"&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Feb 2014 17:17:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/how-to-get-esxi-4-1-license-to-be-accepted-on-newly-reinstalled/m-p/2157578#M203464</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2014-02-06T17:17:58Z</dc:date>
    </item>
    <item>
      <title>how to get esxi 4.1 license to be accepted on newly-reinstalled host (OEM HP Proliant)</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/how-to-get-esxi-4-1-license-to-be-accepted-on-newly-reinstalled/m-p/2157575#M203461</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have just spent the day recovering from two failed disks in two arrays on one elderly HP proliant ml350 g5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It looks like this was deployed with HP-installed esxi 3.x (based on the HP packaging where the USB key used to be), and later upgraded to 4.1.&amp;nbsp; It's a very small install -- the esxi is running stand-alone.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As part of the process of recovering the arrays I (accidentally) erased the usb stick in the box that hosts the esxi install.&amp;nbsp; So I pulled out the the HP CDs, and instead of the HP-branded esxi 3.x (like on the label of the box), there was a home-burned esxi CD labelled as 4.1 (which matched what was running on the box before the problem arose).&amp;nbsp; So I installed from the CD, got all the VM's running again, ghettoVCB (re-)scheduled via crontab and then went to apply the license.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The branded HP box has a certificate (with barcode) showing I have "permission to use" esxi, but no key.&amp;nbsp; The 4.1 key that I have used elsewhere is not accepted in the "Assign License" dialogue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So - where do I go to fix this?&amp;nbsp; Do I need a key from HP? if so, what do I ask for?&amp;nbsp; My experience of dealing with HP for something like this are less favourable than dealing with the electrical-power monopoly, so any help would be appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Feb 2014 07:32:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/how-to-get-esxi-4-1-license-to-be-accepted-on-newly-reinstalled/m-p/2157575#M203461</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2014-02-06T07:32:11Z</dc:date>
    </item>
  </channel>
</rss>

