EFlow deployment error (failed to add device 'Synthetic Ethernet Port') about iotedge-eflow HOT 6 CLOSED

Hi @hututuiandrei,

Thanks for reaching out. Could you please share the VM SKU you are using? Does this VM support nested virtualization?
Also, could you please share the WSSDAgent logs? You can get them from C:\ProgramData\wssdagent.

Thanks,
Francisco

from iotedge-eflow.

Hello @fcabrera23,

VM SKU: Standard_D2ds_v4
Supports nested virtualization
Log file: wssdagent.log

Thank you!

Edit: maybe you meant this "sku": "2019-Datacenter"

from iotedge-eflow.

Hi @hututuiandrei,

Thanks for your response. I see the same issue as you described initially:

ErrorCode[32773] ErrorDescription['AzureVmServer-EFLOW' failed to add device 'Synthetic Ethernet Port'. (Virtual machine ID 3CF18446-754A-4970-80B8-678B33F1B321)] ErrorSummaryDescription [Failed to add device 'Synthetic Ethernet Port'.]

Generally, this error is related to firewalls or policies blocking specific features/ports. A couple of questions

1. Do you have any specific policies limiting server VM usage?
2. Do you have any Antivirus / Antimwlare that could block the VM creation?
3. Can you try adding ports 45000 and 45001 to Windows Defender Firewall and deploying again?

Thanks,
Francisco

from iotedge-eflow.

Hello @fcabrera23,

1. I can confirm that a firewall limits traffic access outside the network for any machine inside it. Is there a list of microsoft services (and respective ports) that we need to allow during the deployment process ?
2. No, the antivirus doesn't seem to be the issue.
3. Windows Defender Firewall is completely turned off on this vm.

from iotedge-eflow.

Hi @hututuiandrei,

Thanks for your information. Please try creating a regular Windows VM using Hyper-V Manager on top of the Azure VM. I'd like to understand if this issue is EFLOW-specific or more related to Hyper-V nested virtualization setup.

Thanks,
Francisco

from iotedge-eflow.

Hi @hututuiandrei,

We saw some issues with D2s and D3s instances with nested virtualization. Please try D4s or D5s; deployment should work.

Thanks,
Francisco

from iotedge-eflow.