![]() ![]() ![]() If you’re using VMware Update Manager the patch will be available through the VMware depot. A reboot would fix it, but that’s a hassle since my firewall/router is virtualized along with my DC (DNS), etc. It was annoying, though, because I could not see my LSI controller status (or any status at all) through the “Hardware Status” tab in vCenter. I didn’t dig too deep into my issue when it’d happen as I only had the host up for about 60 – 65 days on vSphere 6.0 GA. VMware identifies this issue, somewhat vaguely, as involving a memory leak based around CIM providers and Small-Footprint CIM Broker (sfcb) services. I’m not sure what exactly causes it to stop reporting status. My Lenovo TS140 host would stop reporting hardware status after ~20 – 30 days of up-time. It seems as though VMware is considering both of these issues fixed, so that’s good. One of my issues was that I had weirdness setting up NTP during installation and I’ve also had issues with the being able to monitor hardware status from within vCenter Server. I’ve had a couple issues while using vSphere 6. The release notes are available here.Īs you may or may not know, I run vSphere 6.0 in my home lab (on a Lenovo TS140 that has been built up as well as a Dell R710). On 07 July 2015, VMware released their ESXi 6.0.0b patch. Just got back from a nice vacation so I had been away and not doing a whole lot with IT stuff! Hi everyone – thought I’d throw this up here. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |