Bug 811143
Summary: | [RHEL6.3 guest] Network can not get the ip after s3 with NetworkManager service start | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Qunfang Zhang <qzhang> |
Component: | qemu-kvm | Assignee: | Amos Kong <akong> |
Status: | CLOSED WORKSFORME | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.3 | CC: | acathrow, ailan, akong, amit.shah, areis, bcao, bsarathy, dyasny, flang, juzhang, michen, mkenneth, rhod, shuang, virt-maint, yvugenfi |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-12-21 09:42:40 UTC | Type: | Bug |
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
Qunfang Zhang
2012-04-10 09:30:38 UTC
Update for more clear: (1) When 'service NetworkManager stop', the guest still has networking because the 'network' service is up. So in this condition, guest network is always available. Suspend guest to memory and wakeup it after 5 minutes, guest network is accessible as well. (2) When 'NetworkManager' service starts, will hit this bug. I know this sounds a bit odd, but please confirm that this bug doesn't happen on a non virt (real hardware) rhel6.3 machine (you can probably test this by suspending the host itself). I have this exact problem on one of my old fedora boxes (a netbook), so this might be a problem unrelated to qemu. (In reply to comment #3) > I know this sounds a bit odd, but please confirm that this bug doesn't happen > on a non virt (real hardware) rhel6.3 machine (you can probably test this by > suspending the host itself). > > I have this exact problem on one of my old fedora boxes (a netbook), so this > might be a problem unrelated to qemu. Hi, Ademar Just test on host which is installed with the following packages, and this issue does not happen on a host. install tree: RHEL6.3-20120329.0/ kernel version: 2.6.32-262.el6.x86_64 Steps: 1. Install the host with the above tree. 2. Check the network. It is available and can ping other host. And the 'NetworkManager' service is starting. 3. #pm-suspend 4. Wait for 8 minutes. 5. Wakeup host by press the power button. The power button is blinking during suspending to mem. And press it to wakeup system. Result: Host resumes from S3 and comes back to the screen before it suspended. Wait for few seconds the network will come back. 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. Talked with mst, reassign this to me. I think this is specific to the network adapters -- I believe this doesn't happen with virtio devices, is that correct? If so, please adjust summary to note it only happens with e1000. Hi, Amit I can not reproduce it now on the latest rhel6.4 host even with the same command line in comment 0. Tried all virtio/e1000/rtl8139 nics. Guest can get ip address again after resume with NetworkManager started. Host: Install tree: RHEL6.4-20121212.1/ kernel-2.6.32-348.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.346.el6.x86_64 OK - so looks like this one got fixed, then! Amos, might be worthwhile to check recent commits to e1000 device emulation to see what could've caused this. Thanks for testing again, closing. |