qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [Spice-devel] Seem thread Competition


From: Alon Levy
Subject: Re: [Qemu-devel] [Spice-devel] Seem thread Competition
Date: Mon, 26 Dec 2011 11:31:50 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

On Mon, Dec 26, 2011 at 02:36:55PM +0800, ZhouPeng wrote:
> On Thu, Dec 22, 2011 at 8:49 PM, ZhouPeng <address@hidden> wrote:
> > On Thu, Dec 22, 2011 at 6:53 PM, Alon Levy <address@hidden> wrote:
> >> On Thu, Dec 22, 2011 at 10:00:18AM +0000, 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 <address@hidden> 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 1CO3233TE828,
> >>> > >> 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 error:
> >>> > >> invalid string in json text.
> >>> > >>           ds": 1323332828, "microseco{"timest35p":39}, 
> >>> > >> "econds":PICE_D
> >>> > >>
> >>> > >> This similar bug seems has been reported by:
> >>> > >> https://bugzilla.redhat.com/show_bug.cgi?id=744105
> >>> > >>
> >>> > >> The patch(http://cgit.freedesktop.org/spice/qemu/commit/?h=spice.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  in spice-core.c again and the patch is in qemu unstable
> >>> > 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. Which
> >>> > > version of spice are you using?
> >>> >
> >>> > spice-server.x86_64  version 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 since
> >>> 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=273917
> >>> (spice-server-0.10.0-1)?
> >>>
> >>
> >> If you find it fixes your problem and doesn't introduce any new ones
> >> please +1 spice-0.10.0-1.fc16 at
> >> https://admin.fedoraproject.org/updates/spice-0.10.0-1.fc16
> Have +1, Thanks.
> >
> > After the steps below, I am sure it is spice-server-0.10.0-1.fc16.x86_64 
> > works.
> > address@hidden pkgconfig]# ldd /usr/bin/qemu-kvm
> >      libspice-server.so.1 => /usr/lib64/libspice-server.so.1
> > (0x00007f5f02799000)
> >
> > address@hidden ~]# rpm --erase spice-server-0.9.1-1.fc16.x86_64 --nodeps
> > address@hidden ~]# rpm --erase spice-server-0.10.0-1.fc16.x86_64 --nodeps
> > address@hidden ~]# ls /usr/lib64/libspice-server* -l
> > lrwxrwxrwx. 1 root root 24 Dec 20 06:43 /usr/lib64/libspice-server.so
> > -> libspice-server.so.1.0.2
> > address@hidden ~]# virsh restore 43.ckp
> > error: Failed to restore domain from 43.ckp
> > error: internal error Child process (LC_ALL=C
> > PATH=/sbin:/usr/sbin:/bin:/usr/bin /usr/bin/qemu-kvm -help) status
> > unexpected: exit status 127
> >  //Note: libspice-server.so.1.0.2 doesn't exists
> >
> > address@hidden ~]# rpm -i spice-server-0.10.0-1.fc16.x86_64.rpm
> > address@hidden ~]# ls /usr/lib64/libspice-server* -l
> > lrwxrwxrwx. 1 root root     24 Dec 20 06:43
> > /usr/lib64/libspice-server.so -> libspice-server.so.1.0.2
> > lrwxrwxrwx  1 root root     24 Dec 22 07:21
> > /usr/lib64/libspice-server.so.1 -> libspice-server.so.1.0.2
> > -rwxr-xr-x  1 root root 983600 Nov 14 08:08 
> > /usr/lib64/libspice-server.so.1.0.2
> > address@hidden ~]# virsh restore 43.ckp
> > Domain restored from 43.ckp
> > ----
> > The software suits related:
> >
> >  spice-server   x86_64   0.10.0-1.fc16    installed
> >  qemu-kvm      x86_64   2:0.15.1-3.fc16  @updates
> >
> > This random bug appears at least 2 time one day before fixing.
> > So in the coming 2 days, if this bug does't appear again, I will
> > assume spice-server-0.10.0-1.fc16.x86_64.rpm fix it :)
> 
> The bug does appear again, So I think

You meant doesn't?

> spice-server-0.10.0-1.fc16.x86_64.rpm can fix.
> 
> The bug appear in my  software before, in steps  below:
> 
> 1) virsh restore vm.ckp vm.xml
> 2) spice client connect
> some time later go step 3)
> 3) virsh dump vm  vm.xml
> 4) virsh save vm vm.ckp
> some time later go step 1) again
> 
> The err always appears in step 3) at random.
> 
> Anyway it is fixed.
> Thanks,
> --
> Zhou Peng



reply via email to

[Prev in Thread] Current Thread [Next in Thread]