[Spice-devel] spice-vdagent-win 0.8.0 release

[Thorsten Kohfeldt]

Am 07.11.2016 um 10:21 schrieb Christophe Fergeau:
> On Mon, Nov 07, 2016 at 10:07:58AM +0100, Thorsten Kohfeldt wrote:
>>
>> BTW,
>> _all_ binaries' details state 'Version 0.5.1.0, copyright RH 2009'.
>> Here it would make sense to auto update with the build number, right ?
>
> Now only one build will be made, so no need for that ;)

Hmm ...
Shouldn't the Version read 0.8.0.1, copyright RH 2016 ?
Respectively, what ever you designate the VDA version in digit 0-3
plus build number in 4th place ?


>>> I've disabled all the various builders now and only kept f25 x86-64. For
>>> now, I would pick one of the f24 builds.
>>
>> Bad luck,
>> I tested Win10/x86 with the F23/x86 build and the rawhide/x86 build.
>>
>> Screen resize / auto guest resolution adaption seems to work (depending
>> on manual choice of F23 libvirt spice viewer menu settings) as well as
>> copy/paste of text guest->host and host->guest.
>>
>> NO improvement on mouse sluggishness though.
>
> Why "bad luck" ? Seems to be working as expected, I did not expect mouse
> slugginess improvements from these builds.

Bad luck I tested F23 and rawhide while you suggested F24.

So, there's no more function other than screen resizing and copy/paste ?
But it also provides the ability to handle the mouse cursor user-local
(as far as I understand from the wddm driver related discussion) ?


>> Would it be possible to add a post processing step to the build chain(s)
>> which rpm2cpio-extracts the 4 relevant binaries (service and agent in x86
>> and x64) into a single zip file (or maybe even skip the rpm2cpio but pack
>> the binaries directly after they were built),
>> so that zip file can be downloaded directly by the Windows guest ?
>
> Not really possible on copr, but yeah would be nicer for users. Though
> as far as I'm concerned, final product would be the spice-guest-tools
> installer, and iirc it's able to consume these directly.

See below, spice guest installer is convenient, but counter-productive
from a professional sense, as it fires a full installation broad side.
Production system maintainers (like me) might prefer surgical updates.


>>>> Or would we even get those released on the next Fedorapeople ISO (where
>>>> I currently cannot find them) ?
>>>
>>> Getting these on virtio-win ISO was discussed a bit, but never moved
>>> forward.
>>
>> I would really love to see that happen, i.e provision of the 4 binaries
>> I mentioned above in my rpm2cpio -> zip request (here raw, not zipped).
>>
>> That would allow to install Win drivers, Ballon Service and Spice VDAgent
>> consistently from one source without having to use the sledge hammer
>> Spice-Guest-Tools-1.xx.msi (or exe ?) from spice space.
>> Spice VDAgent seems to be the one missing set of key binaries on that ISO.
>
> Well, I'd push to have the spice-guest-tools installer on that ISO as
> well ;) Though imo it would be best to move towards single-driver .msi
> files, plus one installer installing all.

Eh, do single driver msi files support the Windows device manager driver
update auto-search-the-disk-for-drivers funtion ? ;^)

Anyway, the Ballon Service exe is already provided in a certain manner
on that ISO - not auto installing, but ready to be used by admin scripts.
Same should be true for Spice Service and VDAgent exes.
I envision that possible short-term as a minimum admin convenience ...
... more complex improvements to the ISO are asking for much more
patience due to necessary discussions etc, I guess ...

Regards

Thorsten


> Christophe