Re:AWS vs. GCP reliability is wildly different
by jiggawatts on Wednesday September 21, 2022 @07:32PM
(#32933023)
The clever trick here is that they'll pre-copy most of the memory without bothering to do it consistently, but mark pages that the source had written to as "dirty". The network cutover is stop-the-world, but VMware doesn't copy the dirty pages during the stop. Instead, it simply treats them as "swapped to pagefile", where the pagefile is actually the source machine memory. When computation resumes at the target, the source is used to page memory back in on-demand. This allows very fast cutovers.
Re:AWS vs. GCP reliability is wildly different
by politelemon on Thursday September 22, 2022 @02:05AM
(#32935245)
> VM is stunned for a millisecond
This conjures up hilarious mental imagery, thanks
Re:AWS vs. GCP reliability is wildly different
by kevincox on Thursday September 22, 2022 @10:15AM
(#32939065)
You just bop it on the head, and move it to the new machine quickly. By the time the VM comes to it won't even realize that it is in a new home.
Essential, memory state is copied to the new host, the VM is stunned for a millisecond and the cpu states is copied and resumed on the new host (you may see a dropped ping). All the networking and storage is virtual anyway so that is "moved" (it's not really moved) in the background.