Hi, all When I use crash to deal with the vmcore generated by 'vrish dump', I meet the following error: crash: seek error: kernel virtual address: ffffffff8180f1e0 type: "cpu_possible_mask". When I specify '-d 8' to get more information, I found the following message: NOTE: KVM/QEMU CPU_SAVE_VERSION 12 is greater than supported version 9 So I guess crash does not support it now. Does anyone have plan to fix it? Thanks Wen Congyang

----- Original Message ----- > > > ----- Original Message ----- >> Hi, all >> >> When I use crash to deal with the vmcore generated by 'vrish dump', >> I >> meet the following error: >> >> crash: seek error: kernel virtual address: ffffffff8180f1e0 type: "cpu_possible_mask". >> >> When I specify '-d 8' to get more information, I found the following message: >> >> NOTE: KVM/QEMU CPU_SAVE_VERSION 12 is greater than supported version 9 >> >> So I guess crash does not support it now. Does anyone have plan to fix it? >> >> Thanks >> Wen Congyang > > Hi Wen, > > Also, because of your familiarity with this area, I certainly invite you > to take a look at this... ;-) > > Thanks, > Dave Hi Wen, On a related note, what is the status with your "virsh dump-guest-memory" replacement of "virsh dump"? The last I saw, it seemed like the qemu guys finally seemed willing to accept it?

Dave

----- Original Message ----- > At 06/22/2012 09:06 PM, Dave Anderson Wrote: > > > > > > ----- Original Message ----- > >> > >> > >> ----- Original Message ----- > >>> Hi, all > >>> > >>> When I use crash to deal with the vmcore generated by 'vrish dump', > >>> I meet the following error: > >>> > >>> crash: seek error: kernel virtual address: ffffffff8180f1e0 type: "cpu_possible_mask". > >>> > >>> When I specify '-d 8' to get more information, I found the following message: > >>> > >>> NOTE: KVM/QEMU CPU_SAVE_VERSION 12 is greater than supported version 9 > >>> > >>> So I guess crash does not support it now. Does anyone have plan to fix it? > >>> > >>> Thanks > >>> Wen Congyang > >> > >> Hi Wen, > >> > >> Also, because of your familiarity with this area, I certainly invite you > >> to take a look at this... ;-) > >> > >> Thanks, > >> Dave > > > > Hi Wen, > > > > On a related note, what is the status with your "virsh dump-guest-memory" > > replacement of "virsh dump"? The last I saw, it seemed like the qemu guys > > finally seemed willing to accept it? > > dump-guest-memory is not a virsh's sub command. It is a qemu monitor command. > The patches for qemu and libvirt have been merged into newest qemu/libvirt. OK, but now I'm confused... I was presuming that you could run the new "dump-guest-memory" command from the KVM host, specifying a particular guest, and it will create an ELF vmcore that the crash utility can read. But I don't know what the term "qemu monitor command" means? Is it a command that can be executed from a shell command line? And will "virsh dump" still exist? And if so, why? Dave

At 06/22/2012 02:03 AM, Dave Anderson Wrote: > > > ----- Original Message ----- >> Hi, all >> >> When I use crash to deal with the vmcore generated by 'vrish dump', I >> meet the following error: >> >> crash: seek error: kernel virtual address: ffffffff8180f1e0 type: "cpu_possible_mask". >> >> When I specify '-d 8' to get more information, I found the following message: >> >> NOTE: KVM/QEMU CPU_SAVE_VERSION 12 is greater than supported version 9 >> >> So I guess crash does not support it now. Does anyone have plan to fix it? >> >> Thanks >> Wen Congyang > > Hi Wen, > > Also, because of your familiarity with this area, I certainly invite you > to take a look at this... ;-) I am busy recently. If I have time and the problem is not fixed, I will try to fix it.