Hello
I've two environnement
the first with qemu 1.5.3 has no problem,
the second with qemu 1.7rc0, display a white cursor in edit zone of
guest windows ( url bar in firefox for example )
Guest : windows Seven
QXL : last stable drivers
Qemu : 1.5.3| 1.7rc0
linux kernel : 3.11.6
Spicy People,
I have some feedback on my experiences with spicy software. Hopefully
this helps the development in some way.
I compiled the following on my slackware 14.1 host:
spice-protocol-0.12.6
spice-0.12.4
spice-gtk-0.21
virt-viewer-0.5.7
When I use the spicec client the vm works fine, ho
From: Marc-André Lureau
Make it easier later to send customized clipboard message
---
src/vdagentd.c | 50 +-
1 file changed, 29 insertions(+), 21 deletions(-)
diff --git a/src/vdagentd.c b/src/vdagentd.c
index cfb7acc..eed183b 100644
--- a/src/vd
From: Marc-André Lureau
---
src/vdagentd.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/vdagentd.c b/src/vdagentd.c
index eed183b..2eb97cb 100644
--- a/src/vdagentd.c
+++ b/src/vdagentd.c
@@ -459,6 +459,9 @@ int do_agent_clipboard(struct udscs_connection *conn,
size = 0;
From: Marc-André Lureau
Do not send clipboard data bigger than last received
VDAgentMaxClipboard.
There is no need to further limit at the session agent, since it is
already OOM safe, and since marhsalling/sending is local, that shouldn't
make any stability or speed difference that deserves the
Hi,
Here is a small series implementing VD_AGENT_CAP_MAX_CLIPBOARD behaviour.
Marc-André Lureau (3):
Add a virtio_write_clipboard() function
Add a warning for unhandled case
Add VD_AGENT_CAP_MAX_CLIPBOARD support
src/vdagentd.c | 68
- Original Message -
> On Wed, Nov 13, 2013 at 10:13:10PM +0100, Marc-André Lureau wrote:
> > When migrating a channel, all channels are disconnected during reset()
> > after MAIN_MIGRATED_END. The channel swap on destination will happen
> > only after MAIN_INIT is completed. During that
On Wed, Nov 13, 2013 at 10:13:10PM +0100, Marc-André Lureau wrote:
> When migrating a channel, all channels are disconnected during reset()
> after MAIN_MIGRATED_END. The channel swap on destination will happen
> only after MAIN_INIT is completed. During that time, the channel
> coroutine can be wa
