denisglups's Posts

Re: ESXi Reboot Reason

by Contributor in vSphere Hypervisor Discussions
‎10-19-2023 07:02 AM
‎10-19-2023 07:02 AM
Hello redfoxw85, you could have a look into the following log: /var/log/hostd.log and search something like  Hostd: [12:51:54.284 27D13B90 info ‘TaskManager’] Task Created : haTask-ha-host-vim.H... See more...
Hello redfoxw85, you could have a look into the following log: /var/log/hostd.log and search something like  Hostd: [12:51:54.284 27D13B90 info ‘TaskManager’] Task Created : haTask-ha-host-vim.HostSystem.reboot-50 If you find anything in this logs, this will indicate, that it was an deliberate reboot.  What you also could test is to execute this command to check if ESXi is configured to automatically reboot after a Purple Screen of Death (PSOD): esxcfg-advcfg -g /Misc/BlueScreenTimeout If the value listed is anything other than 0, then ESXi automatically reboots after the PSOD. If the output is 0, the system is configured to wait for you to manually restart the host. Maybe this will help you to find the reason for the reboot. BR

Re: vCenter Server Appliance Management NOT accessible

by Contributor in VMware vCenter™ Discussions
‎10-13-2023 07:26 AM
‎10-13-2023 07:26 AM
glad I could help you.  Would appreciate if you could mark the post as accepted solution

Re: vCenter Server Appliance Management NOT accessible

by Contributor in VMware vCenter™ Discussions
‎10-12-2023 11:35 AM
2 Kudos
‎10-12-2023 11:35 AM
2 Kudos
Is the port maybe blocked in your firewall? you could maybe try to telnet it with the port. telnet server-IP port For example: telnet 38.76.11.19 5480

Re: VM vCLS no se enciende

by Contributor in VMware vCenter™ Discussions
‎10-12-2023 06:23 AM
‎10-12-2023 06:23 AM
Did you tried to migrate the vm to hosts with diffrent BIOS? from the error message it seems that the vm is using a cpu functionality which is not supported by teh hosts it is residing. So maybe try ... See more...
Did you tried to migrate the vm to hosts with diffrent BIOS? from the error message it seems that the vm is using a cpu functionality which is not supported by teh hosts it is residing. So maybe try to migrate the vm to a host where a vCLS VM is already running on. BR

Re: VM vCLS doesn't turn on

by Contributor in VMware vCenter™ Discussions
‎10-12-2023 05:42 AM
‎10-12-2023 05:42 AM
I assume you might have some issues with processor or feature supporting 'cpuid.mwait'. If the processor is latest and capable of handling  'cpuid.mwait' then I assume you might have an older BIOS. ... See more...
I assume you might have some issues with processor or feature supporting 'cpuid.mwait'. If the processor is latest and capable of handling  'cpuid.mwait' then I assume you might have an older BIOS. If you migrate to different host and power on, is that working?  are all of your hosts identical in hardware and firware versions?   BR