From: Avi Kivity <avi@qumranet.com>
To: Mike Snitzer <snitzer@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: kexec/kdump of a kvm guest?
Date: Sat, 05 Jul 2008 14:20:12 +0300 [thread overview]
Message-ID: <486F58EC.6020408@qumranet.com> (raw)
In-Reply-To: <170fa0d20806261158me6f81d0p2ea4fa6b7e694a5a@mail.gmail.com>
Mike Snitzer wrote:
> My host is x86_64 RHEL5U1 running 2.6.25.4 with kvm-70 (kvm-intel).
>
> When I configure kdump in the guest (running 2.6.22.19) and force a
> crash (with 'echo c > /proc/sysrq-trigger) kexec boots the kdump
> kernel but then the kernel hangs (before it gets to /sbin/init et al).
> On the host, the associated qemu is consuming 100% cpu.
>
> I really need to be able to collect vmcores from my kvm guests. So
> far I can't (on raw hardware all works fine).
>
>
I've tested this a while ago and it worked (though I tested regular
kexecs, not crashes); this may be a regression.
Please run kvm_stat to see what's happening at the time of the crash.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-07-05 11:20 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 [this message]
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
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=486F58EC.6020408@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm@vger.kernel.org \
--cc=snitzer@gmail.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