----- Original Message -----
On Fri, Jul 13, 2012 at 09:31:37AM -0400, Dave Anderson wrote:
>
>
> ----- Original Message -----
> > On Thu, Jul 12, 2012 at 03:47:57PM -0400, Dave Anderson wrote:
[...]
> > > Does that work for you?
> >
> > Thanks. It works. I though that there is an issue with conring
> > symbol too.
> > Have you done other tests on RHEL5?
>
> I just did some basic commands, and I didn't see any other problems besides
> the log/conring issue. But I don't really have a good test suite for the Xen
> hypervisor options. And honestly, I've never even seen a "real"
hypervisor
> crash dump, I just have a few forced samples. If you'd like, I can give you a
Our support team is going to use this feature more widely.
It looks that we will have good testbed for Xen crash support.
> pointer to a really early RHEL5.2-era (2.6.18-89.el5) xen-syms/vmcore pair
> that you can use to verify your changes on if you don't have any dumps of
> that era available.
Yes please. It will be very helpful.
Here's one:
http://people.redhat.com/anderson/xen-5.2-dump.tar.gz
It's really old -- it needs the --xen_phys_start 0x3f000000 command line
option because that version didn't pass the phys_start location in the
dumpfile.
Thanks,
Dave