[Devel] [Q] migrating inotify assigned on ploop device
Cyrill Gorcunov
gorcunov at virtuozzo.com
Tue Jan 12 02:13:51 PST 2016
On Tue, Jan 12, 2016 at 01:06:26PM +0300, Igor wrote:
> >>suspend
> >>17b176df-55b6-46c2-9284-67f4475588df : ploop1
> >>
> >>resume
> >>17b176df-55b6-46c2-9284-67f4475588df : ploop2
> >I fear it's not that simple. Look, in CRIU bundle we've a tool named
>
> I do not see any troubles. user provide mapping by ID
> on restore criu have all information ID:OLD-DEVICE:NEW-DEVICE
The main trouble is to invent some longstanding solution instead
of "lets add one more option for this case". Once we start passing
this arguments into criu we will have to save the name mapping somewhere
in images but I think it's not that good.
Also as far as I understand at moment of dump we know only _old-device_
name, we don't know yet which hame appear on restore.
>
> Ok. let me know when your design will be ready.
The idea I've had in mind for migration case
- suspend
- fetch new name for ploop from destination
- recode images with new ploop names
- restore
for suspend/resume it might be
- fetch new ploop name
- recode images
- restore
or something like that.
Cyrill
More information about the Devel
mailing list