On Mon, Nov 07, 2016 at 10:53:38AM +0100, Thorsten Kohfeldt wrote: > > 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 ? Ah, updated in that way. Yes. I thought you were saying they should be different between different fedora builders. > > > > > > 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. Ah, this really is not important, I would not recommend rawhide in case of potential breakage there, otherwise any versions should do (and if not, there's a bug somewhere ;) > > 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) ? I believe server-side/client-side mouse is what is currently broken in the wddm driver and what is causing the slowness. So I would not focus on this too much right now. > > > > > > 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 ? ;^) Dunno, maybe, maybe not. Note that I did not say this should replace the unpacked drivers, just that it would be better than the monolithic spice-guest-tools installer we have now. > > 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. Yeah, "provided in a certain manner", if you ask me that's not a good way at all as obscure manual steps are needed to have something which works. Christophe
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/spice-devel