Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-109592

[virtio-win][viosock] viosock driver can not be updated from the window update server

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • No
    • Moderate
    • 1
    • rhel-virt-windows
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • Red Hat Enterprise Linux
    • RHEL-10.2 Pending
    • Pass
    • virtio-win-prewhql-0.1-290
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • x86_64
    • None

      Description of problem:

      Viosock can not update from the Windows update server

      Version-Release number of selected component (if applicable):

      kernel-6.12.0-103.el10.x86_64
      qemu-kvm-10.0.0-6.el10.x86_64
      edk2-ovmf-20250523-2.el10.noarch
      seabios-bin-1.16.3-7.el10.noarch
      virtio-win-prewhql-281.iso

      How reproducible:
      100%

      Steps to Reproduce:
      1. Boot a Win10 LTSC 1809 guest with a viosock device

      /usr/libexec/qemu-kvm \
      -name 'avocado-vt-vm3' \
      -machine q35 \
      -nodefaults \
      -vga std \
      -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \
      -device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 \
      -device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \
      -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \
      -device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 \
      -device pcie-root-port,port=0x15,chassis=6,id=pci.6,bus=pcie.0,addr=0x2.0x5 \
      -device pcie-root-port,port=0x16,chassis=7,id=pci.7,bus=pcie.0,addr=0x2.0x6 \
      -device pcie-root-port,port=0x17,chassis=8,id=pci.8,bus=pcie.0,addr=0x2.0x7 \
      -blockdev node-name=file_stg1,driver=file,cache.direct=on,cache.no-flush=off,filename=win10-64-2019-virtio.qcow2,aio=threads \
      -blockdev node-name=drive_stg1,driver=qcow2,cache.direct=on,cache.no-flush=off,file=file_stg1 \
      -device virtio-blk-pci,id=stg1,drive=drive_stg1,bus=pci.8,addr=0x0 \
      -device virtio-net-pci,mac=9a:36:83:b6:3d:05,id=idJVpmsF,netdev=id23ZUK6,bus=pci.3 \
      -netdev tap,id=id23ZUK6,vhost=on \
      -m 14336 \
      -smp 2,maxcpus=4 \
      -cpu 'Skylake-Server',hv_stimer,hv_synic,hv_vpindex,hv_reset,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv-tlbflush,+kvm_pv_unhalt \
      -device piix3-usb-uhci,id=usb -device usb-tablet,id=input0 \
      -vnc :10 \
      -rtc base=localtime,clock=host,driftfix=slew \
      -boot order=cdn,once=c,menu=off,strict=off \
      -enable-kvm \
      -qmp tcp:0:1231,server,nowait \
      -monitor stdio \
      -device vhost-vsock-pci,id=vhost1,guest-cid=6 \
      -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0 \

      2. Open the Windows Update service

      3. Try to update the viosck driver from the Windows Update server

      Actual results:
      viosock driver can not be updated from the Windows update server.

      Expected results:
      viosock driver can be updated from the Windows update server.

      Other information:
      We already pushed the 281 build (only for Win10 LTSC 1809) to the Windows update server and it takes effect.

              yvugenfi@redhat.com Yan Vugenfirer
              rhn-support-menli Menghuan Li
              Virt Windows SST Bugs Virt Windows SST Bugs
              Leidong Wang Leidong Wang
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: