iotedge-eflow

Release Notes

• Azure IoT Edge 1.1.13
• CBL Mariner May Update 2

Fixed Issues

• No fixed issues

Known Issues

• Issue: Reboot the EFLOW VM from inside VM will stop the VM but won't start again.
• Issue: Reboot after feature update won't start the WSSDAgent.

Download EFLOW 1.1.2205.02062 MSI.

For more information, check AzEFLOW-Update and EFLOW Releases.

Release Notes

• Azure IoT Edge 1.1.13
• CBL Mariner May Update
• NVIDIA A2 GPU support
• Added -customSsh parameter during Deploy-EflowVm for using users own OpenSSH library

Fixed Issues

• Fix issue with Set-EflowVmDnsServers only will take into account the first item of the provided list
• Fix issue with NVIDIA T4 GPU
• Fix issue with DpsTpm provisioning on Server SKUs
• Fix issue 104 - headless provisioning parameter not working as documented
• Fix issue with Set-EflowVmFeature missing configuration

Known Issues

• Issue: Reboot the EFLOW VM from inside VM will stop the VM but won't start again.
• Issue: Reboot after feature update won't start the WSSDAgent.

Download EFLOW 1.1.2204.23052 MSI.

For more information, check AzEFLOW-Update and EFLOW Releases.

Release Notes

• Azure IoT Edge 1.2.9
• CBL Mariner March Update 3
• Add support for PowerShell 7 and PowerShell SDK
• Static MAC address support

Fixed Issues

• Fix issue with Set-EflowVmFeature cmdlet pre requisite verification
• Fix issue 122 - Static IP deployment fails if -ip4PrefixLength is not provided
• Fix issue 127 - Timeout when provisioning with TPM
• Fix issue 134 - Could not initialize DPS provisioning client after reboot of host-OS

Known Issues

• Issue: Reboot the EFLOW VM from inside VM will stop the VM but won't start again.
• Issue: Reboot after feature update won't start the WSSDAgent.

Download EFLOW X64 1.2.9.20042 MSI.
Download EFLOW ARM64 1.2.9.20042 MSI.

For more information, check AzEFLOW-Update and EFLOW Releases.

Release Notes

• Azure IoT Edge 1.1.11
• CBL Mariner March Update 3
• Static MAC address support

Fixed Issues

• Fix issue with Set-EflowVmFeature cmdlet pre requisite verification
• Fix issue 122 - Static IP deployment fails if -ip4PrefixLength is not provided
• Fix issue 127 - Timeout when provisioning with TPM
• Fix issue 134 - Could not initialize DPS provisioning client after reboot of host-OS

Known Issues

• Issue: Reboot the EFLOW VM from inside VM will stop the VM but won't start again.
• Issue: Reboot after feature update won't start the WSSDAgent.

Download EFLOW 1.1.2203.14042 MSI.

For more information, check AzEFLOW-Update and EFLOW Releases.

Release Notes

• Azure IoT Edge 1.2.8
• CBL Mariner Febraury Update
• Add Set-EflowVmDNSServers cmdlet for DNS configurations. For more information, check EFLOW PowerShell functions
• Check correct provisioning when using Provision-EflowVm cmdlet

Fixed Issues

• Fix issue with the query of Defender for IoT status
• Fix issue of high memory usage by WSSDAgent

Known Issues

• Issue: Reboot the EFLOW VM from inside VM will stop the VM but won't start again.
• Issue: Reboot after feature update won't start the WSSDAgent.

Download EFLOW X64 1.2.8.08032 MSI.
Download EFLOW ARM64 1.2.8.08032 MSI.

For more information, check AzEFLOW-Update and EFLOW Releases.

⚠️ Important

We are migrating EFLOW Windows Server deployments from HCS to VMMS technology. Manual migration is needed; for more information, check Server VMMS Manual Migration. All new EFLOW Windows Server deployments will be based on VMMS virtualization technology.

Release Notes

• Azure IoT Edge 1.1.9
• CBL Mariner January Update
• Support for PowerShell 7 and PowerShell SDK
• Add Set-EflowVmDNSServers cmdlet for DNS configurations. For more information, check EFLOW PowerShell functions

Fixed Issues

• Fix issue with Static IP on Server SKUs deployments
• Fix issue with high memory/CPU usage of WSSDAgent

Known Issues

• Issue: Reboot the EFLOW VM from inside VM will stop the VM but won't start again.
• Issue: Reboot after feature update won't start the WSSDAgent.

Download EFLOW 1.1.2202.21022 MSI.

For more information, check AzEFLOW-Update and EFLOW Releases.

⚠️ Important

This is a Public Preview version of Azure IoT Edge for Linux on Windows Continuous Release (EFLOW CR), not intended for production use. A clean installation may be required for production use once the final General Availability (GA) release is available. For more information, check https://aka.ms/AzEFLOW-CR.

Release Notes

• Azure IoT Edge 1.2 (version 1.2.7)
• CBL Mariner January Update
• Microsoft Defender for IoT integration
• PowerShell Module to support installation, configuration, and VM interaction
• Added support for ARM64 devices
• Provisioning (Manual) using connection string and X.509 certificates
• Provisioning (Automatic - DPS) using symmetric keys, X.509 certificates, TPM attestation
• All other features included with EFLOW 1.1LTS
• Updated partition layout, including dedicated log partition.
• New deployment parameters for specifying VM data and log partition sizes – Check new Deploy-Eflow parameters

Resources

• Public Preview Blog
• Documentation

Changes from EFLOW 1.1 LTS

• EFLOW CR version is a non-LTS version, based on IoT Edge 1.2 branch. It contains new features and capabilities that are in the latest stable release. EFLOW 1.1 LTS is the Long-term support (LTS) version based on IoT Edge 1.1 LTS. This version will be stable through the supported lifetime of this version and will not include new features released in later versions. This version will be supported until Dec 2022 to match the IoT Edge 1.1 LTS release lifecycle.
• Integration of Azure IoT Edge 1.2 - For more information, check Azure IoT Edge 1.2.0 release is now generally available.
• Integration of Microsoft Defender for IoT. To enable this feature, check EFLOW PowerShell cmdlets.
  Important: Due to security concerns, once Defender for IoT is enabled in the EFLOW VM, it cannot be disabled.

Known Issues

• Issue: Reboot the EFLOW VM from inside VM will stop the VM but won't start again.
• Issue: Reboot after feature update won't start the WSSDAgent.

Download EFLOW X64 1.2.7.07022 MSI.
Download EFLOW ARM64 1.2.7.07022 MSI.

For more information, check AzEFLOW-Update and EFLOW Releases

⚠️ Important

We are migrating EFLOW Windows Server deployments from HCS to VMMS technology. Manual migration is needed; for more information, check Server VMMS Manual Migration. All new EFLOW Windows Server deployments will be based on VMMS virtualization technology.

Release Notes

• CBL Mariner January update
• Added DNS configuration warning. For more information, check AzEFLOW-DNS
• Enable Developer experience with Visual Studio & EFLOW. For more information, check AzEFLOW-Develop

Fixed Issues

• Fix bug related to Provision-EflowVm status messaging
• Fix bug related to reprovision failure using DPS X509
• Fix bug related to installation failure due to certificate expiration
• Fix bug related to the EFLOW VM not being accessible due to networking issues
• Fix Get-EflowVmEndpoint issue not returning the correct networking information on Server SKUs

Known Issues

• Issue: Reboot the EFLOW VM from inside VM will stop the VM but won't start again.
• Issue: Reboot after feature update won't start the WSSDAgent.

Download EFLOW 1.1.2201.04022 MSI.

For more information, check AzEFLOW-Update and EFLOW Releases.

⚠️ Important

We are migrating EFLOW Windows Server deployments from HCS to VMMS technology. Manual migration is needed; for more information, check Server VMMS Manual Migration. All new EFLOW Windows Server deployments will be based on VMMS virtualization technology.

Release Notes

• Enable read-only physical TPM access from IoT Edge modules - Check our TPM Sample.

Fixed Issues

• Fix bug related to Static IP on Windows Server/Client SKUs
• Fix bug related to custom endpoints for provisioning using DPS

Known Issues

• Issue: Reboot the EFLOW VM from inside VM will stop the VM but won't start again.
• Issue: Reboot after feature update won't start the WSSDAgent.

Download EFLOW 1.1.2112.20121 MSI.

For more information, check AzEFLOW-Update and EFLOW Releases.

⚠️ Important

We are migrating EFLOW Windows Server deployments from HCS to VMMS technology. Manual migration is needed; for more information, check Server VMMS Manual Migration. All new EFLOW Windows Server deployments will be based on VMMS virtualization technology.

Release Notes

• CBL-Mariner October Update
• Azure IoT Edge 1.1.8 Update

Fixed Issues

Known Issues

• Issue: Reboot the EFLOW VM from inside VM will stop the VM but won't start again.
• Issue: Reboot after feature update won't start the WSSDAgent.
• Issue: Failed to deploy EFLOW VM using Static IP.

Download EFLOW 1.1.2111.17111 MSI.

For more information, check AzEFLOW-Update and EFLOW Releases.

⚠️ Important

We are migrating EFLOW Windows Server deployments from HCS to VMMS technology. Manual migration is needed; for more information, check Server VMMS Manual Migration. All new EFLOW Windows Server deployments will be based on VMMS virtualization technology.

Release Notes

• CBL-Mariner September Update
• EFLOW Windows Server virtualization technology migration from HCS to VMMS
• Limited Static IP to Internal/External Switch (Default Switch Static IP not supported)
• Enable Docker logs rotation
• PowerShell cmdlets Get-Help documentation improved

Fixed Issues

• Fix issue 72 related to TPM passthrough after changing EFLOW resources allocation
• Fix an issue that prevented TPM provisioning when using an Internal/External switch
• Fix issue 85 that prevented using custom RegistrationId when provisioning with TPM
• Fix issue 69 related to Get-EflowTpmProvisionInfo to return an PS Object

Known Issues

• Issue: Reboot the EFLOW VM from inside VM will stop the VM but won't start again.
• Issue: Reboot after feature update won't start the WSSDAgent.

Download EFLOW 1.1.2110.03111 MSI.

For more information, check AzEFLOW-Update and EFLOW Releases.

Release Notes

• CBL-Mariner August Update
• Support for multiple networks (NICs) (Beta version). For more information check Wiki - Multiple NICs.
• Disable CBL-Mariner kernel dumps 128MB allocation
• Introduction of Intel iGPU Support (beta drivers)
• Update Nvidia container runtime (1.3.3 ⇢ 1.5.1)

Fixed Issues

• Fix issue 77 that prevented EFLOW update when the installation was in a custom directory.
• Fix issue 72 that caused an error with TPM passthrough after Set-EflowVm command.
• Fix an issue that showed empty EFLOW VM information when being in a stop state.

Known Issues

• Issue: Reboot the EFLOW VM from inside VM will stop the VM but won't start again.
• Issue: Reboot after feature update won't start the WSSDAgent.
• EFLOW virtual machine creation failed when using Windows Server 2022 Public Preview.

Download EFLOW 1.1.2109.0 MSI.

For more information, check AzEFLOW-Update and EFLOW Releases.

⚠️ Important

If you are updating a device from the public preview version of IoT Edge for Linux on Windows to the generally available version, you need to uninstall and reinstall Azure IoT Edge. For more information, check AzEFLOW-Update.

Release Notes

• Update Azure IoT Edge from 1.1.4 to version 1.1.5.
• CBL-Mariner July Update.
• Support for Static IP when using External Switch (Client & Server) and Internal Switch (Server using DHCP).

Fixed Issues

• Fix the issue that prevented users from correctly installing EFLOW when memoryInMB was an odd number.

Known Issues

• Trying to reboot the EFLOW VM from inside VM (sudo reboot / sudo shutdown –r now) will stop the VM but won't start it again. To reboot the VM, use PowerShell commands: Stop-Eflow and Start-Eflow.
• When the host reboots after a feature update, it's possible that the wssdagent service won't start. Therefore, the user needs to manually start the service or reboot the host again to start the wssdagent service.
• Not compatible with NVIDIA GeForce/Quadro GPU driver versions 510.06 and 471.21. For new GeForce/Quadro EFLOW deployments please use driver version 470.76.
• EFLOW virtual machine creation failed when using Windows Server 2022 Public Preview.

⚠️ Important

If you are updating a device from the public preview version of IoT Edge for Linux on Windows to the generally available version, you need to uninstall and reinstall Azure IoT Edge. For more information, check AzEFLOW-Update.

Release Notes

• Update Azure IoT Edge from 1.1.3 to version 1.1.4 - Release 1.1.4 · Azure/iotedge.
• New functionality to provide a virtual switch to the EFLOW VM during deployment. Windows Server customers will have to create the virtual switch prior to EFLOW installation. NOTE: If no virtual switch is provided, EFLOW will attempt the installation using the Default Switch. For more information, check Deply-EflowVm command.
• Support for Static IP when using an ICS Default Switch. NOTE: Internal and External switches still don't support Static IP.
• New PowerShell function to retrieve TPM provisioning information (Get-EflowVmTpmProvisioningInfo).

Fixed Issues

• Fix Issue 33 that prevented users from correctly installing EFLOW unless ExecutionPolicy was set to Unrestricted.
• Fix Issue 49 that resulted in WSSD Agent high CPU usage after EFLOW installation.
• Fix Issue 57 that prevented the installation when Microsoft Update was disabled in the Windows host machine.

Known Issues

• Trying to reboot the EFLOW VM from inside VM (sudo reboot / sudo shutdown –r now) will stop the VM but won't start it again. To reboot the VM, use PowerShell commands: Stop-Eflow and Start-Eflow.
• When the host reboots after a feature update, it's possible that the wssdagent service won't start. Therefore, the user needs to manually start the service or reboot the host again to start the wssdagent service.
• EFLOW virtual machine creation failed when using Windows Server 2022 Public Preview.

⚠️ Important

If you are updating a device from the public preview version of IoT Edge for Linux on Windows to the generally available version, you need to uninstall and reinstall Azure IoT Edge. For more information, check AzEFLOW-Update.

Release Notes

• Fix "Signer is not trusted" bug that prevented users from correctly installing EFLOW.

Known Issues

• Deploy-EflowVm fails to install the EFLOW VM when running on Windows Server SKU's
• Trying to reboot the EFLOW VM from inside VM (sudo reboot / sudo shutdown –r now) will stop the VM but won't start it again. To reboot the VM, use PowerShell commands: Stop-Eflow and Start-Eflow.
• When the host reboots after a feature update, it's possible that the wssdagent service won't start. Therefore, the user needs to manually start the service or reboot the host again to start the wssdagent service.
• GPU-PV nvidia-container-cli: requirement error: unsatisfied condition: cuda>=11.2 - This issue is not specific to EFLOW. A workaround can be found on Step 11 of the guide: Run a GPU module on Microsoft Azure Stack Edge Pro GPU device
• EFLOW virtual machine creation failed when using Windows Server 2022 Public Preview.

⚠️ Important

If you are updating a device from the public preview version of IoT Edge for Linux on Windows to the generally available version, you need to uninstall and reinstall Azure IoT Edge. For more information, check AzEFLOW-Update.

Release Notes

• Azure IoT Edge 1.1 LTS (version 1.1.3)
• CBL Mariner (Linux Kernel version 5.10.37.1)
• PowerShell Module to support installation and configuration
• Provisioning (Manual) using connection string and X.509 certificates
• Provisioning (Automatic - DPS) using symmetric keys, X.509 certificates, TPM attestation
• GPU passthrough for Linux workloads (See: AzEFLOW-GPU for more information)

Resources

• GA Blog
• GA IoT Show
• Documentation

Changes from Public Preview

• Azure EFLOW VM lifecycle management has changed and, as a result, is no longer available through Hyper-V Manager. Instead, please see PowerShell commands for managing the virtual machine.
• Azure EFLOW Linux image no longer includes a package manager. The Linux environment is kept up to date using Windows Update. Please see AzEFLOW-Update for more information on updates.
• Azure EFLOW Linux image migrated to a read-only root-fs and does not support adding custom packages to the Linux runtime.
• Windows Admin Center (WAC) Azure IoT Edge extension updated to 1.61.0 to support new EFLOW GA functionalities – WAC IoT Edge extension remains in preview.
• Remove EFLOW VM hostname final GUID and changed naming scheme to Windows host device name + "-EFLOW"

Known Issues

• Trying to reboot the EFLOW VM from inside VM (sudo reboot / sudo shutdown –r now) will stop the VM but won't start it again. To reboot the VM, use PowerShell commands: Stop-Eflow and Start-Eflow.
• When the host reboots after a feature update, it's possible that the wssdagent service won't start. Therefore, the user needs to manually start the service or reboot the host again to start the wssdagent service.
• GPU-PV nvidia-container-cli: requirement error: unsatisfied condition: cuda>=11.2 - This issue is not specific to EFLOW. A workaround can be found on Step 11 of the guide: Run a GPU module on Microsoft Azure Stack Edge Pro GPU device/
• EFLOW virtual machine creation failed when using Windows Server 2022 Public Preview.

Release Notes

• Additional event logs for updates, deployments, and provisioning
• Update minimum requirements: Free memory from 2GB to 1GB

Known Issues

• WAC extension and Get-EflowVMEdgeInformation command will return the wrong EFLOW version. To check the IoT Edge version use sudo iotedge -V command inside the EFLOW VM.

Release Notes

• Fix issue with Provision-EflowVM tool for DPS using x509 certificate which was incorrectly requiring "-registrationId" flag even though it was not used for the provisioning process
• Fix issue with Get-EflowVmSytemInformation tool, which was showing free storage of the rootfsA partition instead of the total storage on the data partition
• Fix bug which created a malformed variable in the Window's System's PATH variable
• Update iotedge from 1.0.10.4 to version 1.1.0 Release 1.1.0 · Azure/iotedge
• Addition of runtime package to support serial passthrough. For more information, visit EFLOW - Samples

Known Issues

• WAC extension and Get-EflowVMEdgeInformation command will return the wrong EFLOW version. To check the IoT Edge version use sudo iotedge -V command inside the EFLOW VM.