I am experimenting ESX patch management on an host without an VM on there for learning purposes.
When installing an update which System Impact is set to "No VM Shutdown & No Host Reboot" still shutdown hostd service.
What is the impact of restarting the hostd service? In my experience it does shutdown the VMs.
INFO: No repository URL specified, going with file:/root/updates/ESX-1001726
INFO: Configuring...
INFO: Preparing to install VMware ESX Server ESX-1001726...
INFO: Running yum upgrade...
INFO: | Gathering header information file(s) from server(s)
INFO: | Server: Esxupdate-compatible repository for VMware ESX Server ESX-1001726
INFO: | Finding updated packages
INFO: | Downloading needed headers
INFO: | Finding obsoleted packages
INFO: | Resolving dependencies
INFO: | Dependencies resolved
INFO: | I will do the following:
INFO: | update: shadow-utils 2:4.0.3-29.RHEL3.i386
INFO: | Downloading Packages
INFO: | Getting shadow-utils-4.0.3-29.RHEL3.i386.rpm
INFO: | Running test transaction:
INFO: | Test transaction complete, Success!
INFO: | shadow-utils 100 % done 1/2
INFO: | Completing update for shadow-utils - 2/2
INFO: | Updated: shadow-utils 2:4.0.3-29.RHEL3.i386
INFO: | Transaction(s) Complete
INFO: Shutting down hostd...
INFO: Running esxcfg-boot to regenerate initrds...
INFO: Restarting hostd...
INFO: --- TOTALS: 1 packages installed, 0 pending or failed, 0 removed, 0 excluded ---
INFO: Install succeeded - please come again.
