Re: [Spice-devel] improving spice-html5 performance

2013-02-21 Thread Attila Sukosd
I would also be interested in helping out improving it possibly :) Attila On Wed, Feb 20, 2013 at 10:14 AM, Erfane Arwani erfane.arw...@apwise.comwrote: Hello Jeremy, We'd like to know more about your code. +Have you generated the javascript? Automatically? In the Wiki you talk about C

Re: [Spice-devel] spice crashes

2013-02-21 Thread Trebor Forban
2013/2/20 Alon Levy al...@redhat.com: I haven't recompiled with debugging for the stack trace yet; is it still necessary, or does the information above suffice? Sorry for dropping the ball on this. I'm afraid it's hard to debug even with this information. If you could run the vm under

Re: [Spice-devel] spice crashes

2013-02-21 Thread Alon Levy
- Original Message - 2013/2/20 Alon Levy al...@redhat.com: I haven't recompiled with debugging for the stack trace yet; is it still necessary, or does the information above suffice? Sorry for dropping the ball on this. I'm afraid it's hard to debug even with this

Re: [Spice-devel] [PATCH spice-gtk] channel: swap tls status during seamless migration

2013-02-21 Thread Marc-André Lureau
- Mensaje original - On Wed, Feb 20, 2013 at 05:34:07PM +0100, Marc-André Lureau wrote: In some cases, source and destinations may have different channel encryption. We need to swap tls state too during seamless migration. Are we fine with going from encrypted to non-encrypted

Re: [Spice-devel] [PATCH spice-gtk] channel: swap tls status during seamless migration

2013-02-21 Thread Christophe Fergeau
On Thu, Feb 21, 2013 at 05:20:06AM -0500, Marc-André Lureau wrote: - Mensaje original - On Wed, Feb 20, 2013 at 05:34:07PM +0100, Marc-André Lureau wrote: In some cases, source and destinations may have different channel encryption. We need to swap tls state too during

Re: [Spice-devel] spice crashes

2013-02-21 Thread Trebor Forban
Hello Alon, ok, after compiling libssl-dev with -DPURIFY qemu fails to start under valgrind: root@thfs1:~# less qemu-1.4.0-system-x86_64_valgrind-2013-02-21-11-12.log ==5726== Memcheck, a memory error detector ==5726== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. ==5726==

Re: [Spice-devel] spice crashes

2013-02-21 Thread Trebor Forban
Hello Alon, forget my last mail, it was just noise. I had an error in my conf. Best regards, TF 2013/2/21 Trebor Forban trebor.for...@gmail.com: Hello Alon, ok, after compiling libssl-dev with -DPURIFY qemu fails to start under valgrind: root@thfs1:~# less

Re: [Spice-devel] Higher (quadratical) resolution

2013-02-21 Thread David Jaša
Hi, Mike píše v St 20. 02. 2013 v 09:13 -0800: Hi Dennis, Wow, great help Dennis, you just solved my problem I've been struggling with for the last week and as expected it was something silly. I had upgraded from QEMU 1.0 to 1.2 but all my libvirt domains were still specifying

Re: [Spice-devel] spice crashes

2013-02-21 Thread Alon Levy
What is the qemu command line? Are you running with kvm or with tcg? - Original Message - Hello Alon, ok, I've got the VM running under valgrind now, but valgrind quits logging due to excessive errors. The log is attached. Best regards, TF 2013/2/21 Trebor Forban

Re: [Spice-devel] spice crashes

2013-02-21 Thread Alon Levy
Can you run qemu built with debugging symbols? same goes for spice-server. - Original Message - Hello Alon, ok, I've got the VM running under valgrind now, but valgrind quits logging due to excessive errors. The log is attached. Best regards, TF 2013/2/21 Trebor Forban

[Spice-devel] Windows Guest Tools 0.52

2013-02-21 Thread Christophe Fergeau
Hi, I've put a new release of the SPICE Guest Tools for Windows at http://spice-space.org/download/windows/spice-guest-tools/spice-guest-tools-0.52.exe I've changed the versioning for this release to base the version number off the virtio-win ISO it's based on [1]. The SPICE agent is

[Spice-devel] Windows SPICE vdagent 0.7.0 release

2013-02-21 Thread Christophe Fergeau
Hi, I've tagged a 0.7.0 release of the SPICE agent for Windows, source and binaries can be found at http://spice-space.org/download/windows/vdagent/vdagent-win-0.7.0/ The 32 and 64 bit binaries were built on Fedora's koji using mingw. Christophe pgpr_QPxkqtMl.pgp Description: PGP signature

Re: [Spice-devel] spice crashes

2013-02-21 Thread Trebor Forban
Hi Alon, 2013/2/21 Alon Levy al...@redhat.com: What is the qemu command line? Are you running with kvm or with tcg? + export SDL_VIDEO_X11_DGAMOUSE=0 + SDL_VIDEO_X11_DGAMOUSE=0 + /usr/bin/qemu-system-x86_64 -name master99,process=master99 -cpu qemu64 -rtc base=localtime -enable-kvm -runas

Re: [Spice-devel] spice crashes

2013-02-21 Thread Trebor Forban
Not meaning to rub anyone the wrong way, I would still like to note a few unqualified observations: I suspect the problems may be within the spice-guest-tools. With an older version of the spice-guest-tools (I believe spice-guest-tools-0.1.exe) there was a bug/race which frequently caused guest

[Spice-devel] Usbredirection problem with digital signature pendrive

2013-02-21 Thread Fabio Fantoni
I have a problem with usb digital signature device with usbredirection. I have enabled on spicy Options-Auto redirect newly plugged in USB devices. The devices that I'm trying to redirect contains 2 components: Bus 002 Device 014: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB Flash

Re: [Spice-devel] spice crashes

2013-02-21 Thread Christophe Fergeau
On Thu, Feb 21, 2013 at 03:05:57PM +0100, Trebor Forban wrote: With spice-guest-tools-0.3.exe and spice-guest-tools-0.52.exe the vdagent starts reliably, but the hang at boot is back, at least with smp=1 and NIC_MODEL='virtio' and the system is quit unstable. This might be a similar issue to

Re: [Spice-devel] Usbredirection problem with digital signature pendrive

2013-02-21 Thread Hans de Goede
Hi, On 02/21/2013 04:18 PM, Fabio Fantoni wrote: I have a problem with usb digital signature device with usbredirection. I have enabled on spicy Options-Auto redirect newly plugged in USB devices. The devices that I'm trying to redirect contains 2 components: Bus 002 Device 014: ID 1307:0163