(sorry for crappy link, can't figure out how to link directly to the appropriate question. Search for "What is the underlying hypervisor on C5 instances" question).
Maybe find a new regression
Should we try it on a db shard?
Or exercise some discretion...
instance sizes aren’t powers of two
The discount's just 15 percent
We can hand wave that away
It shouldn’t cause a downtime event
Let’s be adults here I say...
Everything xen, everything xen
I don't think so
Everything xen, everything xen
I don't think so
— Bush, Everything Xen
" Q. What is the underlying hypervisor on C5 instances?
C5 instances use a new EC2 hypervisor that is based on core KVM technology. "
If they are announcing things like a brand new hypervisor ahead of re:Invent one wonders what they are saving for the main event...is it too much to hope for managed Kubernetes?
I did notice that it took a while for the status check to go green though. There was a warning message saying that it couldn't connect to the instance. I was able to SSH just fine though.
Since both hypervisors have very good support for hardware virtualization technology, it becomes more of an architecture decision. Practically speaking, it is a little bit easier to build a very small footprint hypervisor with the core KVM code than Xen.
[1] https://github.com/torvalds/linux/blob/master/arch/x86/xen/
Has anyone booted one yet? Is it KVM or something from scratch that AWS wrote?