This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2084003 - [virtual network][windows]Sometimes windows guest can not get ip after the disable&enable interface
Summary: [virtual network][windows]Sometimes windows guest can not get ip after the di...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virtio-win
Version: 9.1
Hardware: Unspecified
OS: Windows
medium
medium
Target Milestone: rc
: ---
Assignee: ybendito
QA Contact: Lei Yang
Parth Shah
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-11 07:54 UTC by Lei Yang
Modified: 2023-10-08 02:32 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
.Windows VM fails to get IP address after network interface reset Sometimes, Windows virtual machines fail to get an IP address after an automatic network interface reset. As a consequence, the VM fails to connect to the network. To work around this problem, disable and re-enable the network adapter driver in the Windows Device Manager.
Clone Of:
Environment:
Last Closed: 2023-10-08 02:32:02 UTC
Type: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-11366 0 None None None 2023-10-08 06:50:37 UTC
Red Hat Issue Tracker RHELPLAN-121676 0 None None None 2023-10-08 06:50:37 UTC
Red Hat Issue Tracker RHELPLAN-168002 0 None None None 2023-10-08 02:24:03 UTC

Description Lei Yang 2022-05-11 07:54:25 UTC
Description of problem:
Sometimes windows guest can not get ip after the disable&enable interface.
This problem only occurs occasionally, but the current case has a higher chance of reproducee. Also, the problem can only be reproduced with auto. So far, QE has not been able to reproduce this issue manually.

Version-Release number of selected component (if applicable):
qemu-kvm-6.2.0-13.module+el8.7.0+15131+941fbd8d.x86_64
kernel-4.18.0-388.el8.x86_64
virtio-win-prewhql-0.1-215.iso

How reproducible:
3/10

Steps to Reproduce:
1.Boot a windows guest
/usr/libexec/qemu-kvm \
-name 'avocado-vt-vm1'  \
-sandbox on  \
-machine q35,memory-backend=mem-machine_mem \
-device pcie-root-port,id=pcie-root-port-0,multifunction=on,bus=pcie.0,addr=0x1,chassis=1 \
-device pcie-pci-bridge,id=pcie-pci-bridge-0,addr=0x0,bus=pcie-root-port-0  \
-nodefaults \
-device VGA,bus=pcie.0,addr=0x2 \
-m 7168 \
-object memory-backend-ram,size=7168M,id=mem-machine_mem  \
-smp 6,maxcpus=6,cores=3,threads=1,dies=1,sockets=2  \
-cpu 'Haswell-noTSX-IBRS',vme=on,ss=on,vmx=on,pdcm=on,f16c=on,rdrand=on,hypervisor=on,arat=on,tsc-adjust=on,umip=on,md-clear=on,stibp=on,arch-capabilities=on,ssbd=on,xsaveopt=on,pdpe1gb=on,abm=on,ibpb=on,ibrs=on,amd-stibp=on,amd-ssbd=on,skip-l1dfl-vmentry=on,pschange-mc-no=on,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=on \
-device pcie-root-port,id=pcie-root-port-1,port=0x1,addr=0x1.0x1,bus=pcie.0,chassis=2 \
-device qemu-xhci,id=usb1,bus=pcie-root-port-1,addr=0x0 \
-device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \
-device pcie-root-port,id=pcie-root-port-2,port=0x2,addr=0x1.0x2,bus=pcie.0,chassis=3 \
-device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pcie-root-port-2,addr=0x0 \
-blockdev node-name=file_image1,driver=file,auto-read-only=on,discard=unmap,aio=threads,filename=/root/avocado/data/avocado-vt/vl_avocado-vt-vm1_image1.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 pcie-root-port,id=pcie-root-port-3,port=0x3,addr=0x1.0x3,bus=pcie.0,chassis=4 \
-device virtio-net-pci,ctrl_mac_addr=off,mac=9a:56:ac:fc:24:87,id=idtJYgks,mq=on,vectors=10,netdev=idrLM4I1,bus=pcie-root-port-3,addr=0x0  \
-netdev tap,id=idrLM4I1,vhost=on,queues=4 \
-blockdev node-name=file_cd1,driver=file,auto-read-only=on,discard=unmap,aio=threads,filename=/home/kvm_autotest_root/iso/windows/winutils.iso,cache.direct=on,cache.no-flush=off \
-blockdev node-name=drive_cd1,driver=raw,read-only=on,cache.direct=on,cache.no-flush=off,file=file_cd1 \
-device scsi-cd,id=cd1,drive=drive_cd1,write-cache=on  \
-vnc :0  \
-rtc base=localtime,clock=host,driftfix=slew  \
-boot menu=off,order=cdn,once=c,strict=off \
-enable-kvm \
-device pcie-root-port,id=pcie_extra_root_port_0,multifunction=on,bus=pcie.0,addr=0x3,chassis=5 \
-monitor stdio \

2.Changing MAC address to 9a:56:ac:fc:24:88
reg add HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0001 /v NetworkAddress /d 9a56acfc2488  /f

3.Verify the new mac address, and restart the network, nic can not get ip adress
netsh interface set interface name="Ethernet Instance 0" admin=DISABLED
netsh interface set interface name="Ethernet Instance 0" admin=ENABLED


C:\Windows\system32> ipconfig /all


Windows IP Configuration

Host Name . . . . . . . . . . . . : WIN-OEEN089EBML
Primary Dns Suffix  . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No


C:\Windows\system32>


Actual results:
Sometimes windows guest can not get ip after the disable&enable interface

Expected results:
Get ip address

Additional info:

Comment 3 Yvugenfi@redhat.com 2022-08-16 14:50:46 UTC
What happen when you issue ipconfig /renew command?

Is there a problem with DHCP server in QE lab (this is something we were told during team meeting)?

Comment 4 Lei Yang 2022-08-22 02:43:48 UTC
(In reply to Yvugenfi from comment #3)
> What happen when you issue ipconfig /renew command?
Haven't tried this, I will add this command in the future when I hit problems again.
> 
> Is there a problem with DHCP server in QE lab (this is something we were
> told during team meeting)?
The QE lab's DHCP server works well when I encountered this problem.

Thanks
Lei

Comment 6 Lei Yang 2022-09-14 03:55:51 UTC
Hit same issue.

Test Version:
qemu-kvm-7.1.0-1.el9.x86_64
kernel-5.14.0-162.el9.x86_64
virtio-win-prewhql-0.1-225.iso

Comment 7 Lei Yang 2022-10-11 11:53:27 UTC
Hit same issue

Test Version:
kernel-5.14.0-174.el9.x86_64
qemu-kvm-7.1.0-2.el9.x86_64
edk2-ovmf-20220526git16779ede2d36-4.el9.noarch
virtio-win-prewhql-0.1-227.iso

Comment 17 Lei Yang 2022-12-21 05:20:11 UTC
Hit same issue

Test Version:
virtio-win-prewhql-0.1-231.iso
qemu-kvm-7.2.0-1.el9.x86_64
kernel-5.14.0-217.el9.x86_64
edk2-ovmf-20220826gitba0e0e4c6a-2.el9.noarch

Comment 24 Lei Yang 2023-03-02 05:39:46 UTC

*** This bug has been marked as a duplicate of bug 1958175 ***

Comment 25 Lei Yang 2023-03-02 06:24:14 UTC
Please ignore Comment 23 and 24, this is a mistake, they not dup problem, since this problem does not involve hotplug. Let's continue monitoring it.

Comment 29 RHEL Program Management 2023-10-08 02:32:02 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.


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