Mike Snitzer wrote:
On Thu, Jul 24, 2008 at 9:15 AM, Vivek Goyal <vgoyal@xxxxxxxxxx> 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@xxxxxxx> 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.
Regards,
Anthony Liguori
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 2.6.25.4 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).
Mike
--
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
--
Libvir-list mailing list
Libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list