Add a wpr log profile for WSL and instructions on how to use it (#6436)

* Add a wpr log profile for WSL and instructions on how to use it

Blue committed Jan 20, 2021 at 19:16 UTC 5c4ea8de2c3e28d32e1c5b24d6536bc3a39aa489
2 files changed +70
CONTRIBUTING.md
+18
@@ -159,3 +159,21 @@ To collect WSL logs follow these steps:
159 - Get a link to your feedback item by clicking on 'Share my Feedback' and post that link to the Github thread so we can easily get to your feedback!
160
161 ![GIF Of networking instructions](img/networkinglog4.gif)
162 +
163 +#### Record WSL logs manually
164 +
165 +If creating a Feedback Hub entry isn't possible, then WSL logs need to be captured manually.
166 +
167 +To do so, first download [wsl.wprp](https://github.com/microsoft/WSL/blob/master/diagnostics/wsl.wprp), then run in an administrative command prompt:
168 +
169 +```
170 +$ wpr -start wsl.wprp -filemode
171 +```
172 +
173 +Once the log collection is started, reproduce the problem, and run:
174 +
175 +```
176 +$ wpr -stop wsl.etl
177 +```
178 +
179 +This will stop the log collection and create a file named `wsl.etl` that will capture diagnostics information.
\ No newline at end of file
diagnostics/wsl.wprp new
+52
@@ -0,0 +1,52 @@
1 +<?xml version="1.0"?>
2 +<WindowsPerformanceRecorder Version="1">
3 + <Profiles>
4 + <EventCollector Id="Collector" Name="Collector">
5 + <BufferSize Value="256"/>
6 + <Buffers Value="1024"/>
7 + </EventCollector>
8 +
9 + <EventProvider Id="lxcore_kernel" Name="0CD1C309-0878-4515-83DB-749843B3F5C9"/>
10 + <EventProvider Id="lxcore_user" Name="D90B9468-67F0-5B3B-42CC-82AC81FFD960"/>
11 + <EventProvider Id="lxcore_service" Name="B99CDB5A-039C-5046-E672-1A0DE0A40211"/>
12 + <EventProvider Id="vm_chipset" Name="de9ba731-7f33-4f44-98c9-6cac856b9f83"/>
13 + <EventProvider Id="vmcompute_dll" Name="AF7FD3A7-B248-460C-A9F5-FEC39EF8468C"/>
14 + <EventProvider Id="vmcompute" Name="17103E3F-3C6E-4677-BB17-3B267EB5BE57"/>
15 + <EventProvider Id="vmmm" Name="6066F867-7CA1-4418-85FD-36E3F9C0600C"/>
16 + <EventProvider Id="vmwp" Name="51DDFA29-D5C8-4803-BE4B-2ECB715570FE"/>
17 + <EventProvider Id="9p" Name="e13c8d52-b153-571f-78c5-1d4098af2a1e"/>
18 + <EventProvider Id="p9rdr" Name="bb1d36f0-e0e0-48cc-9493-fef0e3d0b28c" />
19 + <EventProvider Id="mup" Name="20c46239-d059-4214-a11e-7d6769cbe020" />
20 + <EventProvider Id="rfsmon" Name="51734B23-5B7E-4892-BA8E-45BC110B735C" />
21 + <EventProvider Id="hyperv_storage" Name="c7ad62c6-5c99-5a1b-bbc4-0821ae5b765e" />
22 + <EventProvider Id="hns" Name="0c885e0d-6eb6-476c-a048-2457eed3a5c1" />
23 + <Profile
24 + Id="WSL.Verbose.File"
25 + Name="WSL"
26 + Description="Traces for all WSL components"
27 + LoggingMode="File"
28 + DetailLevel="Verbose"
29 + >
30 + <Collectors>
31 + <EventCollectorId Value="Collector">
32 + <EventProviders>
33 + <EventProviderId Value="lxcore_kernel"/>
34 + <EventProviderId Value="lxcore_user"/>
35 + <EventProviderId Value="lxcore_service"/>
36 + <EventProviderId Value="vm_chipset"/>
37 + <EventProviderId Value="vmcompute_dll"/>
38 + <EventProviderId Value="vmcompute"/>
39 + <EventProviderId Value="vmmm"/>
40 + <EventProviderId Value="vmwp"/>
41 + <EventProviderId Value="9p"/>
42 + <EventProviderId Value="p9rdr"/>
43 + <EventProviderId Value="mup"/>
44 + <EventProviderId Value="rfsmon"/>
45 + <EventProviderId Value="hyperv_storage"/>
46 + <EventProviderId Value="hns"/>
47 + </EventProviders>
48 + </EventCollectorId>
49 + </Collectors>
50 + </Profile>
51 + </Profiles>
52 +</WindowsPerformanceRecorder>
\ No newline at end of file