On Sun, Oct 21, 2012 at 1:29 PM, Manuel Bouyer <bouyer%antioche.eu.org@localhost> wrote: > OK, here's another patch, which also checks that the mapping doesn't > change. But I wonder is the corruption occurs on the NetBSD side. > Could you also add some debugging code on the other side ? Still no luck with the new patch, I've been looking at the Linux code, and the attached patch (taken the idea from Linux) mitigates the problem, but we still have it. I've also added the trace and verbose options to xenstored running in the Dom0, and there's no sign that anyone is writing to xenstore when the crash happens. Is it possible that someone writes to the machine address xen_start_info.store_mfn and is there anyway to check that nobody is mapping this ma to another va?
Description: Binary data