31–40 of 50 posts
Earlier quoted context omitted.
That vulnerability only applies to HVM guests. No doubt there are other reasons to have rebooted since 2013, but if one of Rackspace's servers only has paravirtualized guests (do they use HVM at all? I don't know), they can get by without patching it.
rackspace most likely uses hvm guests. I think they had freebsd before there was xen pv support
Why do the major Xen providers get advance access to the patches while my machines have to sit vulnerable for over a week?
Why do the major Xen providers get advance access to the patches while my machines have to sit vulnerable for over a week?
Why do the major Xen providers get advance access to the patches while my machines have to sit vulnerable for over a week?
First kernel with certain security guarantees formally proven; now open source. It can be used as a hypervisor which seems like its most obvious first use case. At least until there is enough middle-ware to build full systems directly with it.
Xen's hypervisor would seem to be a great place to implement live patching like KSplice/kGraft/Kpatch does for the Linux kernel. Presumably that stuff still works on KVM host machines with live guests.