This bug has been copied from bug #707966 and has been proposed
to be backported to 5.7 z-stream (EUS).
Patch(es) for this issue have been committed in kernel 2.6.18-274.6.1.el5.
Verify this problem with guest kernel 2.6.18-274.6.1.el5.
Host kernel: 2.6.18-274.el5xen
Host CPU model: Intel Xeon E5405
1. Reproduce this problem with x86_64 guest:
guest kernel: 2.6.18-274.5.1.el5
guest conf: apic=0
2. Verify this problem with x86_64 guest:
guest kernel: 2.6.18-274.6.1.el5
guest conf: works both with apic=0 and apic=1
Repeat above steps after updating host kernel to 2.6.18-274.6.1.el5xen.
Also test 32b guest with normal and pae kernel, this problem does not exists(even with kernel 2.6.18-274.5.1.el5).
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.
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.
A previously applied patch to help clean-up a failed nmi_watchdog check by disabling various registers caused single-vcpu Xen HVM guests to become unresponsive during boot when the host CPU was an Intel Xeon Processor E5405 or an Intel Xeon Processor E5420, and the VM configuration did not have the apic = 1 parameter set. With this update, NMI_NONE is the default watchdog on AMD64 HVM guests, thus, fixing this issue.