Please refer to for system requirementsĭuring EFLOW deployment, the Deploy-EFlow PowerShell cmdlet checks that all the prerequisites are met.
#UNIX ERROR SEAIQ WINDOWS#
This Windows device does not meet the minimum requirements for Azure EFLOW. Installer will try removing the VM and mark the installation as failed. If you want to remove the Azure IoT Edge for Linux on Windows installation from your device, use the following commands.Ĭreating storage vhd (file: $($config)) failedĮrror when creating or resizing the EFLOW virtual machine VHDX.Ĭheck EFLOW installation logs C:\Program Files\Azure IoT Edge and WSSDAgent logs C:\ProgramData\wssdagent for more information.Įrror related to virtual machine creation by WSSDAgent. Make sure to completely uninstall EFLOW before starting a new installation. In some cases, if the installation fails in its final steps, the VM was created and it's still running in the Windows host OS. You much remove '$name' virtual machine first.ĭuring EFLOW deployment, the installer checks if there's an EFLOW VM created from previous installations. To redeploy the virtual machine, please uninstall and re-install $eflowProductName. EFLOW reinstallation is needed.Īn existing virtual machine was detected. If the directory isn't available, the VM can't be created. For example, if the default installation directory was used, the configuration files should be in the C:\Program Files\Azure IoT Edge\yaml directory.Ĭheck if the directory was deleted or moved. Virtual machine configuration could not be retrieved from wssdagentįind the EFLOW configuration yaml files under the EFLOW root installation folder. WSSDAgent runs a service on the Windows host OS. The WSSDAgent is the EFLOW component that creates and manages the lifecycle of the VM. If one of these services isn't available, the installation fails.įor more information EFLOW Hyper-V support, see Azure IoT Edge for Linux on Windows Nested Virtualization. The EFLOW virtual machine requires several Hyper-V services in order to create and run the virtual machine. These errors are related to Hyper-V virtualization technology stack and services. Ensure Hyper-V is configured properly and capable of starting virtual machines.
Hyper-V core services not running (vmms, vmcompute, hvhost). Hyper-V properties indicate the Hyper-V component is not functional (property HyperVisorPresent is false). Hyper-V properties indicate the Hyper-V component is not functional (property HyperVRequirementVirtualizationFirmwareEnabled is false) If this feature isn't available or the feature installation fails, the EFLOW deployment fails.
#UNIX ERROR SEAIQ INSTALL#
When deploying EFLOW, if one of the prerequisites it's not met, the installer tries to install it. Please add '$featureversion' optional feature in settings and restart the deployment. $feature isn't available in this Windows edition. OpenSSH: If you're using your own custom installation, check customSsh parameter during deployment. Hyper-V: For more information EFLOW Hyper-V support, see Azure IoT Edge for Linux on Windows Nested Virtualization. If you have multiple installations, make sure to have the correct module imported. PowerShell: Close PowerShell session and open a new one. If one the prerequisites aren't met, the Deploy-Eflow cmdlet fails.Įnsure that all required prerequisites are met.
Aborting.ĮFLOW installation has required prerequisites to deploy the virtual machine. Please install manually and restart deployment. Installation of Hyper-V, Hyper-V Management PowerShell or OpenSSH failed. Verify the VHDX file wasn't deleted or moved from the original location. The error occurs if the VHDX file isn't found during resizing. When installing EFLOW current release (CR), the user can provide the data partition size using the vmDataSize.
If it doesn't start, share the content under C:\ProgramData\wssdagent.Įxpected image '$vhdPathBackup' is missing If WSSDAgent isn't running, try starting the service manually using the cmdlet: Start-Service -name WSSDAgent.
Verify the WSSDAgent service is running on the Windows host OS by opening an elevated PowerShell session and running the command Get-Service -Name wssdagent. If the service isn't running, the VM communication and lifecycle fails.
#UNIX ERROR SEAIQ UPDATE#
WssdAgent is unreachable, update has failed. If you're using Windows Client RS5 (17763), verify you have the latest Windows update. If you're using a Windows version 20H1 or later, the HCS/HNS API should meet the requirement. HNS API version X doesn't meet minimum versionĮFLOW uses HCS/HNS to create the virtual machine on client SKUs.
0 kommentar(er)
