EFlow VM and your network configuration about iotedge-eflow HOT 5 CLOSED

@hooligan495,

Thank you for posting your findings and the workaround that you found. Please be aware that while this workaround concept is very relevant, after 4/28 we will be publishing an update that will require reinstallation and change the way we manage the lifecycle of our VM. Once this change is deployed, the EFLOW VM will behave similarly to WSL2 and no longer be visible in Hyper-V Manager. We will be able to use command line tools like HCSDiag and HNSDiag to inspect the image. Your scenario is very valid and we will be looking into methods to avoid this situation. You will find information about this update in the release note tags here on Github. In addition, we will provide troubleshooting guidance in the Wiki as soon as possible.

Terry Warwick
Microsoft

from iotedge-eflow.

Thanks Terry!

I figured the new update might eliminating this workaround.

Jay McGaffigan

from iotedge-eflow.

Hi Terry and TEam,
Quick question .. Where will you announce that the update occurred? On the main page to this repo? some other MS portal? Thanks
Jay

from iotedge-eflow.

Hi @hooligan495,

All the documentation of our releases will be posted on our Releases section. Also, we are working on how to indicate users that they are running an older version of EFLOW, probably through WAC.

Thanks

from iotedge-eflow.

Hi @hooligan495,

As part of the EFLOW GA release, we changed the EFLOW VM host naming. The new naming is generated by the Windows host device name + "-EFLOW". You can check the name of the EFLOW VM following these steps:

1. Open an elevated PowerShell session
2. Start an SSH connection to the EFLOW VM using the command Connect-EflowVm
3. Run the command cat /proc/sys/kernel/hostname to check the hostname

from iotedge-eflow.