Re: [Xen-devel] Regression with commit 095497ffc66b7f031

Am 15.07.2016 um 12:12 schrieb Paolo Bonzini: > > On 15/07/2016 12:07, Peter Lieven wrote: >> Am 15.07.2016 um 12:02 schrieb Paolo Bonzini: >>> On 15/07/2016 10:47, Juergen Gross wrote: >>>> Nothing scaring and no real difference between working and not working

Re: [Xen-devel] Regression with commit 095497ffc66b7f031

Am 15.07.2016 um 12:02 schrieb Paolo Bonzini: > > On 15/07/2016 10:47, Juergen Gross wrote: >> Nothing scaring and no real difference between working and not working >> variant. >> >> Meanwhile I've been digging a little bit deeper and found the reason: >> libxenstore is setting up a reader thread

Re: [Xen-devel] Regression with commit 095497ffc66b7f031

Am 15.07.2016 um 10:47 schrieb Juergen Gross: > On 15/07/16 09:39, Peter Lieven wrote: >> Am 15.07.2016 um 08:32 schrieb Juergen Gross: >>> Commit 095497ffc66b7f031ff2a17f1e50f5cb105ce588 ("vnc-enc-tight: use >>> thread local storage for palette") introduced

Re: [Xen-devel] Regression with commit 095497ffc66b7f031

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