On 06/11/2011 12:23 PM, Jan Kiszka wrote:
From: Jan Kiszka<jan.kis...@siemens.com>
These FPU states are properly maintained by KVM but not yet by TCG. So
far we unconditionally set them to 0 in the guest which may cause
state corruptions - not only during migration.
-#define CPU_SAVE_VERSION 12
+#define CPU_SAVE_VERSION 13
Incrementing the version number seems excessive - I can't imagine a
real-life guest will break due to fp pointer corruption
However, I don't think we have a mechanism for optional state. We
discussed this during the 18th VMState Subsection Symposium and IIRC
agreed to re-raise the issue when we encountered it, which appears to be
now.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
