Bug 807967
Summary: | [virtio-win][netkvm]network can not get the ip after s3 or long disable\enable | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Mike Cao <bcao> |
Component: | virtio-win | Assignee: | Yvugenfi <yvugenfi> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.3 | CC: | acathrow, amit.shah, areis, bcao, bsarathy, dawu, dfleytma, dsirrine, dyasny, jasowang, mdeng, michen, mst, qzhang, rhod, virt-maint |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: Wrong initialization sequence of virtio-net on Windows
Consequence: Sometimes the first packets that were sent through the interface (DHCP client) were stack in the queue for a long time and thus DHCP client was failing to receive IP address.
Fix: Init sequence fixed.
Result: Network always works after power management event or disable\enable.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-21 10:38:23 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 761491 |
Description
Mike Cao
2012-03-29 09:09:27 UTC
Hello Mike, Do you know if this is a regression? Thanks, Yan. Hello Mike, Do you know if this is a regression? Thanks, Yan. (In reply to comment #3) > Hello Mike, > > Do you know if this is a regression? > > Thanks, > Yan. Hi, Yan hard to decide whether it is a regression for virtio-win ,because only hit it w/ the newer qemu-kvm which the s3 patches included more info you can referring to https://bugzilla.redhat.com/show_bug.cgi?id=803187#c7 and https://bugzilla.redhat.com/show_bug.cgi?id=803187#c9 Best Regards, Mike Hello Mike, I am trying to understand if this is a timeout issues that may indicate the problem on the host or this is a device\driver issues like in comment #4. Could you please test same scenario , but to wake up guest almost immediately? Thanks, Yan. (In reply to comment #5) > Hello Mike, > > I am trying to understand if this is a timeout issues that may indicate the > problem on the host or this is a device\driver issues like in comment #4. > > Could you please test same scenario , but to wake up guest almost immediately? > > Thanks, > Yan. Hi Yan, I tested what you said on a windows 2008 64 bits guest which can reproduce this bug steadily.But to wake up guest immediately the issue cannot be reproduced. The nic still was available. After reducing the sleeping time from 10 mins to about 5 mins it also was reproduced as well.Any issues please let me know. Thanks Min This bug can be reproduced on rhel6.3 guest as well when the "NetworkManager" service is starting inside guest. While stop NetworkManager service, this issue does not exist. File bug against rhel guest: Bug 811143 Moving to RHEL6.4 along with the other S3 issue. Same bug can bee reproduces if driver is disabled on the guest and re-enabled after 10 minutes. This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4. Should be in build 37. dengmin pls help to verify this bug on newest virtio-win-prewhql build Thanks, Mike QE verified the bug via build 41. Steps, 1.boot up guest - /usr/libexec/qemu-kvm -m 2G -smp 2 -drive file=/home/win2k8-R2-0724.raw,if=none,id=drive-virtio0-0-0,format=raw,werror=ignore,rerror=ignore,cache=none -device ide-drive,drive=drive-virtio0-0-0,id=virti0-0-0,bootindex=1 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=net0,mac=02:06:10:94:a3:f8 -device virtio-serial-pci,id=virtio-serial0 -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=channel0,name=org.linux-kvm.port.0,id=port0 -chardev socket,id=channel0,host=127.0.0.1,port=12340,server,nowait -chardev socket,id=channel1,host=127.0.0.1,port=19000,server,nowait -uuid 9e6f04cf-2ad7-45aa-9333-2d2ee26570c6 -monitor stdio -drive file=/home/disk1.raw,if=none,id=drive-virtio0-0-1,format=raw,werror=ignore,rerror=ignore,cache=none -device virtio-blk-pci,drive=drive-virtio0-0-1,id=virti0-0-1 -device virtio-balloon-pci,id=balloon1 -qmp tcp:0:4444,server,nowait -spice port=5931,disable-ticketing -vga qxl -cdrom /usr/share/virtio-win/virtio-win-1.5.3.iso -bios /usr/share/seabios/bios-pm.bin 2.install netkvm driver 3.in cmd eg.ping www.redhat.com -t 4.sleep about 10 mins and wake up the guest. Actual results & Expected results: The network is still available So the issue has been fixed on build 41,thanks. Based on comment #18 move status to VERIFIED Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0441.html |