1.1.2110.03111

⚠️ 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.

1.1.2109.0

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.

1.1.2108.0

⚠️ 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.

1.1.2107.0

⚠️ 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.

1.1.2106.1

⚠️ 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.

1.1.2106.0 (Generally Available)

⚠️ 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.

1.0.2.0

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.

1.0.1.0

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.