- Create a folder that is named "C:\Vmmlogs."
- Open an elevated Windows PowerShell window on the VMM server or host computer, and then run the following commands. (The second command may wrap in your display.)
logman delete VMM
This command deletes any existing definitions of the trace. You can safely ignore any "Data Collector Set was not found" errors that you receive.
logman create trace VMM -v mmddhhmm -o $env:SystemDrive\VMMlogs\VMMLog_$env:computername.ETL -cnf 01:00:00 -p Microsoft-VirtualMachineManager-Debug -nb 10 250 -bs 16 -max 512
- Start the trace by typing the following command in the elevated Windows PowerShell window:
logman start vmm
- Reproduce your issue.
- As soon as you reproduce your issue, stop the trace by typing the following command:
logman stop vmm
Note You can find the ETL file in C:\vmmlogs.
- To convert the trace, type the following command:
Netsh trace convert <filename>
Note In this command, the placeholder <filename> represents the name of the ETL that you found in step 5. The converted trace file will have a name in the format <filename>.txt.
Article ID: 2913445 - Last Review: Mar 17, 2014 - Revision: 1