Re: [Qemu-devel] [PATCH v4 2/8] acpi: add vmcoreinfo device

- Original Message - > Hi Dave > > On Wed, Jul 26, 2017 at 10:21 AM, Michael S. Tsirkin wrote: > > On Sat, Jul 15, 2017 at 01:47:50AM +0200, Marc-André Lureau wrote: > >> > > >> > There's more info scattered in other places. > >> > > >> > Why do you get to document it?

Re: [Qemu-devel] [PATCH v2 5/7] kdump: add vmcoreinfo ELF note

s look OK to me. > > > > Reviewed-by: Laszlo Ersek <ler...@redhat.com> > > Without it, crash doesn't read the vmcoreinfo PT_NOTE. And for some > reason, the phys_base in the header wasn't enough (to be doubled > checked). > > Any comment Dave about cras

Re: [Qemu-devel] [PATCH 00/21] WIP: dump: add kaslr support (for after 2.9)

- Original Message - > Hi, > > Latest linux kernel enabled kaslr to randomize phys/virt memory > addresses. There has been some effort to support kexec/kdump so that > crash utility can still works in case crashed kernel has kaslr > enabled. > > This series aims to provide enough

Re: [Qemu-devel] virsh dump (qemu guest memory dump?): KASLR enabled linux guest support

- Original Message - > > > On 09/11/2016 16:28, Dave Anderson wrote: > > I'm not sure whether this "guest userspace agent" is still in play here, > > but if there were such a thing, it could theoretically do the same > > thing that crash current

Re: [Qemu-devel] virsh dump (qemu guest memory dump?): KASLR enabled linux guest support

works in case crashed kernel has kaslr enabled. > > > > But according to Dave Anderson virsh dump does not work, quoted messages > > from Dave below: > > > > """ > > with virsh dump, there's no way of even knowing that KASLR > > ha

Re: [Qemu-devel] virsh dump (qemu guest memory dump?): KASLR enabled linux guest support

> > >> > > >> Latest linux kernel enabled kaslr to randomiz phys/virt memory > > >> addresses, we had some effort to support kexec/kdump so that crash > > >> utility can still works in case crashed kernel has kaslr enabled. > > >

Re: [Qemu-devel] virsh dump (qemu guest memory dump?): KASLR enabled linux guest support

- Original Message - > Hi, > > Latest linux kernel enabled kaslr to randomiz phys/virt memory > addresses, we had some effort to support kexec/kdump so that crash > utility can still works in case crashed kernel has kaslr enabled. > > But according to Dave And

Re: [Qemu-devel] uniquely identifying KDUMP files that originate from QEMU

- Original Message - adding back a few CC's because this discussion is useful On 11/12/14 19:43, Petr Tesarik wrote: V Wed, 12 Nov 2014 15:50:32 +0100 Laszlo Ersek ler...@redhat.com napsáno: On 11/12/14 09:04, Petr Tesarik wrote: On Wed, 12 Nov 2014 12:08:38 +0900 (JST)

Re: [Qemu-devel] [Crash-utility] uniquely identifying KDUMP files that originate from QEMU

- Original Message - Can you fetch that in crash? If you can, then there's nothing to do on the qemu side (and I'll have to apologize for spamming a bunch of lists :/). Well, let's be clear -- I was the one who put you up to it... But no apology is required -- and in fact, if

Re: [Qemu-devel] [PATCH v5] target-ppc: ppc64 target's virtio can be either endian

system dumps and not sure if a system dump analyzing tool should adapt to endianness when analyzing system dumps. Copying Dave Anderson (of crash utility) for his views here. Actually the crash utility doesn't compare the dumpfile to the vmlinux file, but rather it will not initialize

Re: [Qemu-devel] [PATCH v5] target-ppc: ppc64 target's virtio can be either endian

- Original Message - On Tue, 22 Apr 2014 09:19:48 -0400 (EDT) Dave Anderson ander...@redhat.com wrote: - Original Message - On Mon, Apr 21, 2014 at 4:48 PM, Greg Kurz gk...@linux.vnet.ibm.com wrote: On Mon, 21 Apr 2014 09:56:48 +0200 Alexander Graf ag

Re: [Qemu-devel] dump-guest-memory enhancement.

- Original Message - I haven't been there at the original creation of this functionality, but I tend to agree with you. For analyzing the vmcore with gdb or crash, the alignment doesn't seem to be important, so it was probably ignored. With respect to the crash utility, the p_align

Re: [Qemu-devel] [Question] dump memory when host pci device is used by guest

- Original Message - On 10/25/2011 10:23 AM, Avi Kivity wrote: On 10/25/2011 10:06 AM, Wen Congyang wrote: Hi, Avi Kivity, Dave Anderson I have two questions about it: 1. How to know the guest's physical base address in qemu? In fact, it's impossible. Perhaps crash

Re: [Qemu-devel] [Question] dump memory when host pci device is used by guest

- Original Message - The question is that: 'virsh dump' can not be used when host pci device is used by guest. We are discussing how to fix the problem. We have determined that introduce a new monitor command dump. Jan suggested that the core file's format is gdb standard core

Re: [Qemu-devel] [Question] dump memory when host pci device is used by guest

- Original Message - On 10/24/2011 04:25 PM, Dave Anderson wrote: The question is that: 'virsh dump' can not be used when host pci device is used by guest. We are discussing how to fix the problem. We have determined that introduce a new monitor command dump. Jan suggested

Re: [Qemu-devel] [Question] dump memory when host pci device is used by guest

- Original Message - No, an ELF image of the guest's physical memory. Well then that should be pretty straight forward to support. Depending upon how similar it would be to the standard kdump ELF format, the only other issue is how to determine the physical base address at