Installer placement on the ISO filesystem can lead to user confusion about virtio-win-pkg-scripts HOT 9 OPEN

In addition to virtio-win msi the virtio-win tools bundle installs qemu guest and spice agents.
But we are planing to remove spice from the bundle in the next release.

from virtio-win-pkg-scripts.

@rgl
qxl can be replaced with virtio-gpu (viogpudo.sys). There is no replacement for spice/copy&paste feature,
But dynamic desktop resolution feature can be activated by installing vgpusrv service. It should work for
VMs running locally and over VNC.

Cheers,
Vadim.

from virtio-win-pkg-scripts.

I never knew this! What kind of drivers does the .exe install that the .msi does not?

I thought the .exe installed the tools for communicating with the Guest Agent, but if you dont use that feature, you are not missing any drivers AFAIK.

from virtio-win-pkg-scripts.

FWIW, the spice agent was dropped in virtio-win/virtio-win-guest-tools-installer@926dbac

@vrozenfe can you please explain why it was removed?

from virtio-win-pkg-scripts.

@rgl
The short answer is because we (Red Hat) don't support SPICE/qxl anymore.

The long answer is because currently we use almost the same building scripts and infrastructure to build both
upstream and downstream virtio-win packages. And since our downstream package doesn't need SPICE and QXL both of them were removed from the bundle. The same changes were done for both downstream and upstream packages.

Since this question was asked several times in the past, it looks as some upstream users still prefer to have SPICE and QXL components installed automatically. I will try to bring them back in the upstream installer in the next or one of the following releases.

Vadim.

from virtio-win-pkg-scripts.

@vrozenfe, that would be nice! thank you!

Is qxl/spice being replaced with something else?

Is there other combination that has an equivalent feature set (e.g. resizable desktop, copy&paste)?

from virtio-win-pkg-scripts.

This was a super weird decision, almost intentionally evil. For the longest time, I had no idea why my Windows guest wasn't performing correctly.

from virtio-win-pkg-scripts.