Line 102: |
Line 102: |
| | | |
| ;--lazy-pages | | ;--lazy-pages |
− | : Restore pages on demand. | + | : Restore pages on demand. In this case dump works "normally", restore skips the memory pages that can be handled on demand and lazy-pages daemon handles the page faults and reads the memory contents from the image files. |
| | | |
| ;--lazy-migrate | | ;--lazy-migrate |
− | : Allows testing of lazy migration when running ns or uns flavor. | + | : Allows testing of post-copy migration when running <code>ns</code> or <code>uns</code> flavor. It cannot run with the host flavor because during post-copy migration the migrated tasks should exist both on the source and the destination. |
| | | |
| ;--remote-lazy-pages | | ;--remote-lazy-pages |
− | : Simulate lazy migration with page server that can send pages. | + | : Simulates post-copy memory migration. Here again, the dump works "normally", but the lazy-pages daemon does not read data from the image files but requests it "over the network" for the page-server. It is the page-server that reads memory pages from the images and simulates what 'dump --lazy-pages' wound have done. |
| | | |
| ;--title | | ;--title |