[Spice-devel] Spice Protocol Missing Headers

[geoff at hostfission.com]

> I tried a few years back (spice-protocol 0.12.10) to move these code
> generation scripts to spice-protocol, but this did not work out
> nicely so this was reverted.

I found this too, I opted to use the spice.proto file to write my own 
header
with the basics that were required.

> 
> I agree that having the initial link messages in spice/protocol.h, but
> not the rest of the protocol in spice-protocol is unexpected. For now, 
> I
> would suggest that you copy this messages.h file as you suggested, even
> if that's suboptimal. I don't expect that file to change that often.
> 
> Can you give more details about the project you are working on?

Sure :). I spend most of my time in a Linux environment for work but 
enjoy the odd game, so I figured I would give a Windows VM a go with VGA 
passthrough. It works a treat but the issue is getting a video feed back 
to the host, the solutions that are available IMO are substandard 
(ShadowPlay or Steam InHouse Streaming) as I want to have full control 
over the host as well, not just in games.

These services compress to h264 and stream it over the network, where it 
is decoded for display. Since this is all on the local host, I figured 
all those overheads could be bypassed by writing a windows driver that 
allows the host to share some memory mapped ram with the guest. Then on 
the guest I wrote an application that uses NvFBC to capture raw frames 
of the desktop and copy them into the shared memory segment.

This is why I needed a custom client, I am not using spice for the video 
feed, it's just there for mouse and keyboard input. The end result is 
outstanding, the latency is near zero and the video quality is lossless.