3 ms·
They pause your VM, copy everything about its state over to the new machine, and quickly start the other instance. It's pretty clever. I think there are trick
by pclmulqdq 4y ago
They pause your VM, copy everything about its state over to the new machine, and quickly start the other instance. It's pretty clever. I think there are tricks you can play with machines that have large memory footprints to copy most of it before the pause, and only copy what has changed since then during the pause.
The disks are all on the network, so no need to move anything there.
- prmoustache 4y agoIn reality it sync the memory first to the other host and only pause the vm when the last state sync is small enough to be so quick the pause is barely measurable.
- water-your-self 4y agoIndian jones and the register states
- lbhdc 4y agoWhen its transferring the state to the target, how does it handle memory updates that are happening at that time? Is the programs execution paused at that point?
- outworlder 4y agoNo, they keep track of dirty pages.
- GauntletWizard 4y agoNo, but the memory accesses have hooks that say "This memory was written". Then, program execution is paused, and just the sections of memory that were written are copied again. This has memory performance characteristics - I ran a benchmark of memory read/write speed while this was happening once. It more than halved memory speed for the 30s or so it took from migration started to migration complete. The pause, too, was much longer.
- lbhdc 4y agoAhh I think that was the piece I was missing, thanks! I didn't realize there were hooks for tracking memory changes.