linux-kernel - Re: [PATCH v2 0/5] Export offsets of VMCS fields as note information for kdump

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4FC47579.2040504@cn.fujitsu.com>
Date:	Tue, 29 May 2012 15:06:33 +0800
From:	Yanfei Zhang <zhangyanfei@...fujitsu.com>
To:	Avi Kivity <avi@...hat.com>
CC:	mtosatti@...hat.com, ebiederm@...ssion.com, luto@....edu,
	Joerg Roedel <joerg.roedel@....com>, dzickus@...hat.com,
	paul.gortmaker@...driver.com, ludwig.nussel@...e.de,
	linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
	kexec@...ts.infradead.org, Greg KH <gregkh@...uxfoundation.org>
Subject: Re: [PATCH v2 0/5] Export offsets of VMCS fields as note information
 for kdump

于 2012年05月28日 21:28, Avi Kivity 写道:
> On 05/28/2012 08:25 AM, Yanfei Zhang wrote:
>>
>> Dou you have any comments about this patch set?
> 
> I still have a hard time understanding why it is needed.  If the host
> crashes, there is no reason to look at guest state; the host should
> survive no matter what the guest does.
> 
> 

OK. Let me summarize it.

1. Why is this patch needed? (Our requirement)

We once came to a buggy situation: a host scheduler bug caused guest machine's
vcpu stopped for a long time and then led to heartbeat stop (host is still running).

we want to have an efficient way to make the bug analysis when we come to the similar
situation where guest machine doesn't work well due to something of host machine's, 

Because we should debug both host machine's and guest machine's sides to look for
the reasons, so we want to get both host machine's crash dump and guest machine's
crash dump at the same time when the buggy situation remains. 

2. What will we do?

If this bug was found on customer's environment, we have two ways to avoid
affecting other guest machines running on the same host. First, we could do bug
analysis on another environment to reproduce the buggy situation; Second, we
could migrate other guest machines to other hosts. 

After the buggy situation is reproduced, we panic the host *manually*.
Then we could use userland tools to get guest machine's crash dump from host machine's
with the feature provided by this patch set. Finally we could analyse them separately
to find which side causes the problem.

Thanks
Zhang Yanfei

--
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/