I have a freshly installed Server 2019 that randomly restarts. The event log shows an uptime event, and the next event, nine seconds later, is a bootup event. There is also a Hyper-V machine running Server 2019 that disappears after these boots. But after rebooting another time, the Hyper-V guest reappears. This is the second time I have encountered this in about a week.
Server 2019 is supported by ESX 6.0.0.
First, make sure you have installed VMware Tools inside the guest OS. Then I would recommend to look at the event logs more closely and try to find a related event. Also, have a look at the events happening at the VM level. So inside ESXi.
I don't understand your remark about the Hyper-V machine. Is that a physical machine? Or virtual? And from where does it disappear? The network?
First, make sure you have installed VMware Tools inside the guest OS. Then I would recommend to look at the event logs more closely and try to find a related event. Also, have a look at the events happening at the VM level. So inside ESXi.
I don't understand your remark about the Hyper-V machine. Is that a physical machine? Or virtual? And from where does it disappear? The network?
Thanks for the response. I had overlooked VMware tools, so it's installed and I have restarted both machines.
The Hyper-V guest is running under the VMware guest. So it's ESXi ---> CCSDC20 (vmware guest) ---> CCSFS20 (hyper-V guest). The Hyper-V guest completely disappears from Hyper-V manager until I reboot. The VHDX does not disappear, but it does not work with a new test Hyper-V guest. After I reboot the VMware guest, everything is back like to was before the crash.
I have experienced four crashes since installing on 12/27/19, a little over a month ago.
On 1/31, I found a bugcheck:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000020, 0x0000000000000002, 0x0000000000000000, 0xfffff8060b04e66e). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 4bef827c-3315-4615-bc7e-bc1595be41c7.
On 1/21, I found a bugcheck:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000010, 0x0000000000000002, 0x0000000000000001, 0xfffff8062381e009). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 1d4564e2-e606-48f4-a34b-c03d0a2e0feb.
On 12/31 at 11:57, I did not find anything suspicious. I have an event from Kernel-Boot, ID: 20 that says the last shutdown success was true. Subsequent entries indicate this boot was manually-selected safe mode.
On 12/31 at 11:55 PM, I did not find anything suspicious. There were some minor time changes, a time zone change, and network controller configuration entries.
In several instances, an event like this one is listed:
The time service is now synchronizing the system time with the time source time.windows.com,0x8 (ntp.m|0x8|0.0.0.0:123->40.119.6.228:123) with reference id 3825628968. Current local stratum number is 4.
There are no suspicious entries on the first two entries in ESXi under Monitor > Events. The logs don't go back far enough to catch the events on 12/31.
I'll continue to monitor this as VMware tools is now installed.
The server hasn't crashed in over a week, but there was a network problem, and restarts were hanging. Then the Hyper-V guest disappeared again. The following article gave me a clue: A virtual disk support provider for the specified file was not found. (0xC03A0014). The virtual disk driver was in fact missing, but it reappeared after another reboot and the Hyper-V guest came right back, again.
Then I found duplicate "VMware VMCI Host Device" entries in device manager. Device Manager seemed to hang uninstalling them, so I had to disable them first. I uninstalled and reinstalled VMware tools to make sure everything was ok, and it did not come back.
