spice vdagent protocol, was Re: [Qemu-devel] KVM call minutes for Jan 11

[Alon Levy]

On Tue, Jan 11, 2011 at 07:53:40AM -0800, Chris Wright wrote:
> KVM Forum 2011
> - expand the scope? yes, continue up the stack
> - how long?  2 days (maybe 2 1/2 - 3 space permitting)
> - where?  Vancouver with LinuxCon
> 
> Spice guest agent:
> - virt agent, matahari, spice agent...what is in spice agent?
> - spice char device
>   - mouse, copy 'n paste, screen resolution change
> - could be generic (at least input and copy/paste)
>   - send protocol details of what is being sent
> - need to look at how difficult it is to split it out from spice
>   (how to split out in qemu vs. libspice)
> - goal to converge on common framework
> - more discussion on char device vs. protocol
>   - eg. mouse_set breaks if mouse channel is part pv and part spice specific
> - Alon will send link to protocol and try to propose new interfaces

http://spice-space.org/page/Whiteboard/AgentProtocol

That's the corrent documentation. Notably the clipboard is a todo there, I'll
try to get that filled in. I'll continue this discussion on a separate thread 
later.

Alon

> 
> migration and block devices:
> - need to invalidate data after first read on target,
>   because it can be stale
> - close + reopen is what was done for NFS
> - iscsi: can issue ioctl(BLKFLSBUF) to flush, but it's CAP_SYS_ADMIN only
> - O_DIRECT to avoid cache (concerns that it's not guaranteed)
> - agree change the default (cache=none for 
> 
> qemu patch queue is long:
> - slow to return from break
> - patience and more patch review will help make sure things are applied
>   and don't fall through cracks
>