I'm using a variant of the KVM source from RHEL5 plus a few
cherry-picked patches. Host OS is RHEL 5.3. The servers are using E5540
or E5504 processors. The host OS is running from a small USB key, and
there is no place to write a core file. Other accommodations have to be
made to get it. Hopefully
On Sat, 12 Dec 2009 11:09:38 -0700
"David S. Ahern" wrote:
> Thanks for the responses. I had forgotten that SIGABRT==abort() which
> means I have to get the core file to get to the root cause. To date the
> only information I have is a shell exit status of 134 which from the
> bash man pages mean
Thanks for the responses. I had forgotten that SIGABRT==abort() which
means I have to get the core file to get to the root cause. To date the
only information I have is a shell exit status of 134 which from the
bash man pages means it died due to SIGABRT.
David Ahern
On 12/12/2009 01:52 AM, Stef
David S. Ahern schrieb:
> I realize this is a rather generic question, but what are typical
> reasons Qemu would be killed by a SIGABRT? I am seeing this on a
> somewhat regular (though not repeatable on demand) basis. I do not have
> a core file, though I hope to capture one if I can get it repeat
I realize this is a rather generic question, but what are typical
reasons Qemu would be killed by a SIGABRT? I am seeing this on a
somewhat regular (though not repeatable on demand) basis. I do not have
a core file, though I hope to capture one if I can get it repeat again.
Thanks,
--
David Ahern
