___
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel
On Thu, Jan 13, 2011 at 08:52:38AM +0100, Hans de Goede wrote:
> Hi,
>
> Hi,
>
> On 01/13/2011 06:01 AM, Alon Levy wrote:
>
>
>
> >-static void inputs_pipe_add_init(InputsChannel *channel)
> >+static void inputs_pipe_add_init(InputsChannel *inputs_channel)
> > {
> >-SpiceMsgInputsInit inp
On 01/13/2011 11:13 AM, Alexander Graf wrote:
Yes, I had intended to do that but left it out.
Should it be a bitmask or just a button count? Buttons really have no standard
meaning so usually a button count is sufficient.
Some random thoughts:
* multitouch capabilities would be go
On 01/13/2011 11:08 AM, Gerd Hoffmann wrote:
On 01/13/11 16:55, Anthony Liguori wrote:
On 01/13/2011 05:51 AM, Gerd Hoffmann wrote:
On 01/13/11 12:01, Stefan Hajnoczi wrote:
Can you elaborate how the spice display channel comes into play? On a
physical machine you just have input devices with
On 01/13/2011 11:09 AM, Paolo Bonzini wrote:
On 01/13/2011 05:39 PM, Anthony Liguori wrote:
On 01/13/2011 10:14 AM, Avi Kivity wrote:
On 01/13/2011 05:52 PM, Anthony Liguori wrote:
/* host->guest, sent before any other events */
typedef struct qemu_pvtablet_init {
uint32_t res_x; /* x axis re
On Thu, Jan 13, 2011 at 01:44:50PM -0600, Adam Litke wrote:
> On Thu, 2011-01-13 at 21:18 +0200, Alon Levy wrote:
> > On Thu, Jan 13, 2011 at 09:01:34AM -0600, Adam Litke wrote:
> > > On Tue, 2011-01-11 at 20:33 +0200, Alon Levy wrote:
> > > > > Spice guest agent:
> > > > > - virt agent, matahari,
On Thu, 2011-01-13 at 21:18 +0200, Alon Levy wrote:
> On Thu, Jan 13, 2011 at 09:01:34AM -0600, Adam Litke wrote:
> > On Tue, 2011-01-11 at 20:33 +0200, Alon Levy wrote:
> > > > Spice guest agent:
> > > > - virt agent, matahari, spice agent...what is in spice agent?
> > > > - spice char device
> >
On 01/13/2011 07:19 PM, Gerd Hoffmann wrote:
On 01/13/11 17:18, Avi Kivity wrote:
On 01/13/2011 12:19 PM, Gerd Hoffmann wrote:
Hi,
Just throwing a quick writeup into the ring to kickstart the design
discussion ;)
typedef struct qemu_pvtablet_message {
uint32_t size; /* whole message size */
On 01/13/2011 12:19 PM, Gerd Hoffmann wrote:
Hi,
Just throwing a quick writeup into the ring to kickstart the design
discussion ;)
typedef struct qemu_pvtablet_message {
uint32_t size;/* whole message size */
uint32_t type;/* qemu_pvtablet_type */
uin
On 01/13/2011 05:52 PM, Anthony Liguori wrote:
/* host->guest, sent before any other events */
typedef struct qemu_pvtablet_init {
uint32_t res_x; /* x axis resolution */
uint32_t res_y; /* y axis resolution */
uint32_t features; /* qemu_pvtablet_features */
uint32_t available
On Thu, Jan 13, 2011 at 11:19:52AM +0100, Gerd Hoffmann wrote:
> Hi,
>
> Just throwing a quick writeup into the ring to kickstart the design
> discussion ;)
I apologize for not reading everything before sending, I just don't want
to forget this detail: Whatever we design needs to address having
On Thu, Jan 13, 2011 at 12:44:57PM +0200, Dor Laor wrote:
> On 01/13/2011 09:35 AM, Hans de Goede wrote:
> >Ack.
> >
> >On 01/13/2011 06:07 AM, Alon Levy wrote:
> >>---
> >>tests/migrate.py | 158
> >>++
>
> In the past you started with kvm autote
On Thu, Jan 13, 2011 at 08:36:46AM +0100, Hans de Goede wrote:
> Hi,
>
> On 01/13/2011 06:01 AM, Alon Levy wrote:
> >Patches for 0.7
>
> I hope / think you mean 0.9 / master, as we don't want to do
> anything potentially de-stabilizing to 0.7 now. So this is all
> for master, right ?
Right, yes
On Thu, Jan 13, 2011 at 08:52:38AM +0100, Hans de Goede wrote:
> Hi,
>
> Hi,
>
> On 01/13/2011 06:01 AM, Alon Levy wrote:
>
>
>
> >-static void inputs_pipe_add_init(InputsChannel *channel)
> >+static void inputs_pipe_add_init(InputsChannel *inputs_channel)
> > {
> >-SpiceMsgInputsInit inp
On Thu, Jan 13, 2011 at 09:01:34AM -0600, Adam Litke wrote:
> On Tue, 2011-01-11 at 20:33 +0200, Alon Levy wrote:
> > > Spice guest agent:
> > > - virt agent, matahari, spice agent...what is in spice agent?
> > > - spice char device
> > > - mouse, copy 'n paste, screen resolution change
> > > - c
On 01/13/11 17:18, Avi Kivity wrote:
On 01/13/2011 12:19 PM, Gerd Hoffmann wrote:
Hi,
Just throwing a quick writeup into the ring to kickstart the design
discussion ;)
typedef struct qemu_pvtablet_message {
uint32_t size; /* whole message size */
uint32_t type; /* qemu_pvtablet_type */
uint64
On 01/13/2011 05:39 PM, Anthony Liguori wrote:
On 01/13/2011 10:14 AM, Avi Kivity wrote:
On 01/13/2011 05:52 PM, Anthony Liguori wrote:
/* host->guest, sent before any other events */
typedef struct qemu_pvtablet_init {
uint32_t res_x; /* x axis resolution */
uint32_t res_y; /* y axis resoluti
On 13.01.2011, at 17:39, Anthony Liguori wrote:
> On 01/13/2011 10:14 AM, Avi Kivity wrote:
>> On 01/13/2011 05:52 PM, Anthony Liguori wrote:
>>>
>>> /* host->guest, sent before any other events */
>>> typedef struct qemu_pvtablet_init {
>>>uint32_t res_x; /* x axis resolution */
>>>ui
On 01/13/11 16:55, Anthony Liguori wrote:
On 01/13/2011 05:51 AM, Gerd Hoffmann wrote:
On 01/13/11 12:01, Stefan Hajnoczi wrote:
Can you elaborate how the spice display channel comes into play? On a
physical machine you just have input devices with no notion of
display. It's up to the windowin
On 01/13/2011 10:18 AM, Avi Kivity wrote:
On 01/13/2011 12:19 PM, Gerd Hoffmann wrote:
Hi,
Just throwing a quick writeup into the ring to kickstart the design
discussion ;)
typedef struct qemu_pvtablet_message {
uint32_t size;/* whole message size */
uint32_t type;
On 01/13/2011 10:14 AM, Avi Kivity wrote:
On 01/13/2011 05:52 PM, Anthony Liguori wrote:
/* host->guest, sent before any other events */
typedef struct qemu_pvtablet_init {
uint32_t res_x; /* x axis resolution */
uint32_t res_y; /* y axis resolution */
uint32_t features; /* qem
On 01/13/2011 05:51 AM, Gerd Hoffmann wrote:
On 01/13/11 12:01, Stefan Hajnoczi wrote:
Can you elaborate how the spice display channel comes into play? On a
physical machine you just have input devices with no notion of
display. It's up to the windowing system to process input events and
hand
On 01/13/2011 04:19 AM, Gerd Hoffmann wrote:
Hi,
Just throwing a quick writeup into the ring to kickstart the design
discussion ;)
cheers,
Gerd
#ifndef __QEMU_PVTABLET__
#define __QEMU_PVTABLET__ 1
/*
* qemu patavirtual tablet interface
*/
#include
/* our virtio-serial channel */
#
On 01/13/11 12:01, Stefan Hajnoczi wrote:
Can you elaborate how the spice display channel comes into play? On a
physical machine you just have input devices with no notion of
display. It's up to the windowing system to process input events and
handle multihead. Why does a pv tablet tie itself
Can you elaborate how the spice display channel comes into play? On a
physical machine you just have input devices with no notion of
display. It's up to the windowing system to process input events and
handle multihead. Why does a pv tablet tie itself to a display
channel?
What about mouse whee
Hi,
(4) termial forwarding. Just an idea right now. Nowdays that the spice
client side moves to gtk it would be easy to embed a termial widget,
therby allowing easy access to the serial console using something
like this:
-chardev spicevmc,id=console,type=terminal
On 01/13/2011 09:35 AM, Hans de Goede wrote:
Ack.
On 01/13/2011 06:07 AM, Alon Levy wrote:
---
tests/migrate.py | 158
++
In the past you started with kvm autotest.
Is your direction changed? We have several live migration tests, why not
inc
Am Mittwoch, den 12.01.2011, 17:12 +0100 schrieb Gerd Hoffmann:
> Hi folks,
>
> Looks like the spicevmc patch kicked the guest qagent discussion, so
> lets start with this, although it isn't related much to the agent issue
> itself ...
>
>
> The spicevmc chardev just pipes data from a chardev u
Hi,
Just throwing a quick writeup into the ring to kickstart the design
discussion ;)
cheers,
Gerd
#ifndef __QEMU_PVTABLET__
#define __QEMU_PVTABLET__ 1
/*
* qemu patavirtual tablet interface
*/
#include
/* our virtio-serial channel */
#define QEMU_PVTABLET_NAME "org.qemu.pvtablet.0"
Hi,
The VDAgentMouseState messages have one problem: They send the pointer
position as-is, which introduces a dependency on the screen size.
Yeah, if we could get rid of that, that would be great. We could even
introduce a new mouse message type to the existing spice vdagent protocol
and use
Hi,
The VDAgentMouseState messages have one problem: They send the pointer
position as-is, which introduces a dependency on the screen size.
Yeah, if we could get rid of that, that would be great. We could even
introduce a new mouse message type to the existing spice vdagent protocol
and use
Hi,
There isn't much spice-specific stuff in there. The clipboard bits
for example should work unmodified with vnc, one would just have to
hack up a vnc extention to tunnel the agent protocol over vnc (and vnc
client support of course).
VNC already supports copy/paste as part of the protocol
32 matches
Mail list logo
