Bug 765707

Summary: RHEL5.8 HVM guest with e1000 nic hang after save/restore
Product: Red Hat Enterprise Linux 5 Reporter: Yuyu Zhou <yuzhou>
Component: xenAssignee: Xen Maintainance List <xen-maint>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.7CC: jzheng, leiwang, mrezanin, qguan, qwan, shwang, xen-maint, yuzhou
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: 2011-12-09 07:59:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
xend log
none
xm dmesg log none

Description Yuyu Zhou 2011-12-09 07:37:48 UTC 
Description of problem:
Save/restore a RHEL5.8 HVM guest with e1000 nic, the guest hang and lose response after being restored

Version-Release number of selected component (if applicable):
host: xen-3.0.3-135.el5, kernel-xen-2.6.18-300.el5
guest: RHEL5.8-Server-20111205.0 (kernel-2.6.18-300.el5)

How reproducible:
100%

Steps to Reproduce:
1. Create a RHEL5.8 hvm guest (both i386 and x86_64, both up and smp) with e1000 nic. parameter as following:
vif = [ "type=ioemu,mac=06:16:36:63:33:a1,bridge=xenbr0,script=vif-bridge,model=e1000"]
2. Save the guest.
3. Restore the guest from the saved file
 
Actual results:
The guest hangs after restore.

Expected results:
The guest should work well after restore.

Additional info:
1. Same issue with RHEL5.7 GA guest in RHEL5.7 GA host.
2. No problem when the guest using rtl8139 nic or netfront nic.
3. Reproduced on both intel-i7 and amd-5400b machine.
Comment 1 Yuyu Zhou 2011-12-09 07:38:31 UTC 
Created attachment 544368 [details]
xend log
Comment 2 Yuyu Zhou 2011-12-09 07:38:55 UTC 
Created attachment 544369 [details]
xm dmesg log
Comment 3 Miroslav Rezanina 2011-12-09 07:59:46 UTC 
As described in 653271, this is known issue. However, possible fix for this is too risky for current xen lifetime. Until this issue is reported by customer we won't fix it.

This issue should be added to test plan as known issue to not test in future.