RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2070400 - [virtio-win][netkvm]Network adapter in device manager is stuck after install driver with Installer
Summary: [virtio-win][netkvm]Network adapter in device manager is stuck after install ...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virtio-win
Version: 9.0
Hardware: x86_64
OS: Windows
high
high
Target Milestone: rc
: ---
Assignee: Kostiantyn Kostiuk
QA Contact: Ke Ma
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-31 04:57 UTC by leidwang@redhat.com
Modified: 2022-10-27 14:10 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-27 14:09:55 UTC
Type: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-117431 0 None None None 2022-03-31 05:05:38 UTC

Description leidwang@redhat.com 2022-03-31 04:57:12 UTC
Description of problem:
The device in device manager is stuck in 'Windows is still setting up the class configuration for this device. (Code 56)'.

Version-Release number of selected component (if applicable):
kernel-5.14.0-1.7.1.el9.x86_64
qemu-kvm-6.0.0-13.el9_b.5.x86_64 
Win10_21H2_German_x64.iso
virtio-win-1.9.24-4.el8.iso

How reproducible:
100%

Steps to Reproduce:
Step1:Install the German version of Windows 10
/usr/libexec/qemu-kvm \
-name 'avocado-vt-vm1'  \
-sandbox on  \
-machine pc,memory-backend=mem-machine_mem  \
-nodefaults \
-device VGA,bus=pci.0,addr=0x2 \
-m 14336 \
-object memory-backend-ram,size=14336M,id=mem-machine_mem  \
-smp 24,maxcpus=24,cores=12,threads=1,dies=1,sockets=2  \
-cpu 'Skylake-Server',hv_stimer,hv_synic,hv_vpindex,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_frequencies,hv_runtime,hv_tlbflush,hv_reenlightenment,hv_stimer_direct,hv_ipi,+kvm_pv_unhalt \
-device ich9-usb-ehci1,id=usb1,addr=0x1d.0x7,multifunction=on,bus=pci.0 \
-device ich9-usb-uhci1,id=usb1.0,multifunction=on,masterbus=usb1.0,addr=0x1d.0x0,firstport=0,bus=pci.0 \
-device ich9-usb-uhci2,id=usb1.1,multifunction=on,masterbus=usb1.0,addr=0x1d.0x2,firstport=2,bus=pci.0 \
-device ich9-usb-uhci3,id=usb1.2,multifunction=on,masterbus=usb1.0,addr=0x1d.0x4,firstport=4,bus=pci.0 \
-device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \
-device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x3 \
-cdrom /home/Win10_21H2_German_x64.iso \
-blockdev node-name=file_image1,driver=file,auto-read-only=on,discard=unmap,aio=threads,filename=/home/win10-german.qcow2,cache.direct=on,cache.no-flush=off \
-blockdev node-name=drive_image1,driver=qcow2,read-only=off,cache.direct=on,cache.no-flush=off,file=file_image1 \
-device scsi-hd,id=image1,drive=drive_image1,write-cache=on \
-device virtio-net-pci,mac=9a:0e:20:83:e2:d4,id=idzITtFW,netdev=idGFMiL4,bus=pci.0,addr=0x4  \
-netdev tap,id=idGFMiL4,vhost=on \
-monitor stdio \
-vnc :9  \
-rtc base=localtime,clock=host,driftfix=slew  \
-boot menu=off,order=cdn,once=c,strict=off \
-drive file=/home/virtio-win.iso,if=none,media=cdrom,id=ide-cdrom0 \
-device ide-cd,drive=ide-cdrom0,id=cdrom0 \
-enable-kvm

Step2:Use virtio-win-guest-tools to install driver

Actual results:
The device in device manager is stuck in 'Windows is still setting up the class configuration for this device. (Code 56)'.
Expected results:
The network device is not in code 56 state and a network adapter to appear
Additional info:
This problem only seems to happen on the German versions of Windows, as I haven't reproduced the problem on the US version of Windows.

Comment 1 Vadim Rozenfeld 2022-03-31 06:34:47 UTC
also reported upstream 
https://github.com/virtio-win/kvm-guest-drivers-windows/issues/745

Comment 2 leidwang@redhat.com 2022-03-31 07:17:21 UTC
QE does not test German Windows,so mark qe_test_coverage to -.Thanks!

Comment 11 Kostiantyn Kostiuk 2022-10-27 08:20:04 UTC
It looks like a general issue with German Windows and NICs.

https://answers.microsoft.com/en-us/windows/forum/all/network-adapters-not-working-code-56/381f4ed4-ab40-4b10-8606-f5231384bc88


Note You need to log in before you can comment on or make changes to this bug.