On 12/8/13 10:41 AM, Jeff Rizzo wrote:
On 11/18/13 7:22 AM, Jeff Rizzo wrote:On 11/18/13 4:38 AM, FastIce wrote:Hello, we have a similar problem (NetBSD 5.0 VM ). we found out that the problem comes from the libxen. in ../<xen>/tools/libxc/xc_dom0.h<...>/* RETURN VALUE XEN 4.1.2, libxen > 2.9 */ /* return ptr; */ /* RETURN VALUE in 2.9 : */ return (ptr + offset); }If you change ther return value back to ptr+offset all should work fine.In our case it does. I am not sure if this is a xen bug or a feature. Can you test this for your case?Nice work! I won't be able to test this for a couple of days, but it looks very promising. I wonder what the libxen folks have to say about it?+jOk, so it took longer than a couple of days for me to get around to this. :) I have some mixed results to report:The patch fixes my problem when applied to our xentools41-4.1.6.1 package, but it does *not* fix the (same, for me) problem with xentools42-4.2.3.Unfortunately, I'm not that familiar with the Xen libraries - does anyone know of perhaps another place in the code where a similar problem may have been introduced? The patch applied successfully to both versions, but only seemed to fix 4.1. :(+j
Please ignore this; the _real_ problem turned out to be that someone fixed the xentools41 package, but not the xentools42 package, and my patch was not getting applied at all. :-}
+j