News for hackers. Stuff that matters.

A comment on Why Xen Wasn't Hit by RETBleed on Intel CPUs. Parent comment

Re:Why Xen Wasn't Hit by RETBleed on Intel CPUs by schainks on Friday August 26, 2022 @02:11PM (#32610854)
The Xen project members list suggests otherwise: https://xenproject.org/about-us/project-members/

Even if it is a custom hypervisor, AWS likely derived it from Xen and sponsors the project to continue doing so.

[ Parent | on HN ]
Re:Why Xen Wasn't Hit by RETBleed on Intel CPUs by paulfurtado on Saturday August 27, 2022 @01:20AM (#32615972)
Since 2017, all new aws instance types have been "nitro", which is based on kvm https://www.brendangregg.com/blog/2017-11-29/aws-ec2-virtual...

AWS does continue to support older instance types, however, but only legacy workloads are using them. They actually now even run the XEN based legacy instance types on nitro. https://perspectives.mvdirona.com/2021/11/xen-on-nitro-aws-n...

[ Parent | on HN ]
Re:Why Xen Wasn't Hit by RETBleed on Intel CPUs by plam503711 on Friday August 26, 2022 @03:12PM (#32611520)
It's not a custom Xen: it's *is* Xen (AFAIK, with possibly their own patch queue for some specific needs on top of it). What's custom is the toolstack around it :)
[ Parent | on HN ]
Re:Why Xen Wasn't Hit by RETBleed on Intel CPUs by schainks on Friday August 26, 2022 @04:56PM (#32612662)
Yeah that's what I thought, but I couldn't find definitive proof besides old posts from the early days.
[ Parent | on HN ]
Re:Why Xen Wasn't Hit by RETBleed on Intel CPUs by Thev00d00 on Friday August 26, 2022 @04:31PM (#32612414)
nitro is KVM based
[ Parent | on HN ]