Re: [Spice-devel] CEGUI xml error

2010-05-03 Thread Alexander Larsson
On Tue, 2010-05-04 at 08:49 +0200, Attila Sukosd wrote: > I managed to fix it by recompiling CEGUI with the Libxml parser and > now it works fine. > > Now I stumbled upon another issue using gl_fbo or gl_pbuff to render > on the client side: > canvas_get_mask: access violation 0x0 18 > Aborted T

Re: [Spice-devel] CEGUI xml error

2010-05-03 Thread Attila Sukosd
Hi again, On Mon, May 3, 2010 at 1:24 PM, Attila Sukosd wrote: > Hi all, > > I have compiled the spice client from the git repo on Ubuntu 9.04, but > when I try to launch it, nothing happens. It does create a CEGUI.log > and it seems  like it has a problem parsing the TaharezLook.scheme > file w

[Spice-devel] Questions on security.

2010-05-03 Thread Robert Relyea
Hi all, I've been asked to look at the security of the spice protocol. I've looked at the project a bit already and have a few potential things to talk about, but I wanted to understand some of the underlying assumptions before I get too far into it. First, I want to confirm that the protocol

Re: [Spice-devel] Banner

2010-05-03 Thread Izik Eidus
On Sun, 2 May 2010 13:35:22 + (UTC) Robert Rebstock wrote: > Hello all, > > can someone please tell me how to disable the "Red Hat Enterprise > Virtualization | SPICE" banner. > Currently no way to do so. But support for such thing can be easily added, I will look on it after I am will f

Re: [Spice-devel] libspice and save/restore/migration

2010-05-03 Thread Alexander Larsson
> Plan for unstable: > > (1) Keep surface metadata in device memory, i.e. delay the release of > QXL_SURFACE_CMD_CREATE command until the surface is destroyed. > (2) Keep the most recent QXL_CURSOR_SET command in device memory, i.e. > delay the release until the next one comes in. > (3)

Re: [Spice-devel] [PATCH] server: fix invalid self loop in surfaces dependencies.

2010-05-03 Thread Alexander Larsson
On Wed, 2010-04-28 at 18:26 +0300, Yonit Halperin wrote: > Cyclic dependencies between surfaces mustn't occur. They can cause invalid > rendering - > recent drawables might be rendered before older ones. Pushed to master ___ Spice-devel mailing list Sp

[Spice-devel] Banner

2010-05-03 Thread Robert Rebstock
Hello all, can someone please tell me how to disable the "Red Hat Enterprise Virtualization | SPICE" banner. Many thanks in advance, RR PS. Please mail me directly, as I am not subscribed to this list. ___ Spice-devel mailing list Spice-devel@lists.f

Re: [Spice-devel] C version of find_msb()

2010-05-03 Thread Alexander Larsson
On Sat, 2010-05-01 at 22:25 -0600, Bryan Stillwell wrote: > Recently I tried building the Ubuntu SPICE packages on powerpc and found > that the spicec package fails on some x86 assembly code in > common/gl_utils.h. This motivated me to create an optimized C version > of the find_msb() function, wh

Re: [Spice-devel] C version of find_msb()

2010-05-03 Thread Alexander Larsson
On Mon, 2010-05-03 at 11:30 +0200, Gerd Hoffmann wrote: > Hi, > > > This patch allows people to build the spice-client on any 32bit/64bit > > architecture, but it doesn't solve the endianess problems in the SPICE > > protocol itself. Has anyone looked into the network byte-ordering > > issues? >

[Spice-devel] CEGUI xml error

2010-05-03 Thread Attila Sukosd
Hi all, I have compiled the spice client from the git repo on Ubuntu 9.04, but when I try to launch it, nothing happens. It does create a CEGUI.log and it seems like it has a problem parsing the TaharezLook.scheme file which is I guess define in the taharez_look.scheme.c. I have even tried creat

Re: [Spice-devel] C version of find_msb()

2010-05-03 Thread Gerd Hoffmann
Hi, This patch allows people to build the spice-client on any 32bit/64bit architecture, but it doesn't solve the endianess problems in the SPICE protocol itself. Has anyone looked into the network byte-ordering issues? spice protocol (on the wire) is defined to be little endian. Alexander

[Spice-devel] libspice and save/restore/migration

2010-05-03 Thread Gerd Hoffmann
Hi, I want change the way save/restore works for the qxl device. 0.4 works this way: savevm qxl: call worker->save() worker: call interface->set_save_data(data, size) qxl: save data block. loadvm qxl: load data block. qxl: call worker->load() worker: call