Am 15.07.2016 um 08:32 schrieb Juergen Gross:
> Commit 095497ffc66b7f031ff2a17f1e50f5cb105ce588 ("vnc-enc-tight: use
> thread local storage for palette") introduced a regression with Xen:
> Since this commit qemu used as a device model is no longer capable
> to register Xenstore watches (that's the effect visible to a user).
> Reverting this commit makes qemu behave well again. I have no idea
> why that commit would have this effect with Xen, may be some memory
> is clobbered?I personally have no idea, maybe @Paolo has? Maybe the corruption happens somewhere else and is just visible due to this change. Do you see sth when you ran qemu/xen in valgrind? Peter
