Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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!).



AWS rebooted PV instances to implement the Vixen shim ( 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.


I had an HVM instance that had forced downtime.


I had 35 HVM instances that didn’t have forced downtime. There are other reasons a machine could need to be brought out of service.


Seconded, I have about 320 HVM instances and have received only a handful of reboot requests.


Any public docs on how you update the kernel without rebooting the guests?



Amazing. I'm jealous (I use Linode).


Thank you!


Live migration of VM’s is a well solved issue.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: