From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:60967) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ReOXe-00064B-J6 for qemu-devel@nongnu.org; Sat, 24 Dec 2011 05:09:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ReOXc-0003uo-NL for qemu-devel@nongnu.org; Sat, 24 Dec 2011 05:09:26 -0500 Received: from mx1.redhat.com ([209.132.183.28]:46547) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ReOXc-0003uV-Gg for qemu-devel@nongnu.org; Sat, 24 Dec 2011 05:09:24 -0500 Date: Sat, 24 Dec 2011 10:09:16 +0000 From: Alon Levy Message-ID: <20111224100916.GB20735@garlic> References: <20111222081952.GD7059@garlic.redhat.com> <20111222100018.GE2802@garlic.tlv.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] Seem thread Competition List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: ZhouPeng Cc: spice-devel@lists.freedesktop.org, qemu-devel@nongnu.org On Thu, Dec 22, 2011 at 07:07:14PM +0800, ZhouPeng wrote: > On Thu, Dec 22, 2011 at 6:00 PM, Alon Levy wrote: > > On Thu, Dec 22, 2011 at 05:42:29PM +0800, ZhouPeng wrote: > >> On Thu, Dec 22, 2011 at 4:42 PM, Alon Levy wrote: > >> > On Thu, Dec 22, 2011 at 10:13:50AM +0800, ZhouPeng wrote: > >> >> Hi, > >> >> > >> >> I meet the err: > >> >> > >> >> # virsh dumpxml 63 > >> >> error: internal error cannot parse json {"timestamp": {"seconds": > >> >> 1323332828, "microseco{"timest35p":39}, "econds":PICE_D 1CO3233TE= 828, > >> >> Dmicrosec "ds"data"52}, : {"ser: "SPrCE_DIS"ONNEC{ED", "port": {"= serve > >> >> ": {6299": "62, "famiamily": "ipv:", "hist": pv4"1 "hos6": > >> >> "182.168.12.231"}, "2lient.: {"p2rt": 3350196, "fa"ily": "}, "cl, > >> >> "ho{sport":t"35020", ": "19y": "i2.4", "168.1.": "19}: lexical er= ror: > >> >> invalid string in json text. > >> >> =A0 =A0 =A0 =A0 =A0 ds": 1323332828, "microseco{"timest35p":39}, = "econds":PICE_D > >> >> > >> >> This similar bug seems has been reported by: > >> >> https://bugzilla.redhat.com/show_bug.cgi?id=3D744105 > >> >> > >> >> The patch(http://cgit.freedesktop.org/spice/qemu/commit/?h=3Dspic= e.v42) > >> >> seems be related with the competition. > >> >> But I searched the upstream qemu, it has not been merged in. > >> >> > >> >> My qemu is qemu-kvm-0.15.1 on 3.1.2-1.fc16.x86_64 > >> >> > >> >> Is there any plan about this bug, it seems be some serious. > >> >> > >> > > >> > The patch Daniel Berrange mentioned wotrked around it in qemu and = is in > >> > qemu 1.0-rc0 and onward, still checking qemu-kvm. There is another= patch > >> > >> Yea, I searched =A0in spice-core.c again and the patch is in qemu un= stable > >> Sorry, I carelessly search by " me " but not " me;" before. > > > > It is in qemu-kvm-1.0 as well. But like you said fedora carries 0.15.= 1 > > that doesn't have it. > > > >> > in spice-0.10 and in 0.8, still need to check if it's in fedora. W= hich > >> > version of spice are you using? > >> > >> spice-server.x86_64 =A0version 0.9.1 > > > > which doesn't have the spice side fix. but 0.10.0 has it, and it is > > closest to 0.9.1. I assume this is from the fedora package as well si= nce > > you mentioned qemu-kvm is from a fedora package? seems the latest is > > indeed 0.9.1-1, can you test > > http://koji.fedoraproject.org/koji/buildinfo?buildID=3D273917 > > (spice-server-0.10.0-1)? > [root@localhost ~]# rpm -i spice-server-0.10.0-1.fc16.x86_64.rpm > file /usr/lib64/libspice-server.so.1.0.2 from install of > spice-server-0.10.0-1.fc16.x86_64 conflicts with file from package > spice-server-0.9.1-1.fc16.x86_64 >=20 > So I force install > rpm -i --force spice-server-0.10.0-1.fc16.x86_64.rpm >=20 > yum list installed: > spice-server.x86_64 0.9.1-1.fc16 @a= naconda-0 > spice-server.x86_64 0.10.0-1.fc16 in= stalled >=20 > 0.9.1-1.fc16 seems not be overrided. >=20 > So first, I am not sure qemu-kvm will use 0.10.0-1.fc16 or 0.9.1-1.fc= 16 >=20 > Second, this is a random bug, I am not sure when it will appear again. Easy to reproduce - do a lot of connect/disconnect of spice clients in succession (that's how I tested). > --=20 > Zhou Peng