On Sat, Jan 23, 2016 at 10:57:21PM +0100, Reyk Floeter wrote: > > > On 23.01.2016, at 22:27, Jonathon Sisson <open...@j3z.org> wrote: > > > > On Sat, Jan 23, 2016 at 12:19:29PM +0100, Reyk Floeter wrote: > >> No, you have to *enable* SR-IOV in the image. > >> > >> Machines with the Intel NIC will not show any netfront in the device list > >> via XenStore (just try Ubuntu). > >> > >> Reyk > > > > That's correct, but I think what was being pointed out is that > > an instance with SRIOV enabled cannot have it *disabled* (i.e. > > to switch back to xnf NICs). I was able to get xnf operational > > on a c3.large (enhanced networking-capable) by creating an instance > > with CentOS and swapping the root volume out. Any AMI constructed > > on Amazon Linux or Ubuntu will have enhanced networking enabled > > by default, whereas CentOS doesn't appear to have it enabled (unless > > you manually enable it). > > Ah, OK. > > I recommend to upload new images or to use my public openbsd > images to bootstrap new AMIs. > > The "dd from Linux" trick is just a hack if you don't want to install the > aws and ec2 cli tools - but we have ports now. > > Reyk > Fair enough =)
I wasn't certain if the experimental images were considered ready for testing. I'll switch to using them for any other testing I do. Speaking of testing, is there any particular area non-devs could assist with at this time? Gathering dmesgs for different instance types?
