As far as I can see from the upstream discussion this is indeed a kernel issue. Initially it was intended to be fixed by
Author: Mel Gorman <email address hidden>
xen: properly account for _PAGE_NUMA during xen pte translations
...
Steven Noonan forwarded a users report where they had a problem starting vsftpd on a Xen paravirtualized guest, with this in dmesg: BUG: Bad page map in process vsftpd pte:8000000493b88165 pmd:e9cc01067
...
However the patch got reverted later (which also made it back into 14.04 via stable because it caused regressions on migration. With v3.15-rc2 there was a new change to address this:
commit 29c7787075c92ca8af353acd5301481e6f37082f
Author: Mel Gorman <email address hidden>
mm: use paravirt friendly ops for NUMA hinting ptes
It looks that change (while tagged for stable) has not yet been picked up for 3.13.
As far as I can see from the upstream discussion this is indeed a kernel issue. Initially it was intended to be fixed by
Author: Mel Gorman <email address hidden> 88165 pmd:e9cc01067
xen: properly account for _PAGE_NUMA during xen pte translations
...
Steven Noonan forwarded a users report where they had a problem starting vsftpd on a Xen paravirtualized guest, with this in dmesg: BUG: Bad page map in process vsftpd pte:8000000493b
...
However the patch got reverted later (which also made it back into 14.04 via stable because it caused regressions on migration. With v3.15-rc2 there was a new change to address this:
commit 29c7787075c92ca 8af353acd530148 1e6f37082f
Author: Mel Gorman <email address hidden>
mm: use paravirt friendly ops for NUMA hinting ptes
It looks that change (while tagged for stable) has not yet been picked up for 3.13.