Messages in this thread | | | Date | Thu, 19 Apr 2012 15:08:00 +0300 | From | Avi Kivity <> | Subject | Re: [PATCH 0/4] Export offsets of VMCS fields as note information for kdump |
| |
On 04/19/2012 03:01 PM, HATAYAMA Daisuke wrote: > >> 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? > > > > It seems natural to check the situation from guest machine's side when > qemu crashs. Suppose a service is running on the guest machine, and > then the qemu crash. Then, we may need to know the details of the > progress of the service if it's important. What has been successfully > done, and what has not yet.
How can a service on the guest be related to a qemu crash? And how would guest registers help?
You can extract the list of running processes from a qemu crash dump without looking at guest registers. And most vcpus are running asynchronously to qemu, so their register contents is irrelevant (if a vcpu is running synchronously with qemu - it just exited to qemu and is waiting for a response - then you'd see the details in qemu's call stack).
-- error compiling committee.c: too many arguments to function
| |