Univention Bugzilla – Bug 46705
EC2: Enable ENA and SRIOV
Last modified: 2023-06-19 14:02:52 CEST
Our Linux-4.9 kernel provides both the "ena" and "ixgbevf" kernel modulse, so please mark the next AMI as ENA supported and sriovNet supported. <https://docs.aws.amazon.com/de_de/AWSEC2/latest/UserGuide/enhanced-networking-ena.html> <https://docs.aws.amazon.com/de_de/AWSEC2/latest/UserGuide/sriov-networking.html> Be careful of: ixgbevf 0000:00:03.0 ens3: renamed from eth0
QA: SRIOV works with m4.large: $ readlink /sys/class/net/eth0/device/driver ../../../bus/pci/drivers/ixgbevf Here are two nice blog artivles from Amazon on howto enable ENA: * <https://aws.amazon.com/de/blogs/aws/elastic-network-adapter-high-performance-network-interface-for-amazon-ec2/> * <https://aws.amazon.com/de/blogs/aws/the-floodgates-are-open-increased-network-bandwidth-for-ec2-instances/>
Error message in AWS which raise: Enhanced networking with the Elastic Network Adapter (ENA) is required for the 'm5.large' instance type. Ensure that you are using an AMI that is enabled for ENA. (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParameterCombination; Request ID: eb9cd6eb-8d51-4d21-a1b4-545c401da196)
This issue has been filed against UCS 4.3. UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.
Still TODO - even for UCS-5
You can modify a STOPPED instance: > aws ec2 modify-instance-attribute --instance-id i-$IMAGE --ena-support but (re-)starting it afterward does not seem to be enough. Need to require a new AMI?
generate-appliance now uses `register-image` and enabled ENA. A 1st image was successfully built and tested: Bug #55704 *** This bug has been marked as a duplicate of bug 45426 ***