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 by the end of the week I can get make to reproducing the abort and capturing a core. David Ahern On 12/14/2009 09:04 AM, Luiz Capitulino wrote: > On Sat, 12 Dec 2009 11:09:38 -0700 > "David S. Ahern" <daahern@xxxxxxxxx> 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 means it died due to SIGABRT. > > Are you using qemu-kvm or upstream qemu? Which version? Don't you > have any procedure which would make the bug more likely to happen? > > Thanks. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
