kexec/kdump of a kvm guest?
anthony at codemonkey.ws
Thu Jul 24 15:50:06 EDT 2008
Mike Snitzer wrote:
> On Thu, Jul 24, 2008 at 9:15 AM, Vivek Goyal <vgoyal at redhat.com> wrote:
>> On Thu, Jul 24, 2008 at 07:49:59AM -0400, Mike Snitzer wrote:
>>> On Thu, Jul 24, 2008 at 4:39 AM, Alexander Graf <agraf at suse.de> wrote:
> I can do further research but welcome others' insight: do others have
> advice on how best to collect a crashed kvm guest's core?
I don't know what you do in libvirt, but you can start a gdbstub in
QEMU, connect with gdb, and then have gdb dump out a core.
>> It will be interesting to look at your results with 2.6.25.x kernels with
>> kvm module inserted. Currently I can't think what can possibly be wrong.
> If the host's 22.214.171.124 kernel has both the kvm and kvm-intel modules
> loaded kexec/kdump does _not_ work (simply hangs the system). If I
> only have the kvm module loaded kexec/kdump works as expected
> (likewise if no kvm modules are loaded at all). So it would appear
> that kvm-intel and kexec are definitely mutually exclusive at the
> moment (at least on both 2.6.22.x and 2.6.25.x).
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
More information about the kexec