public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Mike Snitzer <snitzer@gmail.com>
Cc: Vivek Goyal <vgoyal@redhat.com>, Alexander Graf <agraf@suse.de>,
	kexec@lists.infradead.org, kvm@vger.kernel.org,
	Avi Kivity <avi@qumranet.com>,
	libvir-list@redhat.com
Subject: Re: kexec/kdump of a kvm guest?
Date: Thu, 24 Jul 2008 14:50:06 -0500	[thread overview]
Message-ID: <4888DCEE.8090807@codemonkey.ws> (raw)
In-Reply-To: <170fa0d20807241203h7065b643k7df1187ef7e76f87@mail.gmail.com>

Mike Snitzer wrote:
> On Thu, Jul 24, 2008 at 9:15 AM, Vivek Goyal <vgoyal@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@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.

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@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   


  reply	other threads:[~2008-07-24 19:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26 18:58 kexec/kdump of a kvm guest? Mike Snitzer
2008-07-05 11:20 ` Avi Kivity
2008-07-24  0:13   ` Mike Snitzer
2008-07-24  8:39     ` Alexander Graf
2008-07-24 11:49       ` Mike Snitzer
2008-07-24 13:15         ` Vivek Goyal
2008-07-24 19:03           ` Mike Snitzer
2008-07-24 19:50             ` Anthony Liguori [this message]
2008-07-25  1:12             ` Vivek Goyal
2008-07-27  8:32               ` Avi Kivity
2008-08-25 15:56               ` Mike Snitzer
     [not found]                 ` <170fa0d20808250856w7dd480a9x35f4112f2464a7cd-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-08-25 16:05                   ` Vivek Goyal
     [not found]             ` <170fa0d20807241203h7065b643k7df1187ef7e76f87-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-27  9:12               ` Avi Kivity

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4888DCEE.8090807@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=agraf@suse.de \
    --cc=avi@qumranet.com \
    --cc=kexec@lists.infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=libvir-list@redhat.com \
    --cc=snitzer@gmail.com \
    --cc=vgoyal@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox