qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: ZhouPeng <zpengxen@gmail.com>
To: qemu-devel@nongnu.org, spice-devel@lists.freedesktop.org,
	alevy@redhat.com
Subject: Re: [Qemu-devel] Seem thread Competition
Date: Thu, 22 Dec 2011 19:07:14 +0800	[thread overview]
Message-ID: <CAAh7U5O696yFvQSgmsCROY8LhmDzZxe-sk9aah5Q2rr+hasVeQ@mail.gmail.com> (raw)
In-Reply-To: <20111222100018.GE2802@garlic.tlv.redhat.com>

On Thu, Dec 22, 2011 at 6:00 PM, Alon Levy <alevy@redhat.com> wrote:
> On Thu, Dec 22, 2011 at 05:42:29PM +0800, ZhouPeng wrote:
>> On Thu, Dec 22, 2011 at 4:42 PM, Alon Levy <alevy@redhat.com> 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)?
[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

So I force install
rpm -i --force spice-server-0.10.0-1.fc16.x86_64.rpm

yum list installed:
spice-server.x86_64                     0.9.1-1.fc16                 @anaconda-0
spice-server.x86_64                     0.10.0-1.fc16                installed

0.9.1-1.fc16 seems not be overrided.

So  first, I am not sure qemu-kvm will use 0.10.0-1.fc16  or 0.9.1-1.fc16

Second, this is a random bug, I am not sure when it will  appear again.
-- 
Zhou Peng

  parent reply	other threads:[~2011-12-22 11:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-22  2:13 [Qemu-devel] Seem thread Competition ZhouPeng
2011-12-22  8:42 ` Alon Levy
2011-12-22  9:42   ` ZhouPeng
2011-12-22 10:00     ` Alon Levy
2011-12-22 10:53       ` [Qemu-devel] [Spice-devel] " Alon Levy
2011-12-22 12:49         ` ZhouPeng
2011-12-26  6:36           ` ZhouPeng
2011-12-26  9:31             ` Alon Levy
2011-12-26  9:47               ` ZhouPeng
2011-12-22 11:07       ` ZhouPeng [this message]
2011-12-23 18:03         ` Ademar de Souza Reis Jr.
2011-12-24 10:09         ` [Qemu-devel] " Alon Levy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAh7U5O696yFvQSgmsCROY8LhmDzZxe-sk9aah5Q2rr+hasVeQ@mail.gmail.com \
    --to=zpengxen@gmail.com \
    --cc=alevy@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=spice-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).