Comment 11 for bug 1243287

The most recent mailing list discussion about the problem is here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2013-December/219176.html

It does not look likely that there will be a fix soon: it's complicated (and the suggestion to inject a data abort has been rejected), and it only affects broken guest code which has direct access to /dev/mem.

You should get dmidecode and any other similarly broken guest binaries fixed.