Let’s start by adding that missing option. But even though support was added for moving the tools to a Ramdisk, they forgot to add the actual option to the list of advanced settings. The RAM disk workaround should be easy to implement, by setting the host’s Advanced setting “ToolsRamdisk” to 1. Apparently excessive reads to the VMware tools are contributing to the premature boot device failures. The first mitigation is an advanced setting introduced in 7.0u2c that moves the VMware tools to a RAM disk. These changes reduce the IO to the boot device, and hopefully, help them last a bit longer between reinstalls. Next, apply the mitigations from VMware KB article 85685, nonchalantly titled: “Removal of SD card/USB as a standalone boot device option”. 7.0u3 has been taking down entire clusters when a thin provisioned VM is powered on, so I’m waiting for some of that dust to settle. Although 7.0u3 is out, I’m staying on 7.0u2d for the time being. This means a full lab rebuild is inevitable, and I’ll get back to that in a future post, but there are some things we can do in the meantime that may stabilize 7.0 and get a little more life out of those boot devices.įirst, upgrade to 7.0u2c or later. Instead, VMware chose to deprecate support for USB/SD card boot devices with plans to remove it completely in a future release. Like most of the community I was expecting a fix in U3. I had to put the brakes on upgrading past 6.7 after my early host upgrades started burning through boot drives. In my case, all of my lab hosts are affected. If you’ve upgraded to ESXi 7 and you use USB or SD card boot devices, you’ve likely experienced some host failures.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |