Hi
on this v4:
- Add ..contents
- Address all comments
- Create a new Backwards Compatibility section at the end of the file for this.
Please review.
Thanks, Juan.
Continuing on my saga to not have a pointer about how migration
works/should work, this are the doc for the long mails that I had to do last week:
1 - Document how backwards compatibility is supposed to work (that is
what it was on v1 and v2)
2 - Document how to handle features that depend of things outside of qemu
a.k.a. we make this a libvirt/management app problem.
3 - Document how we are supposed to fix backwards compatibility
brokenness.
You can see that I was able to find commits on tree to illustrate 1
and 3. The problem for 2 appeared from a discussion with Avihai about
future vfio devices. Do anyone have a good idea about a commit
already on tree to document it?
Please review.
Later, Juan.
Juan Quintela (4):
migration/doc: Add contents
migration/doc: Add documentation for backwards compatiblity
migration/doc: How to migrate when hosts have different features
migration/doc: We broke backwards compatibility
docs/devel/migration.rst | 520 +++++++++++++++++++++++++++++++++++++++
1 file changed, 520 insertions(+)
--
2.41.0