Bug 684709

Summary: windows guest hang after migrate/restore on AMD host
Product: Red Hat Enterprise Linux 5 Reporter: Qixiang Wan <qwan>
Component: xenAssignee: Xen Maintainance List <xen-maint>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 5.7CC: mshao, pbonzini, xen-maint, yuzhang
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-03-14 12:20:47 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:
Attachments:
Description Flags
xend.log
none
hypervisor log (local migrate windows guest) none

Description Qixiang Wan 2011-03-14 09:56:09 UTC 
Description of problem:
After restore a saved windows guest or after (local/remote) migrate the guest, the guest will hang up. This happens both with and without xenpv-win(1.3.4-6.el5) installed.

Version-Release number of selected component (if applicable):]
kernel-xen-2.6.18-247.el5
xen-3.0.3-125.el5

How reproducible:
100%

Steps to Reproduce:
1. start a windows guest (with or without xenpv-win installed
2. save the guest and restore it
3. or migrate (local or remote) the guest for step 2
  
Actual results:
guest will hang after migrate

Expected results:
guest should work well after restore/migrate

Additional info:
It doesn't happen with Intel host.
Comment 1 Qixiang Wan 2011-03-14 10:10:49 UTC 
Created attachment 484130 [details]
xend.log

create a HVM guest, do local migration
$ xm migrate -l guest localhost
Comment 2 Qixiang Wan 2011-03-14 10:11:32 UTC 
Created attachment 484131 [details]
hypervisor log (local migrate windows guest)
Comment 3 Paolo Bonzini 2011-03-14 12:20:47 UTC 
From the xend.log output this seems to be a Windows XP guest, closing as dup of bug 605617.

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