The QXL_IO_NOTIFY_OOM is intended exactly for handling occurrences of
lacking memory. The spice server tries to first release resources that
are no longer in the current tree (and thus, do not need rendering).
It renders drawables only as a last resort. And even then,
it does not update the whole
Hi,
On 04/22/2012 03:16 PM, Marc-André Lureau wrote:
Hi
On Sun, Apr 22, 2012 at 9:40 AM, Alon Levyal...@redhat.com wrote:
On Fri, Apr 20, 2012 at 01:59:05AM +0200, Marc-André Lureau wrote:
So it seems like we should keep sending repeat key press in fact. And
it's probably better to rely on
On 04/23/2012 09:52 AM, Uri Lublin wrote:
---
SpiceXPI/src/plugin/plugin.cpp | 25 -
1 files changed, 16 insertions(+), 9 deletions(-)
diff --git a/SpiceXPI/src/plugin/plugin.cpp b/SpiceXPI/src/plugin/plugin.cpp
index 8acde24..76f2768 100644
---
Hi,
Thanks for letting me know, I've rebased my patches to
qemu-kvm-1.0.1, you can find a branch with the result here:
http://cgit.freedesktop.org/~jwrdegoede/qemu/log/?h=qemu-kvm-1.0.1-usbredir
Note that this is where future development will happen.
Regards,
Hans
On 04/20/2012 05:33 PM,
On Mon, Apr 23, 2012 at 09:04:36AM +0300, Yonit Halperin wrote:
The QXL_IO_NOTIFY_OOM is intended exactly for handling occurrences of
lacking memory. The spice server tries to first release resources that
are no longer in the current tree (and thus, do not need rendering).
It renders drawables
On Thu, Apr 19, 2012 at 09:30:59PM +0200, Marc-André Lureau wrote:
Hi
Somehow, it doesn' t work anymore without trailing /
Urgh, I broke it when cleaning up the patch for submission :-) Sending
a v4 now...
Daniel
--
|: http://berrange.com -o-http://www.flickr.com/photos/dberrange/
From: Daniel P. Berrange berra...@redhat.com
The URI parsing was not correctly skipping over the path component
if a port number was specified using the traditional URI scheme,
eg
spice://somehost:5900/
would result in failed parse due to the trailing '/'
The URI parsing was also not
ack, thanks
On Mon, Apr 23, 2012 at 6:39 PM, Daniel P. Berrange berra...@redhat.com wrote:
From: Daniel P. Berrange berra...@redhat.com
The URI parsing was not correctly skipping over the path component
if a port number was specified using the traditional URI scheme,
eg
Hi
I want to filter the graphics to the client. For example, only the
graphics of a calculator(in guest OS Win7) are send to the client.
I know that there is always the possibility of falling all the way back to
CPU drawing to a memory bitmap which is then copied to the client.
Now, I
Hi
I want to filter the graphics to the client. For example, only the
graphics of a calculator(in guest OS Win7) are send to the client.
I know that there is always the possibility of falling all the way back to
CPU drawing to a memory bitmap which is then copied to the client.
Now, I
10 matches
Mail list logo
