On 07/30/2011 01:28 AM, Anthony Liguori wrote:
No, not at all. Just that converting everything to VMState isn't a
prerequisite for building a more robust migration protocol.
The main thing is to priorities the problems we're facing with.
- Live migration protocol:
- VMState conversion is not complete
- Live migration is not flexible enough (even with subsections)
- Simplify destination cmdline for machine creation
- Qdev
- conversion is not complete
- Machine + devices description are complex and have hidden glue
- Qapi
- Needs merging
- QOB
- Only the beginning
So overall there are many parallel projects, probably more than the
above. The RightThink(tm) would be to pick the ones that we can converge
on and not try to handle all in parallel. There are problems we can live
with. Engineering wise it might not be a beauty but they can wait (for
instance dark magic to create the machines). There are some that prevent
adding new features or make the code hard to support w/o them.
Cheers,
Dor
ps: how hard is to finish the vmstate conversion? Can't we just assume
not converted code is not functional and just remove all of it?
Regards,
Anthony Liguori
