Hi, Avi, Yanfei I'm YOSHIDA Masanori from Hitachi, a developer of livedump. >> And here is a new case from the LinuxCon Japan: >> >> Developers from Hitach are now developing a new livedump mechanism for the >> same reason as ours. They have come to the situation *many times* that guest >> machines crashed due to host's failures, in particular, under development. > > This has happened to me as well, possible even more times . I don't > use crash dumps for debugging but different people may use different > techniques. As Yanfei's introduction, I'm developing livedump for cases where guests crash due to host's failures. Especially in very important systems, it is strongly requested to identify the root cause of any failure even if it is very rare. For this purpose, crash dumps must be obtained. Therefore, we think livedump technique must be applied to the virtualization system on that kind of area. >>> 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. >>> >> >> Could you please tell me your attitude towards this patch? > > I still dislike it conceptually. But let me do a technical review of > the latest version. Actually, current implementation of livedump is just a core part, which dumps only the image of kernel space. And I'd like to expand it to obtain guest image at the same time too. Also for this situation, VMCSINFO seems necessary to be exported. Thanks, YOSHIDA Masanori Yokohama Research Laboratory, Hitachi, Ltd.
