Update to backport of latest upstream version (bz#218050) will resolve this.
*** Bug 220095 has been marked as a duplicate of this bug. ***
Latest upstream backport required a bit more patching to run on ia64 (posted to rhkernel-list and virtualist), but works now, at least as far as firing up graphics is concerned. Still looking into a hang on shutdown that appears to only trigger when graphics are turned on.
Created attachment 144287 [details] Patch posted to virtualist on 12/19
Created attachment 144308 [details] Crash running against vmcore from hanging xen guest Unfortunately, because ia64 xen guest crash dump process doen't lay down a "switch_stack" register dump on the kernel stack of the panicking process, we don't get a completely useful dump. Without that info, its impossible to get a backtrace of the crashing process (Dave Anderson can explain in further detail). Not seeing much of anything useful in the log output either....
The guest shutdown hang is now being tracked in bug 221626.
*** Bug 225539 has been marked as a duplicate of this bug. ***
Note that the shutdown hang mentioned in comment #3 only manifests itself if a 'poweroff' command is issued from a shell within the guest itself -- the Shutdown button in virt-manager and xm shutdown both work.
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.
We're considering updates to hypervisor and libxc, which should remove the need for the attached patch. Jarod, please confirm using the latest kernel-xen and xen from the appropriate branches.
For the moment, the latest kernel and xen combo does indeed provide a working paravirt framebuffer on ia64 without need for any additional patching. However, with the current x86_64 breakage and it being up in the air which ia64 patch is at fault, I'd like to retest this once that is all sorted out.
So it turned out not to be one of the ia64 patches, and with the latest kernel, things are still working just fine. I'm going to say we're good to go on this one.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2007-0635.html