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 2028349 - [Win2022_vm][qede] The "Device Manager" shows QL41112 VF is working properly but no relevant network configuration values can be displayed in “ipconfig" cmdlet
Summary: [Win2022_vm][qede] The "Device Manager" shows QL41112 VF is working properly ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: qemu-kvm
Version: 9.0
Hardware: x86_64
OS: Windows
medium
medium
Target Milestone: rc
: ---
Assignee: Marek Kedzierski
QA Contact: Yanghang Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-02 05:45 UTC by Yanghang Liu
Modified: 2023-05-24 01:44 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-24 01:44:00 UTC
Type: ---
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-104518 0 None None None 2021-12-02 05:47:35 UTC

Description Yanghang Liu 2021-12-02 05:45:56 UTC 
Description of problem:
The "Device Manager" shows QL41112 VF is working properly but I can not get any QL41112 VF network configuration values after running ”ipconfig“ cmdlet in the terminal

Version-Release number of selected component (if applicable):
host:
5.14.0-22.el9.x86_64
qemu-kvm-6.1.0-8.el9.x86_6
edk2-ovmf-20210527gite1999b264f1f-7.el9.noarch
guest:
Windows Server 2022(21H2)


How reproducible:
100%

Steps to Reproduce:
1. import a Q35 + OVMF Win2022 domain

# virt-install --machine=q35 --noreboot --name=win2022  --boot=uefi  --boot nvram.template=/usr/share/edk2/ovmf/OVMF_VARS.fd  --network bridge=switch,model=virtio,mac=52:54:00:01:22:22  --memory=4096 --vcpus=4 --graphics type=vnc,port=5922,listen=0.0.0.0 --import --noautoconsole --disk path=/home/images/2022_q35_ovmf.qcow2,bus=virtio,cache=none,format=qcow2,io=threads,size=20


2. add a QL41112 VF into this Q35 + OVMF Win2022 domain 

# virsh attach-interface win2022 --type hostdev --source $vf_pci_address --managed --config

3. start the Q35 + OVMF Win2022 domain with a QL41112 VF 

# virsh start win2022

4. check the "Device Manager" 

The QL41112 VF can be found in the "Device Manager" and its deivce status is "This device is working properly"


5. Open "command prompt app" and then run the "ipconfig /all" cmdlet

C:\Windows\system32>ipconfig /all  <--- I can not get any related device info after running ”ipconfig“ cmdlet in the terminal


Actual results
I can not get any QL41112 VF network configuration values after running ”ipconfig“ cmdlet in the terminal

Expected results:
The "ipconfig /all" can Displays all current QL41112 VF network configuration values.

Additional info:
Comment 1 Yanghang Liu 2021-12-09 03:11:23 UTC 
Use Q35 + Seabios + Win2022 vm to repeat the step 1 to step 5：
    This problem *can* be reproduced.


Use Q35 + OVMF + Win11 vm to repeat the step 1 to step 5：
    This problem *can not* be reproduced.
Comment 3 Yanghang Liu 2022-01-11 08:00:13 UTC 
This problem can be reproduced in the following test env:
5.14.0-39.el9.x86_64
qemu-kvm-6.2.0-2.el9.x86_64
edk2-ovmf-20210527gite1999b264f1f-7.el9.noarch
seabios-bin-1.15.0-1.el9.noarch
Comment 4 Yanghang Liu 2022-07-19 03:58:10 UTC 
> Steps to Reproduce:
> 1. import a Q35 + OVMF Win2022 domain
> 
> # virt-install --machine=q35 --noreboot --name=win2022  --boot=uefi  --boot
> nvram.template=/usr/share/edk2/ovmf/OVMF_VARS.fd  --network
> bridge=switch,model=virtio,mac=52:54:00:01:22:22  --memory=4096 --vcpus=4
> --graphics type=vnc,port=5922,listen=0.0.0.0 --import --noautoconsole --disk
> path=/home/images/2022_q35_ovmf.qcow2,bus=virtio,cache=none,format=qcow2,
> io=threads,size=20
> 
> 
> 2. add a QL41112 VF into this Q35 + OVMF Win2022 domain 
> 
> # virsh attach-interface win2022 --type hostdev --source $vf_pci_address
> --managed --config
> 
> 3. start the Q35 + OVMF Win2022 domain with a QL41112 VF 
> 
> # virsh start win2022
> 
> 4. check the "Device Manager" 
> 
> The QL41112 VF can be found in the "Device Manager" and its deivce status is
> "This device is working properly"
> 
> 
> 5. Open "command prompt app" and then run the "ipconfig /all" cmdlet
> 
> C:\Windows\system32>ipconfig /all  <--- I can not get any related device
> info after running ”ipconfig“ cmdlet in the terminal



It seems that this bug has been fixed in the following test env:

host:
5.14.0-127.el9.x86_64
qemu-kvm-7.0.0-7.el9.x86_64
seabios-bin-1.16.0-3.el9.noarch
edk2-ovmf-20220526git16779ede2d36-1.el9.noarch

guest:
Windows Server 2022 21H2


The related check point info:
administrator@WIN-A1AR6C3G7HJ C:\Users\Administrator>ipconfig /all

...
Ethernet adapter Ethernet 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : QLogic FastLinQ QL41112-DE 10GbE Adapter (VBD Client SR-IOV VF)
   Physical Address. . . . . . . . . : 52-54-00-21-2D-F3
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::cc73:c3a0:ecfc:d6c9%28(Preferred) 
   IPv4 Address. . . . . . . . . . . : 192.168.200.231(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Tuesday, July 19, 2022 3:49:22 AM
   Lease Expires . . . . . . . . . . : Wednesday, July 20, 2022 3:49:21 AM
   Default Gateway . . . . . . . . . : 192.168.200.254
   DHCP Server . . . . . . . . . . . : 192.168.200.254
   DHCPv6 IAID . . . . . . . . . . . : 475157504
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-29-3A-24-B9-9A-9B-AB-AE-4E-E3
   DNS Servers . . . . . . . . . . . : 192.168.200.2
Comment 5 Yanghang Liu 2022-07-19 04:03:55 UTC 
Hi Marek,

Could we close this bug as CURRENTRELEASE based on the Comment 4 ?
Comment 6 Yanghang Liu 2023-04-06 09:25:17 UTC 
The reason why the two test results in comment 0 and comment 4 are different is :  I have updated windows qede driver manually


Comment 0:

  Test scenario : start a Q35 + OVMF Win2022 domain with a QL41112 VF

  Test Result :  <--- It's not an expected result from QE's view

    1. The QL41112 VF can be found in the "Device Manager" and its device status is "This device is working properly"

    2. I can not get any related device info after running "C:\Windows\system32>ipconfig /all" 

Comment 4:

  Test scenario : start a Q35 + OVMF Win2022 domain with a QL41112 VF and then install its driver via Windows_DriverInstaller_45xxx_41xxx_20.80.1.14.zip

  Test Result :  Both "Device Manager" and "ipconfig" cmdlet show QL41112 VF info correctly
Comment 7 Yanghang Liu 2023-04-06 09:30:38 UTC 
Hi Marek,

Could you please check comment 6 ?

I'm not sure if this bug can be closed as NOTOBUG or  if we can do something to resolve the Comment 0's issue to avoid the confusion.

From QE's view , the info in "Device Manager" and "ipconfig" cmdlet should always be consistent.
Note You need to log in before you can comment on or make changes to this bug.