<div dir="ltr">That isn't necessary. Suffices to register an hvm ami with the "--sriov simple" switch[1].<div><br></div><div>Having registered a copy--ami, I needn't change any modules/boot options configuration.</div><div>The ixgbevf driver was loaded automatically upon boot of supported instance type (r3) and the network interface was operational out of the box.</div><div>Same ami worked without any changes on non-supported instance type (t2) where the vif driver was picked by default.</div><div><br></div><div><br></div><div>Cheers,</div><div>milan</div><div><br></div><div>[1] ec2-register command, Par: To enabled enhanced networking (instance store–backed instances), <a href="http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enhanced-networking-linux">http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enhanced-networking-linux</a><br><div><br></div><div><div class="gmail_extra"><div class="gmail_quote">2015-03-24 23:21 GMT+01:00 David Gay <span dir="ltr"><<a href="mailto:dgay@redhat.com" target="_blank">dgay@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><div class="h5">----- Original Message -----<br>
> From: "milanisko k" <<a href="mailto:vetrisko@gmail.com">vetrisko@gmail.com</a>><br>
> To: "Fedora Cloud SIG" <<a href="mailto:cloud@lists.fedoraproject.org">cloud@lists.fedoraproject.org</a>><br>
> Sent: Friday, March 20, 2015 7:52:21 AM<br>
> Subject: Re: Fedora EC2 Amis: SriovNetSupport<br>
><br>
> That would be one way.<br>
> However, since it actually is a majority of the instance types[1] that<br>
> support this feature, I'd vote to make it the default.<br>
> That's unless it prevents using/booting the "small" instances of course,<br>
> what AFAIK isn't the case --- I was able to create a snapshot ami from an F21<br>
> instance,<br>
> register it with the sriov flag and boot both a t2 and an r3 instances<br>
> without any issue and confirmed the sriov flag was in effect on the r3<br>
> instance.<br>
> The only limit I know of is the ami has to be HVM[2].<br>
> Moreover, the feature is for free, no extra charges apply so why not to take<br>
> advantage of lower latencies on the instances.<br>
><br>
> Cheers,<br>
> milan<br>
><br>
> [1] Enhanced Networking Support, The Instance Types Matrix,<br>
> <a href="http://aws.amazon.com/ec2/instance-types/" target="_blank">http://aws.amazon.com/ec2/instance-types/</a><br>
> [2] Enabling Enhanced Networking on Other Linux Distributions,<br>
> <a href="http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html" target="_blank">http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html</a><br>
><br>
><br>
><br>
> 2015-03-19 18:39 GMT+01:00 Garrett Holmstrom < <a href="mailto:gholms@fedoraproject.org">gholms@fedoraproject.org</a> > :<br>
><br>
><br>
> On <a href="tel:2015-03-19%209" value="+420201503199">2015-03-19 9</a> :11, milanisko k wrote:<br>
><br>
><br>
> I'd like to ask about the status/plan of SriovNet support[1] for Fedora<br>
> Amazon images.<br>
> I was able to set this up manually for recent F21 ami ami-5cd9ea41, but<br>
> it is quite an inconvenient experience --- one has to instantiate, stop,<br>
> set attribute value through the CLI tool and start again to enable the<br>
> feature.<br>
> Would it be possible to register future Fedora amis with the enhanced<br>
> networking flag enabled[1]?<br>
> As far as motivation is concerned, please check the blog post[2] for<br>
> some performance evaluation.<br>
><br>
> Since that only works for some types of instances it wouldn't make sense to<br>
> do that for all images, but registering a separate image (from the same<br>
> bundle/snapshot) with that enabled would be reasonable.<br>
><br>
> --<br>
> Garrett Holmstrom<br>
> ______________________________ _________________<br>
> cloud mailing list<br>
> <a href="mailto:cloud@lists.fedoraproject.org">cloud@lists.fedoraproject.org</a><br>
> <a href="https://admin.fedoraproject" target="_blank">https://admin.fedoraproject</a>. org/mailman/listinfo/cloud<br>
> Fedora Code of Conduct: <a href="http://fedoraproject.org/code-" target="_blank">http://fedoraproject.org/code-</a> of-conduct<br>
><br>
><br>
> _______________________________________________<br>
> cloud mailing list<br>
> <a href="mailto:cloud@lists.fedoraproject.org">cloud@lists.fedoraproject.org</a><br>
> <a href="https://admin.fedoraproject.org/mailman/listinfo/cloud" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/cloud</a><br>
> Fedora Code of Conduct: <a href="http://fedoraproject.org/code-of-conduct" target="_blank">http://fedoraproject.org/code-of-conduct</a><br>
><br>
<br>
</div></div>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.<br>
<br>
-- David<br>
<br>
[1]: <a href="http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enhanced-networking-linux" target="_blank">http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enhanced-networking-linux</a> under "Enabling Enhanced Networking on Other Linux Distributions"<br>
<div class=""><div class="h5">_______________________________________________<br>
cloud mailing list<br>
<a href="mailto:cloud@lists.fedoraproject.org">cloud@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/cloud" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/cloud</a><br>
Fedora Code of Conduct: <a href="http://fedoraproject.org/code-of-conduct" target="_blank">http://fedoraproject.org/code-of-conduct</a><br>
</div></div></blockquote></div><br></div></div></div></div>