Description of problem: windows i386 hvm guest will BSOD(win2003 32bit) or hang(winXP/win2003 32bit) after several local or live migration Version-Release number of selected component (if applicable): kernel-xen-2.6.18-274.el5, xen-3.0.3-132.el5 How reproducible: 30% Steps to Reproduce: 1. Install kernel-xen/xen into 1~2 hosts with AMD CPU 2. create windows i386 32bit guest(e.g win2003 32bit, winxp 32bit) 3. do local or live migration for several times Actual results: Windows guest will BSOD(win2k3) or hang(win2k3, winxp) after about 3 times migration Expected results: Guest running fine Additional info: 1. This issue only happens with AMD CPU, the host we we tried are having Opteron 1220 or Athlon 5200 CPU. It is working fine with Intel hosts. 2. Tried with kernel 272 and 273, guest will hang, but there is no BSOD(both winxp and win2003). only with 274 kernel, it will BSOD with win2k3 32bit guest. 3. Tried with older kernel 268 and 238, there is much less chance of guest hang (10% or so), and there is also no BSOD.
Created attachment 514193 [details] win2003 32bit BSOD after migration screenshot
Created attachment 514194 [details] xm-dmesg
Created attachment 514195 [details] xend.log
Created attachment 514196 [details] qemu-dm.log
This is possibly a dup of bug 605617. We should test the patch posted for that bug on these systems.
(In reply to comment #5) > This is possibly a dup of bug 605617. We should test the patch posted for that > bug on these systems. Maybe, but not exactly same error. It seems higher chance of failure after 272 kernel fix, and there is more chance of BSOD on 274 kernel than 272/273 and any other earlier one. This is why I file this bug. I can test if you build a kernel with that fix.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Stop 0xB8 was also observed by Andrew (bug 605617 comment 17), so closing as duplicate.
*** This bug has been marked as a duplicate of bug 605617 ***