Skip to content

Commit 350c4d1

Browse files
committed
Fix broken aka.ms links in EFLOW troubleshoot common errors
1 parent bc0cebb commit 350c4d1

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Troubleshoot Azure IoT Edge for Linux on Windows common issues
33
description: Learn how to resolve common issues encountered when deploying an IoT Edge for Linux on Windows (EFLOW) solution.
44
author: sethmanheim
55
ms.author: sethm
6-
ms.date: 06/03/2025
6+
ms.date: 02/26/2026
77
ms.topic: troubleshooting-general
88
ms.service: azure-iot-edge
99
services: iot-edge
@@ -86,8 +86,8 @@ This section covers common errors when you interact with the EFLOW virtual machi
8686
> | Unexpected return stats from virtual machine | The execution of `Get-EflowVm` PowerShell cmdlet checks the status of the virtual machine. If the communication with the virtual machine fails, or some of the Linux bash commands inside the VM fail, the cmdlet fails. | Check the EFLOW VM connection using `Connect-EflowVm` PowerShell cmdlet and try manually running the VM stats bash commands inside the VM. |
8787
> | TPM provisioning was not enabled! | To get the TPM provisioning information for the TPM, the EFLOW TPM passthrough must be enabled. If TPM passthrough isn't enabled, the cmdlet fails. | Enable TPM passthrough before getting the TPM information. Use the `Set-EflowVmFeature` PowerShell cmdlet to enable the TPM passthrough. For more information about `Set-EflowVmFeature` PowerShell cmdlet, see [PowerShell functions for IoT Edge for Linux on Windows](./reference-iot-edge-for-linux-on-windows-functions.md). |
8888
> | Unknown feature '$feature' is provided. | The *Set-EflowVmFeature* cmdlet supports _DpsTpm_ and _Defender_ as the two features that can be enabled or disabled. | For more information about `Set-EflowVmFeature` PowerShell cmdlet, see [PowerShell functions for IoT Edge for Linux on Windows](./reference-iot-edge-for-linux-on-windows-functions.md). |
89-
> | Unsupported DDA Type: $gpuName | Currently, GPU DDA is only supported for _NVIDIA Tesla T4_ and _NVIDIA A2_. If the user provides another GPU name, the GPU passthrough fails. | Verify all the GPU prerequisites are met. For more information about EFLOW GPU support, check [Azure IoT Edge for Linux on Windows GPU passthrough](https://aka.ms./azeflow-gpu).
90-
> | Invalid GPU configuration requested, <br/> Passthrough enabled but requested gpuCount == $gpuCount <br/> GPU PassthroughType '$gpuPassthroughType' not supported by '$script:WssdProviderVmms' WssdProvider <br/> Requested GPU configuration cannot be supported by Host, <br/> GPU '$gpuName' not available <br/> Requested GPU configuration cannot be supported by Host, <br/> not enough GPUs available - Requested($gpuCount), Available($($selectedGpuDevice.Count)) <br/> Requested GPU configuration cannot be supported by Host, <br/> GPU PassthroughType '$gpuPassthroughType' not supported <br/> Invalid GPU configuration requested, Passthrough disabled but gpuCount > 0" | These errors are generally related to one or more the GPU dependencies not being met. | Make sure all the GPU prerequisites are met. For more information about EFLOW GPU support, check [Azure IoT Edge for Linux on Windows GPU passthrough](https://aka.ms./azeflow-gpu). |
89+
> | Unsupported DDA Type: $gpuName | Currently, GPU DDA is only supported for _NVIDIA Tesla T4_ and _NVIDIA A2_. If the user provides another GPU name, the GPU passthrough fails. | Verify all the GPU prerequisites are met. For more information about EFLOW GPU support, check [Azure IoT Edge for Linux on Windows GPU passthrough](https://aka.ms/azeflow-gpu).
90+
> | Invalid GPU configuration requested, <br/> Passthrough enabled but requested gpuCount == $gpuCount <br/> GPU PassthroughType '$gpuPassthroughType' not supported by '$script:WssdProviderVmms' WssdProvider <br/> Requested GPU configuration cannot be supported by Host, <br/> GPU '$gpuName' not available <br/> Requested GPU configuration cannot be supported by Host, <br/> not enough GPUs available - Requested($gpuCount), Available($($selectedGpuDevice.Count)) <br/> Requested GPU configuration cannot be supported by Host, <br/> GPU PassthroughType '$gpuPassthroughType' not supported <br/> Invalid GPU configuration requested, Passthrough disabled but gpuCount > 0" | These errors are generally related to one or more the GPU dependencies not being met. | Make sure all the GPU prerequisites are met. For more information about EFLOW GPU support, check [Azure IoT Edge for Linux on Windows GPU passthrough](https://aka.ms/azeflow-gpu). |
9191
> | Failed to Connect to EFLOW VM | When attempting to connect to the EFLOW VM using the Connect-EflowVm PowerShell cmdlet, the connection fails with an "authentication handshake failed" error. | The cause is that the WSSDAgent certificate has expired. The WSSDAgent certificate expires one year after a new installation of EFLOW. Please execute updateWssdCert.ps1 to extend the certificate validity period. Note that updating EFLOW does not extend the validity period of the WSSDAgent certificate, check [updateWssdCert.ps1](https://github.com/Azure/iotedge-eflow/blob/main/eflow-util/updateWssdCert.ps1).|
9292
9393
## Networking

0 commit comments

Comments
 (0)