> Ok, I'll go through the features and see what kind of state the kernel > programs in there and add them to a VMStateDescription thing. Hohumm, > makes sense to me. It does sometimes happen that there is no state. For example it could be an MSR that we are already getting in and out of KVM. However, it is way more common that you have to add support for reading/writing the MSR in KVM as well, and then teach QEMU's target-i386/kvm.c about it as well. It's hard to say without knowing exactly what the feature is about... Is there an architecture manual out there that documents it? Paolo -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html