From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: kexec/kdump of a kvm guest? Date: Sat, 05 Jul 2008 14:20:12 +0300 Message-ID: <486F58EC.6020408@qumranet.com> References: <170fa0d20806261158me6f81d0p2ea4fa6b7e694a5a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Mike Snitzer Return-path: Received: from il.qumranet.com ([212.179.150.194]:51115 "EHLO il.qumranet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751523AbYGELUO (ORCPT ); Sat, 5 Jul 2008 07:20:14 -0400 In-Reply-To: <170fa0d20806261158me6f81d0p2ea4fa6b7e694a5a@mail.gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: 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.