Skip to content

Commit b1abdfb

Browse files
Merge pull request #311833 from jlian/fix/eflow-troubleshoot-corrupted
Fix corrupted markdown and wrong link in EFLOW troubleshoot guide
2 parents ecb3f56 + 143e443 commit b1abdfb

1 file changed

Lines changed: 1 addition & 4 deletions

File tree

articles/iot-edge/troubleshoot-iot-edge-for-linux-on-windows.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -84,14 +84,11 @@ Second, the issue could be related to lack of resources. You can set the *EflowV
8484
Get-CIMInstance Win32_OperatingSystem | Select FreePhysicalMemory
8585
```
8686
1. Check the available CPU cores. Make sure that *NumberOfLogicalProcessors* is greater than *EflowVmAssignedCPUcores*.
87-
```powershell
88-
wmic cpu get NumberOfLogicalProcessors
89-
```ssignedCPUcores*.
9087
```powershell
9188
wmic cpu get NumberOfLogicalProcessors
9289
```
9390
94-
Finally, the issue might be related to networking. For more information about EFLOW VM networking issues, see [How to troubleshoot Azure IoT Edge for Linux on Windows networking](./troubleshoot-common-errors.md).
91+
Finally, the issue might be related to networking. For more information about EFLOW VM networking issues, see [How to troubleshoot Azure IoT Edge for Linux on Windows networking](./troubleshoot-iot-edge-for-linux-on-windows-networking.md).
9592
9693
## Check the status of the IoT Edge runtime
9794

0 commit comments

Comments
 (0)