4 ms·
Disclosure: I work for Google Cloud. We were naturally first because we took action internally, but also because we didn't need to reboot guests to ship new ke
by boulos 9y ago
Disclosure: I work for Google Cloud.
We were naturally first because we took action internally, but also because we didn't need to reboot guests to ship new kernels to hosts. We update kernels on our hosts frequently, and so nobody would have particularly noticed that their VMs underwent migrations (we do it all the time!).
- cthalupa 9y agoAWS rebooted PV instances to implement the Vixen shim ( https://lists.xenproject.org/archives/html/xen-devel/2018-01/msg00436.html https://lists.xenproject.org/archives/html/xen-devel/2018-01... ) from my understanding. I do not believe that HVM instances (which would be closer to your KVM infrastructure) needed to be rebooted.
- mr_toad 9y agoI had an HVM instance that had forced downtime.
- soccerdave 9y agoI had 35 HVM instances that didn’t have forced downtime. There are other reasons a machine could need to be brought out of service.
- Torgo 9y agoSeconded, I have about 320 HVM instances and have received only a handful of reboot requests.
- eclipxe 9y agoAny public docs on how you update the kernel without rebooting the guests?
- snuxoll 9y agoLive migration of VM’s is a well solved issue.
- boulos 9y agohttps://cloudplatform.googleblog.com/2015/03/Google-Compute-Engine-uses-Live-Migration-technology-to-service-infrastructure-without-application-downtime.html https://cloudplatform.googleblog.com/2015/03/Google-Compute-... is probably the easiest to follow.
- collinmanderson 9y agoAmazing. I'm jealous (I use Linode).
- eclipxe 9y agoThank you!