Program virtio-win-guest-tools.exe fails to install into the guest

[Ricky-Tigg]

• Host | OS: Fedora (v.: latest). Installed components:

$ rpm -q qemu-kvm libvirt-daemon virt-manager | column
qemu-kvm-6.2.0-6.fc36.x86_64	libvirt-daemon-8.1.0-2.fc36.x86_64	virt-manager-4.0.0-1.fc36.noarch

Display in use in virt-manager | Instructions part of the XML file of that Qemu-KVM VM's settings.

<graphics type="spice" autoport="yes">
 <listen type="address"/>
 <image compression="off"/>
</graphics>

• Guest | OS: Windows 11. executed | virtio-win-guest-tools.exe v.: 0.1.217.

Note: no use-context. User has to improvise. Then i conceived file virtio-win-guest-tools.exe can be executed within guest.

Hello. The program invariably fails to install; message produced:

[vrozenfe]

The same issue as https://github.com/virtio-win/virtio-win-guest-tools-installer/issues/33 Please try disabling pvpanic, qemuserial and qemucfg.

In any case the problem will be fixed in the next build.

Best, Vadim.

[Ricky-Tigg]

Selecting option Will be installed on request for each of components pvpanic, qemufwcfg, and qemupciserial, leads to a successful installation.

[Remzi1993]

Selecting option Will be installed on request for each of components pvpanic, qemufwcfg, and qemupciserial, leads to a successful installation.

Thank you very much! This also helped me! For me the option stated: Will be installed when required

[nickp85]

This did not work for me in Windows 11, still failed and rolled back

[Pandiora]

This indeed worked for me and interestingly the power consumption went down by 20W. Err? I have already put quite some effort into finding out, how to install Windows 11, with crashes at different stages. VirtIO-GPU, like suggested by some YT-Channel, i.e. caused crashes. The NetKVM-Driver sometimes wasn't even able to install (during windows installation) or caused crashes. Just for testing purposes I even downloaded an english Windows 11-ISO and changed the language later, but even with that I have got the same problems.

It is still hard to tell what caused or solved all the problems for me - I'm now using the no-subscription repository for Proxmox and maybe this fixed something something. All in all installing Windows 11 via Proxmox was a pain in the arse for me and not straightforward like I expected and dozens of people claim. Maybe it is just the i9-12900K and all new hardware which causes such problems.

Thanks for the solution, it would have taken me hours over hours to figure this one out.

[Pandiora]

I need to step back from my previous assumptions: After dozens of tries I found out my RAM (profile) is faulty and caused a lot of errors, which probably weren't tied to faulty drivers. The issue with installing the Guest Agent still exists and hopefully gets fixed soon.

[dudefoxlive]

Selecting option Will be installed on request for each of components pvpanic, qemufwcfg, and qemupciserial, leads to a successful installation.

This worked to get the guest agent installed on my friends VM.

[Ricky-Tigg]

Planning to close reports of mine on this platform that remain open indefinitely in undone/unfixed states soon, rather than continuing to keep them in such states, which would not be healthy for the project owner.

[YanVugenfirer]

@vrozenfe

[Remzi1993]

Planning to close reports of mine on this platform that remain open indefinitely in undone/unfixed states soon, rather than continuing to keep them in such states, which would not be healthy for the project owner.

I don't understand this reasoning? If it's still not working as intended and people still experience this bug then why close it?

[vrozenfe]

I was absolutely sure that for Win10 family drivers this problem was fixed in 0.1.217-2 and is not reproducible in any of subsequent builds (0.1.221-1, 0.1.225-2, and 0.1.229-1). All stub-drivers in these builds are MS attestation signed.

Do you guys experience the same problem with one of the builds mentioned above?

Thanks, Vadim.

[Remzi1993]

I was absolutely sure that for Win10 family drivers this problem was fixed in 0.1.217-2 and is not reproducible in any of subsequent builds (0.1.221-1, 0.1.225-2, and 0.1.229-1). All stub-drivers in these builds are MS attestation signed.

Do you guys experience the same problem with one of the builds mentioned above?

Thanks, Vadim.

I haven't tested it again, but if you think this bug is fixed then you should close this issue.

[Ricky-Tigg]

$ dnf rq --installed --qf '%{name} | %{version}' qemu-kvm libvirt-daemon virt-manager | column
libvirt-daemon | 9.7.0	virt-manager | 4.1.0	qemu-kvm | 8.1.1

My latest attempt of installation of Windows edition 11 with its latest version 23H2 fails; freezing with no error on virt-manager; VM's settings: four vCPUs, 4096 MiB RAM, UEFI firmware: thus I won't be able to test the latest version of virtio-win-guest-tools.exe. Assuming though the issue fixed upon vrozenfe's latest comment.

[Folaht]

Selecting option Will be installed on request for each of components pvpanic, qemufwcfg, and qemupciserial, leads to a successful installation.

This does not work for me and I don't know how I can "roll back".

[Remzi1993]

$ dnf rq --installed --qf '%{name} | %{version}' qemu-kvm libvirt-daemon virt-manager | column
libvirt-daemon | 9.7.0	virt-manager | 4.1.0	qemu-kvm | 8.1.1

My latest attempt of installation of Windows edition 11 with its latest version 23H2 fails; freezing with no error on virt-manager; VM's settings: four vCPUs, 4096 MiB RAM, UEFI firmware: thus I won't be able to test the latest version of virtio-win-guest-tools.exe. Assuming though the issue fixed upon vrozenfe's latest comment.

So, if this happens why did you close this issue? Your reasoning, previously stated one, to close issues does not make any sense especially because project owners can also close issues.

This is why I get frustrated sometimes with open source, some people have strange reasons for doing things.

Edit: I'm almost tempted to test another installation and post the issue myself if it's replicatable, but I'm too lazy.