Hello
Just installed a fresh HP DL380 Gen10 with VMware ESXi 6.5 (6.5.0 Update 2 (Build 8294253) from HPE-ESXi-6.5.0-Update2-iso-Gen9plus-650.U2.10.3.0.24 (Hewlett Packard Enterprise)). Installed a Windows Server 2016 Standard virtual machine, but ESXi kills the VM after running for about 5 minutes. After ESXi killed the VM, I can't power it on anymore.
This appears in the event log of the virtual machine:
Issue detected for vm1-server2016 on esxi1 in ha-datacenter: Configuration file has unexpected changes. Virtual machine has been terminated. Unregister and re-register virtual machine if the configuration file is correct.
I have tried unregistering and re-registering but ESXi keeps doing the same...
Thanks,
Any resolution here? I have the same issue on a fresh DL360 Gen10 with 6.5U2.
Sorry, no, I haven't been able to resolve the issue yet.
Try updating to the latest build which is ESXi 6.5 U2b (8935087).
Also have you installed the latest patches for Windows Server 2016 VM?
Rick
Have tried that, also tried ESXi 6.7, same issue. All patches on the Server 2016 VM are installed. It also happens with a CentOS 7 virtual machine.
Is this also happening if you install ESXi by using the VMware ISO and not the HP Custom?
To see if it is perhaps the ISO.
Is that VM part of cluster and HA enabled ?
It is not part of cluster, completely standalone. Fresh install of ESXi and installed a virtual machine. That's it.
can you share VMware.log and vmkernel.log during the time of issue ?
Can you share hostd.log, vmkernel.log and the VM name for which the issue has most recently occurred?
Cheers,
Supreet
The server is being shipped to somewhere else right now, I'll get back to you on that.
This is a known issue with VMware (also affecting Veeam proxy VMs). See the following Veeam KB (KB2443) and VMware KB (KB56453) articles:
KB2443: Veeam Backup & Replication support for VMware vSphere
VMware KB : Configuration file has unexpected changes and during backup proxy virtual machine terminates
As of this post (10/30/18), there is no resolution yet. However, VMware does detail a workaround.
I am having the same problem, but not related to Veeam... I am running VMware ESXi, 6.5.0, 10884925
Did you end up resolving this issue?