Right now, there is no way savevm versioning can be compatible with upstream QEMU because KVM adds fields to existing savevm structures without incrementing the versions. If you assume that KVM will eventually merge into upstream QEMU, this means that eventually KVM is going to have to break backwards compatibility with itself to resolve this issue in a non-graceful way. So let's do that now instead of doing it later when the situation is only worse. I'm happy to allocate particular version identifiers for KVM to avoid future conflicts. I believe we should try to eliminate the existing differences so that we can converge in the future on a common versioning scheme. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
