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

VMware can do it by live migrating the vm, you will incur a short pause though, and the networking is a bit tricky to setup.. This of course doesn't happen during an unexpected downtime, it's a cold boot on another node in that case.


If you migrate a VM to a second hardware server then you have, by definition, a second server.

The question was how you reboot the posited singular hardware server with no downtime to any VMs running on it.


I have never seen this go smoothly on a production server; it's always WAY slower than expected (if you use any significant amount of memory) and something always gets f'd up wrt the network connectivity, broken caches, etc.


if I understand correctly, this is happening (nearly) transparently on GCP all the time. https://cloud.google.com/compute/docs/instances/live-migrati...

It involves copying the whole VM image over, and rewiring the network connections virtually on the fly.

I say (nearly) because it's not 100% transparent, but my understanding is that it works properly the vast majority of time.


Probably true but I'm also pretty sure Google isn't using VMware for live migrations under the good.


And what do you do when you need to restart the actual VM itself? You know, for when you need to patch the kernel and such...




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

Search: