From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57887) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bNwg0-0000Gl-RM for qemu-devel@nongnu.org; Fri, 15 Jul 2016 02:32:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bNwfw-0001b1-MG for qemu-devel@nongnu.org; Fri, 15 Jul 2016 02:32:43 -0400 Received: from mx2.suse.de ([195.135.220.15]:49275) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bNwfw-0001aw-FO for qemu-devel@nongnu.org; Fri, 15 Jul 2016 02:32:40 -0400 From: Juergen Gross Message-ID: <57888385.1080403@suse.com> Date: Fri, 15 Jul 2016 08:32:37 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Regression with commit 095497ffc66b7f031 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: xen-devel , "qemu-devel@nongnu.org" , Peter Lieven Cc: Gerd Hoffmann , Paolo Bonzini 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? Juergen