[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4F93E411.7070809@redhat.com>
Date: Sun, 22 Apr 2012 13:57:21 +0300
From: Avi Kivity <avi@...hat.com>
To: Gleb Natapov <gleb@...hat.com>
CC: HATAYAMA Daisuke <d.hatayama@...fujitsu.com>, dzickus@...hat.com,
luto@....edu, gregkh@...e.de, kvm@...r.kernel.org,
joerg.roedel@....com, mtosatti@...hat.com,
kexec@...ts.infradead.org, linux-kernel@...r.kernel.org,
paul.gortmaker@...driver.com, zhangyanfei@...fujitsu.com,
ebiederm@...ssion.com, ludwig.nussel@...e.de
Subject: Re: [PATCH 0/4] Export offsets of VMCS fields as note information
for kdump
On 04/22/2012 01:33 PM, Gleb Natapov wrote:
> >
> > What I don't understand is why you are interested in the guest machine
> > at all, if it was qemu that crashed.
> >
> It would be interesting to extract enough information from the core to be
> able to restart the guest from the point where qemu crashed, but
> decoding VMCS is not enough for that.
Interesting idea. It should be possible if you attach all kvm state to
the core (and do quite a lot of digging to recover device model state).
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists