Virtual machine could not be started because the requested memory exceeds the available host resources

When a Hyper‑V VM fails to start due to insufficient memory, the VMMS component writes an Event ID 12006 entry to the Microsoft‑Windows‑Hyper‑V‑VMMS‑Admin log.

The exact behavior of the VMMS debug trace buffer after a service restart is not documented, leaving administrators unsure whether verbose trace data survives a restart of the Virtual Machine Management Service.

Does the VMMS service retain its high‑verbosity debug trace entries after a restart? If the trace is cleared, what logging mechanism should be used to capture deployment‑failure details across reboots? Are there any configuration options that control trace persistence?