Bug 723755
Summary: | win2003 i386 guest BSOD when created with e1000 nic | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Pengzhen Cao <pcao> | ||||||||||||||
Component: | kernel-xen | Assignee: | Paolo Bonzini <pbonzini> | ||||||||||||||
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||||||||
Severity: | high | Docs Contact: | |||||||||||||||
Priority: | urgent | ||||||||||||||||
Version: | 5.8 | CC: | cww, dhoward, drjones, jzheng, leiwang, lersek, pbonzini, xen-maint | ||||||||||||||
Target Milestone: | rc | Keywords: | ZStream | ||||||||||||||
Target Release: | --- | ||||||||||||||||
Hardware: | All | ||||||||||||||||
OS: | Linux | ||||||||||||||||
Whiteboard: | |||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
Doc Text: |
Prior to this update, Xen did not implement certain ALU opcodes. As a result, when a driver used the missing opcodes on memory-mapped I/O areas, it caused the guest to crash. This update adds all the missing opcodes. In particular, this fixes a BSOD crash from the Windows e1000 driver.
|
Story Points: | --- | ||||||||||||||
Clone Of: | Environment: | ||||||||||||||||
Last Closed: | 2012-02-21 03:50:18 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: | |||||||||||||||||
Bug Depends On: | |||||||||||||||||
Bug Blocks: | 514490, 728518 | ||||||||||||||||
Attachments: |
|
Description
Pengzhen Cao
2011-07-21 03:11:03 UTC
Created attachment 514110 [details]
win2003 32bit BSOD with e1000nic
Created attachment 514111 [details]
xm-dmesg
Created attachment 514112 [details]
xm log
Created attachment 514113 [details]
qemu-dm
I think Igor already fixed this, but I'll let him confirm and close as a dup of his emulator fixes bug. Please retest with http://scratch.englab.brq.redhat.com/imammedo/xen-imul-shaf.gz (In reply to comment #6) > Please retest with > http://scratch.englab.brq.redhat.com/imammedo/xen-imul-shaf.gz I have tried with this, still no luck, BSOD as normal xen.gz. Possibly related to bug 653271. 0xC000001D is an "Illegal instruction", perhaps an assertion failure. xor r32, m32 is not handled by xen. Easily fixed, will see next week if there's something else. Created attachment 515910 [details]
prototype patch
Patch fixes the bug. Created attachment 516113 [details]
patch
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. Patch(es) available in kernel-2.6.18-282.el5 You can download this test kernel (or newer) from http://people.redhat.com/jwilson/el5 Detailed testing feedback is always welcomed. Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Prior to this update, Xen did not implement certain ALU opcodes. As a result, when a driver used the missing opcodes on memory-mapped I/O areas, it caused the guest to crash. This update adds all the missing opcodes. In particular, this fixes a BSOD crash from the Windows e1000 driver. Reproduced with -274 kernel. Booting Windows 2003 i386 guest with e1000 nic goes directly into crash, $ xm dmesg ... (XEN) 33, This opcode isn't handled yet! (XEN) handle_mmio: failed to decode instruction (XEN) mmio opcode: gpa 0xf4003828, len 2: 33 01 With -300 kernel, the guest does not crash, either at booting or reinstalling the e1000 driver. 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/RHSA-2012-0150.html |