virtio-win / virtio-win-pkg-scripts Goto Github PK

Windows 10 Pro
Driver 1.208
Eats up all memory

I used the windows 2008 R2 ISO to install my vm and the disk used virtio technology。I downloaded the virtio-win-0.1.185.iso and attached a cdrom included it to my vm。

when installing the os, windows finds no suitabe driver file in the cdrom.

cannot find driver:

Environment

• Proxmox VM
• OS Name: Microsoft Windows Server 2012 R2 Standard
• Windows Version = "6.3.9600.18969"

Issue
Impossible to install driver on this path .\NetKVM\2k12R2\amd64\

Windows message
Windows found driver software for your device but encountered an error while attempting install it.
Red Hat VirtIO Ethernet Adapter
A problem was encountered while attempting to add the driver to the store.

Workaround
It's working with the driver 2008 R2 (.\NetKVM\2k8R2\amd64)

Source driver
virtio-win-0.1.217.iso

Hi, I want to install some drivers for Windows Server 2008 R2 VM, using autounattend.xml file to automatically install my needed drivers.

My desired drivers were installed successfully, but when I want to install the ballooning driver located in iso virtio image, I face with error shown here:

I used the latest stable version of virtio-win.iso linked in repository. Also I used old versions but I faced with same error.
I would be appreciate if you help me.

As of writing, README.md says in section "virtio-win driver signatures":

All the Windows binaries are from builds done on Red Hat’s internal build system, which are generated using publicly available code. Windows 8+ drivers are cryptographically signed with Red Hat’s test signature Windows 10+ drivers are signed with Microsoft attestation signature. However they are not signed with Microsoft’s WHQL signature. WHQL signed builds are only available with a paid RHEL subscription.

Is this section still correct? There are (3rd-party) sites claiming that already since version 0.1.204 (July 2021), the virtio-win drivers would be WHQL-signed. May I kindly ask you to comment on this and/or to clarify the current status, please?

This shows when I run virtio-win-guest-tools.exe /?:

Are these all the possible options? I can't enlarge the window so I am not sure

We're using these drivers, installing them in unattended mode. I've noticed what NetKVM and viostor driver packages for:

xp
2k3
w7
2k8
2k8R2

are refusing to install in unattended mode. I've checked them using SignTool and they aren't passing the verification:

`
d:\virtio-win-0.1.185\viostor\2k8\amd64>SignTool verify /v /c viostor.cat /pa viostor.sys viostor.inf

Verifying: viostor.sys
File is signed in catalog: viostor.cat
Hash of file (sha1): 2846A614D102616D1D4A8EE8039124DA2BFEB05E

Signing Certificate Chain:
Issued to: VeriSign Universal Root Certification Authority
Issued by: VeriSign Universal Root Certification Authority
Expires: Wed Dec 02 02:59:59 2037
SHA1 hash: 3679CA35668772304D30A5FB873B0FA77BB70D54

    Issued to: Symantec Class 3 SHA256 Code Signing CA - G2
    Issued by: VeriSign Universal Root Certification Authority
    Expires:   Mon Jul 22 02:59:59 2024
    SHA1 hash: 1392E4C7FF25B9517E931077BBE2664DC87EF70D

        Issued to: Red Hat, Inc.
        Issued by: Symantec Class 3 SHA256 Code Signing CA - G2
        Expires:   Wed Jan 26 02:59:59 2022
        SHA1 hash: F01DAC89598C52D94FE8CA91187E1853947D115A

The signature is timestamped: Thu Jan 09 04:30:05 2020
Timestamp Verified by:
Issued to: VeriSign Universal Root Certification Authority
Issued by: VeriSign Universal Root Certification Authority
Expires: Wed Dec 02 02:59:59 2037
SHA1 hash: 3679CA35668772304D30A5FB873B0FA77BB70D54

    Issued to: Symantec SHA256 TimeStamping CA
    Issued by: VeriSign Universal Root Certification Authority
    Expires:   Sun Jan 12 02:59:59 2031
    SHA1 hash: 6FC9EDB5E00AB64151C1CDFCAC74AD2C7B7E3BE4

        Issued to: Symantec SHA256 TimeStamping Signer - G3
        Issued by: Symantec SHA256 TimeStamping CA
        Expires:   Fri Mar 23 02:59:59 2029
        SHA1 hash: A9A4121063D71D48E8529A4681DE803E3E7954B0

Successfully verified: viostor.sys

Verifying: viostor.inf
SignTool Error: File not found in the specified catalog.
SignTool Error: File not valid: viostor.inf

Number of files successfully Verified: 1
Number of warnings: 0
Number of errors: 1
`

The rest of the drivers (starting from w8/2012 and up to w10/2019) are passing the verification fine.
Due to this, for listed OS I have to roll drivers back to release virtio-win-0.1.141 - in this release, ALL packages are passing verification. So signatures clearly broke somewhere in between virtio-win-0.1.141 and virtio-win-0.1.185.

Also, additional issue - in w7 and 2k8R2 packages, in catalog file, there are wrong inf filename: netkvm_no_rsc.inf instead of netkvm.inf

I've tested only NetKVM and viostor driver packages but I'm suspecting it is the same for the other drivers too.

for slow connections, it would be great to have a possibility to download the drivers individually - and then only download the necessary drivers.

In Windows 2016 and 2019, after installing virtio-win-guest-tools.exe from virtio-win-0.1.208.iso the network stops working.

This happens while I'm building the image with packer from the Windows iso. Windows autounattended correctly finds the drivers and is able to install Windows. But, after Windows is installed, and execute virtio-win-guest-tools.exe is executed, and for some reason, while its running, the network goes down and the network adapter even disappears from Device Manager.

Please note that this worked correctly with virtio-win-0.1.190.iso.

Do you have any idea of what might the problem?

PS: It works fine with Windows 2022; but not for 2016 and 2019.

What's the last version of virtio wich support w7 ?

The direct links to both stable and latest point to virtio-win-0.1.215.iso at this time. The RedHat signature used to sign the drivers in that image expired on 1/25/2022. As a result I am unable to get the certificate installed as a root Trusted Publisher on a Windows client because it is rejected for expiry reasons.

Is there a new release available with a non-expired signature? Thank you.

Am unable to synchronize this repo on a CentOS Linux release 7.9.2009 (Core) host.

Relevant lines from dnf update --repo virtio-win-stable -v

Loaded plugins: builddep, changelog, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, needs-restarting, playground, repoclosure, repodiff, repograph, repomanage, reposync
DNF version: 4.0.9
cachedir: /var/cache/dnf
.....
repo: downloading from remote: virtio-win-stable
virtio-win builds roughly matching what was shipped in latest RHEL 0.0 B/s | 0 B 00:00
Cannot download 'https://fedorapeople.org/groups/virt/virtio-win/repo/stable': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried.
Failed to synchronize cache for repo 'virtio-win-stable', ignoring this repo.
No module defaults found
--> Starting dependency resolution
--> Finished dependency resolution
Dependencies resolved.
Nothing to do.
Complete!

On the same host am able to download repomd.xml using wget

wget -P /tmp/ https://fedorapeople.org/groups/virt/virtio-win/repo/stable/repodata/repomd.xml

Have tried running dnf clean all && dnf update but the error is still present.

yum update is no different though the error reported is a bit more informative.

.....
https://fedorapeople.org/groups/virt/virtio-win/repo/stable/repodata/repomd.xml: [Errno 12] Timeout on https://fedorapeople.org/groups/virt/virtio-win/repo/stable/repodata/repomd.xml: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
Trying other mirror.
https://fedorapeople.org/groups/virt/virtio-win/repo/stable/repodata/repomd.xml: [Errno 12] Timeout on https://fedorapeople.org/groups/virt/virtio-win/repo/stable/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')
Trying other mirror.
.....

Any pointers to what may be the cause of this error?

Update the issue seems to be resolved and I'm now able to download the files again. Optional fix: provide a mirror for these files.

Non of the provided links are working, it seems the website fedorapeople is not working.
Stable virtio-win ISO
Stable virtio-win RPM
Latest virtio-win ISO
Latest virtio-win RPM
Latest virtio-win-guest-tools.exe
virtio-win direct-downloads full archive with links to other bits like qemu-ga, a changelog, etc.

fedorapeople.org has a security policy called HTTP Strict Transport Security (HSTS), which means that Firefox can only connect to it securely. You can’t add an exception to visit this site.

Is your feature request related to a problem? Please describe.
The virtio-win-gt-x64.msi and virtio-win-gt-x86.msi installers are in the root directory of the ISO filesystem, even though they don't install all drivers like the virtio-win-guest-tools.exe installer does. That can create confusion among new users and cause them to install the wrong file.

Describe the solution you'd like
Move the virtio-*.msi installers to a subdirectory so it's clear the virtio-win-guest-tools.exe installer should be ran.

Describe alternatives you've considered
Make the virtio-*.msi installers return an error directing to run virtio-win-guest-tools.exe if they are ran directly by the user (by using a command line switch for example; not sure if it's technically possible or not).

Additional context
None.

Can you please tag the releases in this github repo?

That would make it easier to figure out what version of this repo corresponds to https://fedorapeople.org/groups/virt/virtio-win/CHANGELOG and to the iso file at https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.173-2/

BTW, I don't quite understood the relationship of this repo with https://github.com/virtio-win organization. Shouldn't this repo be in that org?

Currently there is an virtio-win-x86.msi and virtio-win-x64.msi, but shouldnt there also be a virtio-win-gt-arm64.msi?

Ofcourse the x64.msi can run on ARM because Win11 emulates the x64 instructions, but I assume it installs the wrong drivers when you execute it on Win11 for ARM.

Silent install with virtio-win-gt-x64.msi is not possible because windows is asking for trust on driver publisher.
If you store, in the first step, the certificate at cert:\LocalMachine\TrustedPublisher the install will work.

Meanwhile I use this powershell script before running msiexec:

$DriverPath = Get-Item "d:\virtio-win-0.1.173\*\2k12r2\amd64" 

$CertStore = Get-Item "cert:\LocalMachine\TrustedPublisher" 
$CertStore.Open([System.Security.Cryptography.X509Certificates.OpenFlags]::ReadWrite)

Get-ChildItem -Recurse -Path $DriverPath -Filter "*.cat" | % {
    $Cert = (Get-AuthenticodeSignature $_.FullName).SignerCertificate

    Write-Host ( "Added {0}, {1} from {2}" -f $Cert.Thumbprint,$Cert.Subject,$_.FullName )

    $CertStore.Add($Cert)
}

$CertStore.Close()

Describe the bug
Windows VM loses static IP address after upgrading virtio-win drivers.

To Reproduce
Upgrading virtio-win drivers tried on Windows Server 2016/2019/2022

Expected behavior
Configuration of network adapter is not lost

Screenshots

Host:

• Disto: Proxmox
• Kernel Linux 6.2.9-1-pve

Guest:

• Windows version
• virtio-win version virtio-win-0.1.229.iso

The upgrade to virtio-win 0.1.185-1 (from virtio-win 0.1.173-9) broke the spice/QXL automatic screen resizing (e.g. when I resize the virt-viewer window the Windows VM guest screen no longer resizes with it).

I'm testing this on a Ubuntu 20.04 host (virt-viewer 7.0; virtual machine manager 2.2.1; libvirt 6.0.0; qemu 4.2) while running a Windows 2019 server (with this month cumulative updates).

The package/vagrant environment that I use to test this is at https://github.com/rgl/windows-vagrant. In concrete, in these lines:

• https://github.com/rgl/windows-vagrant/blob/master/windows-2019.json#L53-L55
• https://github.com/rgl/windows-vagrant/blob/master/Vagrantfile.template#L9-L12
• https://github.com/rgl/windows-vagrant/blob/0593025e078c995ee71d38ea5683dcd08252673a/provision.ps1#L41-L71

https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso
NET::ERR_CERT_DATE_INVALID

Hi,

I would like to automate the installation and upgrade of VirtIO-drivers.

To get past the "Accept the RedHat-Certificate to install"-Popup I want to use certutil.exe to import the required certificate before running pnputil.
(see https://community.spiceworks.com/how_to/24713-silent-install-of-software-that-has-an-unsigned-driver ).

Can you please add the certificate in a folder or top-level on the ISO so it is easier to script the import/installation?

Best regards and Thanks
Rainer

I find it very useful to also have spice vdagent installed (as it automatically resizes the screen when I resize the virt-viewer window). Can you also include this in the iso?

Currently, I'm installing it in my base windows image as https://github.com/rgl/windows-2016-vagrant/blob/ca72c8cc59f0c3eb1acbacfa0130675ff02bca96/provision.ps1#L85-L97. Maybe the vdagent can also be included in the virtio-win-guest-tools-installer?

Hello.

Can you please give more information about usage? Maybe an example of builted directory?
Readme document not user friendly.

Morphin:~/Documents/iso:./make-driver-dir.py \
> ../iso/kvm-guest-drivers-windows-master/
ERROR: driver=qxldod ostuple=Win8/x64 not found in input=/home/morphin/Documents/iso/kvm-guest-drivers-windows-master/

I don't have qxldod drivers and i dont need that.

Currently WdfCoInstaller01011.dll only included for W8.11 virtio-input drivers.
It schould also be included for W2012R2 virtio-input driver folder.

Describe the bug
Same as #60
except the temporary solution doesn't work.

To Reproduce
Regular install

Expected behavior
Complete installation of virtio-win-guest-tools.

Screenshots

Host:

• Distro: Manjaro Linux
• Kernel version: 6.1.69-1-MANJARO x86_64
• QEMU version: 8.2.0-2
• QEMU command line: None, I start virt-manager
• libvirt version: 1:9 10.0-1
• libvirt XML

<channel type="spicevmc">
  <target type="virtio" name="com.redhat.spice.0" state="disconnected"/>
  <alias name="channel0"/>
  <address type="virtio-serial" controller="0" bus="0" port="1"/>
</channel>

Guest:

• Microsoft Windows 11 Pro
• 10.0.22000 Build 22000

Additional context

https://privatebin.io/?2edd40ce1daacf0d#FZe812pPpjHbUAN3fTeafPCuLi3g4tGSXSoYXBMq2H8B

virtio-win.spec pointed me to this repo.
I see there is no arm64 mentioned in virtio-win-pre-installable-drivers-win-10.xml

is it too late to catch the final train before 2021 or other deadline?
(context: https://docs.microsoft.com/en-us/windows-hardware/drivers/install/deprecation-of-software-publisher-certificates-and-commercial-release-certificates )

我使用了virtio-win-0.1.190.iso 最新版版本，vioscsi.sys出现黑屏 0xc0000428代码，无法进行GPT分区模式下启动引导

如果分区为MBR，则可以正常使用。

Description of problem:
The virtio-win.iso 2022-04-14 08:04 has somehow broken storage driver for Windows 2012R2.
The previous version (https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.215-1/virtio-win.iso) works without an issue.

Version-Release number of selected component (if applicable):
(stable) virtio-win.iso from 2022-04-14 08:04 (virtio-win-0.1.217-1)

How reproducible:
Always

Steps to Reproduce:

1. Start windows 2012R2 server installation in libvirt with virtio disk.
2. Try to locate storage driver on the virtio iso.

Actual results:
No storage driver is found

Expected results:
Driver is found, disk is recognized and installation can proceed.

Additional info:
This is regression against virtio-win-0.1.215-1.

Describe the bug
I install the RPM packages on my fedora box and not super tux cart and steam lag and hang every time I open them.

To Reproduce
install the RPM packages on the host and the guest. Install steam on the Gust (should be Linux) and then super tux kart. Nether of them should work. Both should hang shortly after lunching.

Expected behavior
They launch and work "semi" good.

Screenshots

Host:

• Disto: Fedora 38
• Kernel version: 6.3.8
• QEMU version: 7.2.1
• QEMU command line: ?
• libvirt version: 9.0.0
• libvirt XML file: ?

Guest:

• Fedora
• 0.1.229

Additional context
Add any other context about the problem here.

Originally filed here: https://bugzilla.redhat.com/show_bug.cgi?id=1353036

When downloading the .repo file from https://fedoraproject.org/wiki/Windows_Virtio_Drivers you'll see that it has gpgcheck=0 set. When setting to 1, installing any package from this repo will fail due to missing signatures.

Was attempting to setup windows 11 VM with .208 version and when I install the storage driver during the install process the system crashes out completely.
I attempt the same operations with .185 and it is working correctly.
There is something in the new driver that is incompatible with Windows 11 22000.282.

The repo meta data in latest, stable & source RPM repos are last updated 2020-06-11, i.e. dnf & yum clients will not download the most recent version stored in these repos.

• 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:

This is from a suggestion here: https://lists.fedoraproject.org/archives/list/[email protected]/message/VTZHQFZRGYUUWQUFEXO5O3USB4VN3AL2/

We should publish hashes or gpg signatures of the direct-download content

I try to update form 0.1.217-2 on 0.1.221 and i get error 0x80070643
I don't have secure boot enabled and with 0.1.271-2.iso install work fine

I put my log file but i don't find in log why the process crash...
Virtio-win-guest-tools_20220730132500.log

Anyone can help me please?

I just attempted to update my drivers in a Windows 11 guest using the x64 0.1.217 MSI and it fails and rolls back. Programs list still shows the old version of the drivers and guest software. After the failure the network adapter had no drivers and would not work. Had to mount the ISO in the VM and manually install the drivers from device manager for network and serial then update SCSI controller. All worked manually but MSI for drivers and EXE for guest tools still won't run. Attaching log file.

Please let me know how I can fix this broken install. Been using the MSI installer for years and from Windows 10 to now Windows 11 upgraded last year. Have updated previously on Windows 11 and worked fine.

Virtio-win-guest-tools_20220428230549_003_virtio_win_gt_x64.msi.log

Hi all,

Running W2K12 on KVM (Rocky 8.x host).

Downloaded latest iso and mounted it.
It persistently fails to install (though I followed the issue on deactivating three options) Red Hat VirtIO GPU DOD contoller.

Attaching screenshot and logs

qxl-wddm-dod driver for Win2012R2 shipped with 134 drivers iso is not signed while the driver shipped with 133-1 iso was signed properly.

Hi,
Actually this is not a issue, but just a question. Sorry for disturbing if this is not a proper place to ask question :).
I just download https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.217-1/virtio-win.iso , I want to know the git commit hash of https://github.com/virtio-win/kvm-guest-drivers-windows related with this virtio-win.iso. Where can i find this information ?
Thanks.

I could not get my windows 10 guest to detect virtio graphics card drivers (works as a normal VGA). I expect good acceleration with virtio vga. Are the drivers included or is there any alpha/beta I can use to test ?

I hope this is the right place for this issue.
A while back I opened this issue here: virtio-win/kvm-guest-drivers-windows#157

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

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

• Guest | OS: Windows 10.

• In host:

$ rpm -qi virtio-win | sed -n '2p;9p;13p'
Version     : 0.1.215
Signature   : (none)
Build Host  : panda
URL         : http://www.redhat.com/

'http://www.redhat.com/' | incorrect form. the correct form is 'https://www.redhat.com/'.

Hello. The RPM file – as stable version – obtained from this repository contains an unsigned package. I suspect the drivers contained in that package to be unsigned as well since a function depending on signed driver in order to be operational in guest, is not.

illustration in virt-manager | menu View.

Guest agent is not available which leads KVM to have option Autoresize VM with window to not be available as well.

I can't install the video driver for Windows 10 - I get code 52.
Is there anything I can do to make it work?

Hi,

you provide a .MSI for the guest-agent, but not for the Balloon Service.

If someone like the chocolatey package maintainer just loops over the directory structure and installs all the .INF files he will miss out on the blnsrv.exe.

Could you provide a proper .MSI for the blnsrv.exe please.

Thanks
Rainer