[CRIU] [PATCH 0/3] devmap: Introduce ability to map block device when migraring filesystem
Cyrill Gorcunov
gorcunov at openvz.org
Tue Nov 24 02:12:17 PST 2015
It is been found that when we migrating to another machine with
own ploop copy we can't restore inotify objects because the
device ID of ploop has been changed and criu refuses to operate
in such unknown environment.
Thus for migration we need some way to tell CRIU that changed
device IDs are expected. Which is done via --device-map option
(command line or RPC).
Note I've not yet tested this series in real life because I need
to modify p.haul/vzmigrate as well.
Still please take a look, comments are highly appreciated. Maybe
we should extend device-mapping from the beginning to consider
type of devices, major/minor parts or device ranges.
Cyrill Gorcunov (3):
devmap: Introduce --device-map argument
devmap: Add rpc interface
devmap: mountpoint -- Allow to open mountpoint for mapped devices
Documentation/criu.txt | 4 ++++
cr-service.c | 14 ++++++++++++++
crtools.c | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
include/cr_options.h | 2 ++
lib/criu.c | 26 ++++++++++++++++++++++++++
lib/criu.h | 2 ++
mount.c | 18 +++++++++++++++++-
protobuf/rpc.proto | 7 +++++++
8 files changed, 120 insertions(+), 1 deletion(-)
--
2.5.0
More information about the CRIU
mailing list