Earlier quoted context omitted.
> How many people want to run an updated kernel without known security vulnerabilities? How many people call that "a custom kernel"? Haven't heard anybody call an upstream distro kernel update a "custom kernel". Is this a typical conversation people have? "Hey Jim, did you update the servers to get the latest OpenSSL security fixes? - Yap, I compiled and installed a custom kernel". Maybe they need to run a better dis…
It's specific to VM images. "Custom" here means "not baked into Xen," since your filesystem is not considered when spawning a domU kernel except in limited circumstances. In the Xen world, your kernel is provided by your hosting provider. You can apt-get all day and nothing will happen. That is what custom means in this context. "Not yours." Read accordingly; you've made the same flawed point at several spots in this…
I thought they used KVM for some reason... But I guess if they use Xen they yeah, they are stuck with whatever kernel they get.