2,257
edits
Changes
Jump to navigation
Jump to search
Created page with "{{Release|1.3-rc1|25 Apr 2014}} === New features === * AArch64 * Multiple mount namespaces * FPU state restore control ** Restore old FPU state on newer CPUs ** Ability to ig..."
{{Release|1.3-rc1|25 Apr 2014}}
=== New features ===
* AArch64
* Multiple mount namespaces
* FPU state restore control
** Restore old FPU state on newer CPUs
** Ability to ignore FPU restoration
* Support stopped multi-threaded tasks
* CRIU now can execv() other binary right after restore is complete
* Inode-revese mapping can be enforced to allow live-migration with FS copying
* Gold linker can now be used to compile CRIU
* "Berserker" test to check CRIU scalability
* Punch pages from mem images on restore (optimizes live-migration)
=== Optimizations ===
* Batched deduplication of memory images
* Packed rlimits into core image
* Packed timers into core image
=== Fixes ===
* Bad checks for kcmp() ret codes resulted in errors in file sharing detection
* Multiple mmap-s of same files with different flags blocked the restore
* Integer overflow in huge mapping restore caused restoration failure
* Devpts's newinstance option was lost during dump
* Subsequent dump could try to find old mem dump for newly forked task
* Bad detection of overmounted mountpoints on fsnotify restore
* Page-server could read partial message and failed
* Errors in dumping of two subsequent anon vmas in some cases
* Irmap mis-compared devices for disk FS-s
* TMPFS handles always change during dump/restore
* Pre-dump sometimes hangs on FIFO-s
* Post-restore script fails too late (if does it)
=== New features ===
* AArch64
* Multiple mount namespaces
* FPU state restore control
** Restore old FPU state on newer CPUs
** Ability to ignore FPU restoration
* Support stopped multi-threaded tasks
* CRIU now can execv() other binary right after restore is complete
* Inode-revese mapping can be enforced to allow live-migration with FS copying
* Gold linker can now be used to compile CRIU
* "Berserker" test to check CRIU scalability
* Punch pages from mem images on restore (optimizes live-migration)
=== Optimizations ===
* Batched deduplication of memory images
* Packed rlimits into core image
* Packed timers into core image
=== Fixes ===
* Bad checks for kcmp() ret codes resulted in errors in file sharing detection
* Multiple mmap-s of same files with different flags blocked the restore
* Integer overflow in huge mapping restore caused restoration failure
* Devpts's newinstance option was lost during dump
* Subsequent dump could try to find old mem dump for newly forked task
* Bad detection of overmounted mountpoints on fsnotify restore
* Page-server could read partial message and failed
* Errors in dumping of two subsequent anon vmas in some cases
* Irmap mis-compared devices for disk FS-s
* TMPFS handles always change during dump/restore
* Pre-dump sometimes hangs on FIFO-s
* Post-restore script fails too late (if does it)