That isn't necessary. Suffices to register an hvm ami with the "--sriov simple" switch[1].
Having registered a copy--ami, I needn't change any modules/boot options configuration.
The ixgbevf driver was loaded automatically upon boot of supported instance type (r3) and the network interface was operational out of the box.
Same ami worked without any changes on non-supported instance type (t2) where the vif driver was picked by default.
Cheers,
milan
[1] ec2-register command, Par: To enabled enhanced networking (instance store–backed instances), http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enhanced-networking-linux
2015-03-24 23:21 GMT+01:00 David Gay <dgay@xxxxxxxxxx>:
I'm responsible for Fedimg which uploads our AMIs. Seems to be a reasonable thing to get people's opinions on. Do you *have* to start the instance up then stop it and do all the stuff at [1]? If that has to be done for every HVM upload we provide, that might add some significant time and oddness to the automatic upload process. I don't see a way to just simply toggle a flag at AMI registration time, but then again, I'm not familiar with enhanced networking on AWS.----- Original Message -----
> From: "milanisko k" <vetrisko@xxxxxxxxx>
> To: "Fedora Cloud SIG" <cloud@xxxxxxxxxxxxxxxxxxxxxxx>
> Sent: Friday, March 20, 2015 7:52:21 AM
> Subject: Re: Fedora EC2 Amis: SriovNetSupport
>
> That would be one way.
> However, since it actually is a majority of the instance types[1] that
> support this feature, I'd vote to make it the default.
> That's unless it prevents using/booting the "small" instances of course,
> what AFAIK isn't the case --- I was able to create a snapshot ami from an F21
> instance,
> register it with the sriov flag and boot both a t2 and an r3 instances
> without any issue and confirmed the sriov flag was in effect on the r3
> instance.
> The only limit I know of is the ami has to be HVM[2].
> Moreover, the feature is for free, no extra charges apply so why not to take
> advantage of lower latencies on the instances.
>
> Cheers,
> milan
>
> [1] Enhanced Networking Support, The Instance Types Matrix,
> http://aws.amazon.com/ec2/instance-types/
> [2] Enabling Enhanced Networking on Other Linux Distributions,
> http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html
>
>
>
> 2015-03-19 18:39 GMT+01:00 Garrett Holmstrom < gholms@xxxxxxxxxxxxxxxxx > :
>
>
> On 2015-03-19 9 :11, milanisko k wrote:
>
>
> I'd like to ask about the status/plan of SriovNet support[1] for Fedora
> Amazon images.
> I was able to set this up manually for recent F21 ami ami-5cd9ea41, but
> it is quite an inconvenient experience --- one has to instantiate, stop,
> set attribute value through the CLI tool and start again to enable the
> feature.
> Would it be possible to register future Fedora amis with the enhanced
> networking flag enabled[1]?
> As far as motivation is concerned, please check the blog post[2] for
> some performance evaluation.
>
> Since that only works for some types of instances it wouldn't make sense to
> do that for all images, but registering a separate image (from the same
> bundle/snapshot) with that enabled would be reasonable.
>
> --
> Garrett Holmstrom
> ______________________________ _________________
> cloud mailing list
> cloud@xxxxxxxxxxxxxxxxxxxxxxx
> https://admin.fedoraproject. org/mailman/listinfo/cloud
> Fedora Code of Conduct: http://fedoraproject.org/code- of-conduct
>
>
> _______________________________________________
> cloud mailing list
> cloud@xxxxxxxxxxxxxxxxxxxxxxx
> https://admin.fedoraproject.org/mailman/listinfo/cloud
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>
-- David
[1]: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enhanced-networking-linux under "Enabling Enhanced Networking on Other Linux Distributions"
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
_______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
