...or sometimes bothsometimes both!
ESXi 5.1 crashingESXi 5.1 crashing (bug fixed by updates)
Installing XenServer 6.2 on Proliant DL160G6 freezes during "Installing from base pack"Installing XenServer 6.2 on Proliant DL160G6 freezes during "Installing from base pack" (firmware)
Disconnected Network Adapter on VMware - only power cycle solve thisDisconnected Network Adapter on VMware - only power cycle solve this (firmware)
Unable to view sensor data in ESXi 5.x on DL380 G7Unable to view sensor data in ESXi 5.x on DL380 G7 (bug fixed by updates)
Why is VMware ESXi 5.5 crashing?Why is VMware ESXi 5.5 crashing? (bug fixed by updates)
ESXi host losing connection to vCenterESXi host losing connection to vCenter (bug fixed by updates)
HP ProLiant with SATA/SAS DrivesHP ProLiant with SATA/SAS Drives (firmware)
Is this a basic troubleshooting step that people are missing? Maybe it's that VMware and HP solutions require more massaging and care than others, but my impression is that people simple aren't making the effort to keep their environments updated and run into bugs as a result.
In a time where software updates are mandatory for general purpose operating systems, our phones, televisions, bathroom scales and even my bicycle, why is it missed so often in the server hardware and virtualization space?
Is there a cleaner way to answer these questions or suggest, "are you on a recent revision of software|firmware|BIOS?" at the time of posting?
