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 807967 - [virtio-win][netkvm]network can not get the ip after s3 or long disable\enable
Summary: [virtio-win][netkvm]network can not get the ip after s3 or long disable\enable
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virtio-win
Version: 6.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Yvugenfi@redhat.com
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 761491
TreeView+ depends on / blocked
 
Reported: 2012-03-29 09:09 UTC by Mike Cao
Modified: 2013-05-30 15:13 UTC (History)
16 users (show)

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.
Clone Of:
Environment:
Last Closed: 2013-02-21 10:38:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0441 0 normal SHIPPED_LIVE virtio-win bug fix and enhancement update 2013-02-20 20:48:13 UTC

Description Mike Cao 2012-03-29 09:09:27 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
virtio-win-prewhql-24

How reproducible:
80%

Steps to Reproduce:
1.start guest w/ virtio-net-pci
/usr/libexec/qemu-kvm -M rhel6.3.0  -enable-kvm -m 4G -smp 4 -name win2k8R2 -uuid e37055a7-8205-470c-a546-109ca2307c9c -monitor stdio -drive file=/test/win2k8r2,if=none,id=drive-virtio-disk0,format=raw,cache=none,werror=stop,rerror=stop,aio=native -device ide-drive,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,id=hostnet0,vhost=on -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:22:3a:0a,bus=pci.0,addr=0x4 -spice port=5900,disable-ticketing -k en-us -vga qxl
2.in the guest  ping www.redhat.com -t 
3.sleep in the guest 
4.after 10 mins ,wake it up 
  
Actual results:
Guest network down ,and failed to get the ip again after resume

Expected results:
network still work


Additional info:
workaround :disable then re-enable network adapter can fix this issue
Comment 2 Yvugenfi@redhat.com 2012-03-29 10:24:57 UTC 
Hello Mike,

Do you know if this is a regression?

Thanks,
Yan.
Comment 3 Yvugenfi@redhat.com 2012-03-29 10:25:19 UTC 
Hello Mike,

Do you know if this is a regression?

Thanks,
Yan.
Comment 4 Mike Cao 2012-03-29 10:44:43 UTC 
(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
Comment 5 Yvugenfi@redhat.com 2012-04-03 08:59:41 UTC 
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.
Comment 6 Min Deng 2012-04-05 06:07:37 UTC 
(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
Comment 7 Qunfang Zhang 2012-04-10 09:32:59 UTC 
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
Comment 8 Ronen Hod 2012-04-17 08:45:26 UTC 
Moving to RHEL6.4 along with the other S3 issue.
Comment 9 Yvugenfi@redhat.com 2012-05-29 13:57:15 UTC 
Same bug can bee reproduces if driver is disabled on the guest and re-enabled after 10 minutes.
Comment 11 RHEL Program Management 2012-07-10 07:02:21 UTC 
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.
Comment 12 RHEL Program Management 2012-07-11 02:03:02 UTC 
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.
Comment 13 Yvugenfi@redhat.com 2012-09-04 15:04:51 UTC 
http://git.engineering.redhat.com/?p=users/yvugenfi/internal-kvm-guest-drivers-windows/.git;a=commit;h=75d6526dd2aa56f6efc081262dcf36b02ed2ece6
Comment 15 Yvugenfi@redhat.com 2012-09-30 12:13:18 UTC 
Should be in build 37.
Comment 16 Mike Cao 2012-10-12 08:05:24 UTC 
dengmin 
pls help to verify this bug on newest virtio-win-prewhql build 

Thanks,
Mike
Comment 18 Min Deng 2012-10-15 03:39:57 UTC 
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.
Comment 19 Mike Cao 2012-10-15 04:59:49 UTC 
Based on comment #18 move status to VERIFIED
Comment 20 errata-xmlrpc 2013-02-21 10:38:23 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.