- Subject: Re: [PATCH 0/4] Export offsets of VMCS fields as note information for kdump
- From: Avi Kivity <avi@xxxxxxxxxx>
- Date: Wed, 18 Apr 2012 11:24:59 +0300
- Cc: mtosatti@xxxxxxxxxx, ebiederm@xxxxxxxxxxxx, luto@xxxxxxx, joerg.roedel@xxxxxxx, dzickus@xxxxxxxxxx, paul.gortmaker@xxxxxxxxxxxxx, gregkh@xxxxxxx, ludwig.nussel@xxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, kvm@xxxxxxxxxxxxxxx, kexec@xxxxxxxxxxxxxxxxxxx
- In-reply-to: <4F8E6DA5.8030503@cn.fujitsu.com>
- References: <4F84E0DF.8040206@cn.fujitsu.com> <4F8D1F46.3090901@redhat.com> <4F8D4B4C.8070705@cn.fujitsu.com> <4F8D4D1C.4010400@redhat.com> <4F8E6DA5.8030503@cn.fujitsu.com>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120329 Thunderbird/11.0.1
On 04/18/2012 10:30 AM, zhangyanfei wrote:
> >
> > Okay. Do you expect it to help in debugging the crash? Did you have
> > cases where it would help?
> >
>
> Yes, I do expect it to help in debugging the crash.
> Looking into host machine's crash dump, if we figure out the fact that the crash
> had happend when some host's resource was requested and used by some guset machine.
> Then, we surely want to look into the situation from guest machine's view.
>
>
What type of resource? Can you give an example?
--
error compiling committee.c: too many arguments to function
--
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
[KVM ARM]
[KVM ia64]
[KVM ppc]
[Spice Development]
[Libvirt]
[Libvirt Users]
[Linux USB Devel]
[Video for Linux]
[Linux Audio Users]
[Photo]
[Yosemite News]
[Yosemite Photos]
[Linux Kernel]
[Linux SCSI]
[XFree86]