On 04/19/2012 02:27 PM, HATAYAMA Daisuke wrote: > >> The reason why we want to retrieve guest machine's memory image as > >> crash dump is that then we can debug guest machine's status using > >> symbolic debugger such as gdb and crash utility. > >> > >> This is very useful. Please consider the situation where engineers are > >> forced to look into guest machine's memory image through qemu-kvm's > >> process core dump using gdb without any symbolic information. It's > >> very inefficient. > > > > I still don't follow. If qemu crashed, the values in guest registers > > are irrelevant. In what way can the help debug the qemu crash? > > > > It would be not helpful for the qemu crash case you are concerned > about. We want to use the guest state data to look into guest > machine's image in the crasshed qemu. Why? -- 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
