This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Since this bugzilla is in a component that is not approved for the current release, it has been closed with resolution deferred. You may reopen this bugzilla for consideration in the next release.
One other detail: not only will system-config-kdump need to enable setup for Xen, it will also need to make sure it's the _right_ setup, which isn't precisely the same as for non-xen kernels. In particular, the "crashkernel=" arg needs to be on the "kernel xen.gz..." line in the grub.conf, not the "module vmlinuz..." line; and the dump kernel will need to be loaded "@32m", not the default "@16m" that non-xen uses.
nb: I had to deal with the same issue in the firstboot module, and its fairly straight-forward. We obviously set the offset to 32 instead of 16 on x86 and x86_64 xen, and then just use grubby with --mbargs instead of --args to add the parameters to the correct line in grub. These changes are in the latest kexec-tools (which carries the firstboot module). Not sure yet how this will all shake out if/when we get around to ia64 xen kdump...
Not an approved component moving to 5.2 for consideration
This is in support of a feature add we've committed to for 5.1 though...
Created attachment 172434 [details] s-c-kdump support for configuring kdump on xen kernels The attached patch implements system-config-kdump xen dump support, bringing it on par with what we have in the kdump firstboot module.
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-0882.html