Jens-Uwe Schluessler
2018-Jul-14 11:41 UTC
[CentOS-virt] AWS c5d.9/18xlarge instances not supported
Hi, why are larger AWS instances c5d.9xlarge and c5d.18xlarge (NVMe SSD attached) NOT supported by Centos7 AMI, while smaller instances (e.g. c5d.4xlarge) are supported? Also regular c5.9/18xlarge are supported. Thanks, Jens-Uwe Jens-Uwe Schl??ler -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20180714/d0901e87/attachment.html>
Nico Kadel-Garcia
2018-Jul-14 12:22 UTC
[CentOS-virt] AWS c5d.9/18xlarge instances not supported
On Sat, Jul 14, 2018 at 7:41 AM, Jens-Uwe Schluessler <jens-uwe.schluessler at tu-dresden.de> wrote:> Hi, > > why are larger AWS instances c5d.9xlarge and c5d.18xlarge (NVMe SSD > attached) NOT supported by Centos7 AMI,It wouldn't be the first time. I had problems with the i3 instances when they first came out, and I've been dealing with kernel/hardware incompatibilities with Linux kernels since.... 2000. New hardware, and even new virtualization toolkits that interact with both the supporting hardware and the virtualization layer, can have startling interactions. That's why testing is so critical.> while smaller instances (e.g. c5d.4xlarge) are supported? > > Also regular c5.9/18xlarge are supported.See above. Also, the base CentOS 7 3.10.0 kernel is becoming a bit dated: it's 5 years old now. If you have time: can you set up a smaller instance, do kernel updates on top of a CentOs 7 AMI, and see if *that* AMI is compatible with the new instances? Might make for an interesting test and get you a working AMI.
Jens-Uwe Schluessler
2018-Jul-14 15:33 UTC
[CentOS-virt] AWS c5d.9/18xlarge instances not supported
It seems, c5d.9xlarge and c5d.18xlarge are excluded by intention, already grayed out in AWS instance start console. Other providers (RH) enable them too. Thanks -----Urspr?ngliche Nachricht----- Von: CentOS-virt <centos-virt-bounces at centos.org> Im Auftrag von Nico Kadel-Garcia Gesendet: Samstag, 14. Juli 2018 14:22 An: Discussion about the virtualization on CentOS <centos-virt at centos.org> Betreff: Re: [CentOS-virt] AWS c5d.9/18xlarge instances not supported On Sat, Jul 14, 2018 at 7:41 AM, Jens-Uwe Schluessler <jens-uwe.schluessler at tu-dresden.de> wrote:> Hi, > > why are larger AWS instances c5d.9xlarge and c5d.18xlarge (NVMe SSD > attached) NOT supported by Centos7 AMI,It wouldn't be the first time. I had problems with the i3 instances when they first came out, and I've been dealing with kernel/hardware incompatibilities with Linux kernels since.... 2000. New hardware, and even new virtualization toolkits that interact with both the supporting hardware and the virtualization layer, can have startling interactions. That's why testing is so critical.> while smaller instances (e.g. c5d.4xlarge) are supported? > > Also regular c5.9/18xlarge are supported.See above. Also, the base CentOS 7 3.10.0 kernel is becoming a bit dated: it's 5 years old now. If you have time: can you set up a smaller instance, do kernel updates on top of a CentOs 7 AMI, and see if *that* AMI is compatible with the new instances? Might make for an interesting test and get you a working AMI. _______________________________________________ CentOS-virt mailing list CentOS-virt at centos.org https://lists.centos.org/mailman/listinfo/centos-virt -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 7524 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos-virt/attachments/20180714/5aae7626/attachment-0002.p7s>
Henry Finucane
2018-Jul-14 19:11 UTC
[CentOS-virt] AWS c5d.9/18xlarge instances not supported
On Sat, Jul 14, 2018 at 5:22 AM Nico Kadel-Garcia <nkadel at gmail.com> wrote:> See above. Also, the base CentOS 7 3.10.0 kernel is becoming a bit > dated: it's 5 years old now. If you have time: can you set up a > smaller instance, do kernel updates on top of a CentOs 7 AMI, and see > if *that* AMI is compatible with the new instances? Might make for an > interesting test and get you a working AMI.I did this with CentOS 6 at some point, and it's worth noting that you'll have to build your own AMI from scratch, you can't just update the existing AMI- the base AMI's lack of support "taints" derived ones. I used packer's chroot builder, it was pretty reasonable and you can find examples online to help you get started. -- ----------------------- | Henry Finucane -----------------------