On 2011-10-25 03:37, Wen Congyang wrote:
At 10/24/2011 11:58 PM, Dave Anderson Write:
- 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
At 10/24/2011 11:30 PM, Avi Kivity Write:
On 10/24/2011 05:25 PM, Dave Anderson wrote:
- 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.
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 can scan through the core looking for a signature. Need
to be careful since multiple
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 can scan through the core looking for a
On 10/25/2011 10:35 AM, Paolo Bonzini wrote:
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
On 10/25/2011 10:52 AM, Avi Kivity wrote:
Crash uses a heuristic based on the IDT base to identify the base from
migrate-to-file output. It also needs CR3 in order to read from
virtual address.
Does elf not store cr3? Perhaps a note with the contents of the
privileged cpu registers is
On 2011-10-25 10:56, Paolo Bonzini wrote:
On 10/25/2011 10:52 AM, Avi Kivity wrote:
Crash uses a heuristic based on the IDT base to identify the base from
migrate-to-file output. It also needs CR3 in order to read from
virtual address.
Does elf not store cr3? Perhaps a note with the
- 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
On 10/25/2011 03:18 PM, Dave Anderson wrote:
Crash uses a heuristic based on the IDT base to identify the base from
migrate-to-file output. It also needs CR3 in order to read from virtual
address.
Just to clarify -- the need for the IDT base and cr3 is *only* true for
KVM dumps using
- 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
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 that the core
file's
format is
- 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
On 10/24/2011 05:25 PM, Dave Anderson wrote:
- 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
- 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
At 10/24/2011 11:58 PM, Dave Anderson Write:
- 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
At 10/21/2011 09:02 PM, Dave Anderson Write:
- Original Message -
At 10/21/2011 03:11 PM, Jan Kiszka Write:
On 2011-10-20 12:03, Wen Congyang wrote:
At 10/20/2011 05:41 PM, Jan Kiszka Write:
On 2011-10-20 03:22, Wen Congyang wrote:
I didn't read full story but 'crash' is used for
On 2011-10-20 12:03, Wen Congyang wrote:
At 10/20/2011 05:41 PM, Jan Kiszka Write:
On 2011-10-20 03:22, Wen Congyang wrote:
I didn't read full story but 'crash' is used for investigating kernel
core generated
by kdump for several years. Considering support service guys, virsh dump
should
At 10/21/2011 03:11 PM, Jan Kiszka Write:
On 2011-10-20 12:03, Wen Congyang wrote:
At 10/20/2011 05:41 PM, Jan Kiszka Write:
On 2011-10-20 03:22, Wen Congyang wrote:
I didn't read full story but 'crash' is used for investigating kernel
core generated
by kdump for several years. Considering
On 2011-10-21 15:02, Dave Anderson wrote:
- Original Message -
At 10/21/2011 03:11 PM, Jan Kiszka Write:
On 2011-10-20 12:03, Wen Congyang wrote:
At 10/20/2011 05:41 PM, Jan Kiszka Write:
On 2011-10-20 03:22, Wen Congyang wrote:
I didn't read full story but 'crash' is used for
On Fri, Oct 21, 2011 at 09:02:37AM -0400, Dave Anderson wrote:
It would be kind of cool if there was a /dev/mem-like interface
to a KVM guest's physical memory, so that you could sit on a KVM host
and enter crash vmlinux-of-guest /dev/mem-of-guest in order to
run live analysis of a guest.
OT
On 2011-10-20 03:22, Wen Congyang wrote:
I didn't read full story but 'crash' is used for investigating kernel core
generated
by kdump for several years. Considering support service guys, virsh dump
should support
a format for crash because they can't work well at investigating vmcore by
At 10/20/2011 05:41 PM, Jan Kiszka Write:
On 2011-10-20 03:22, Wen Congyang wrote:
I didn't read full story but 'crash' is used for investigating kernel core
generated
by kdump for several years. Considering support service guys, virsh dump
should support
a format for crash because they
On 2011-10-19 04:04, KAMEZAWA Hiroyuki wrote:
On Tue, 18 Oct 2011 10:31:10 +0200
Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-10-18 10:31, Wen Congyang wrote:
At 10/18/2011 04:26 PM, Jan Kiszka Write:
On 2011-10-18 10:25, Wen Congyang wrote:
At 10/18/2011 04:19 PM, Jan Kiszka Write:
At 10/19/2011 07:40 PM, Jan Kiszka Write:
On 2011-10-19 04:04, KAMEZAWA Hiroyuki wrote:
On Tue, 18 Oct 2011 10:31:10 +0200
Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-10-18 10:31, Wen Congyang wrote:
At 10/18/2011 04:26 PM, Jan Kiszka Write:
On 2011-10-18 10:25, Wen Congyang wrote:
At
Hi, Jan Kiszka
At 10/10/2011 05:34 PM, Jan Kiszka Write:
On 2011-10-10 11:02, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 08:52:08AM +0200, Jan Kiszka wrote:
Run gdb with set debug remote 1 and watch the communication, it is not
that complex. But a dump command is probably simpler
On 2011-10-18 09:15, Wen Congyang wrote:
Hi, Jan Kiszka
At 10/10/2011 05:34 PM, Jan Kiszka Write:
On 2011-10-10 11:02, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 08:52:08AM +0200, Jan Kiszka wrote:
Run gdb with set debug remote 1 and watch the communication, it is not
that
At 10/18/2011 03:52 PM, Jan Kiszka Write:
On 2011-10-18 09:15, Wen Congyang wrote:
Hi, Jan Kiszka
At 10/10/2011 05:34 PM, Jan Kiszka Write:
On 2011-10-10 11:02, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 08:52:08AM +0200, Jan Kiszka wrote:
Run gdb with set debug remote 1 and watch
On Tue, Oct 18, 2011 at 03:15:29PM +0800, Wen Congyang wrote:
Hi, Jan Kiszka
At 10/10/2011 05:34 PM, Jan Kiszka Write:
On 2011-10-10 11:02, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 08:52:08AM +0200, Jan Kiszka wrote:
Run gdb with set debug remote 1 and watch the
On 2011-10-18 09:58, Daniel P. Berrange wrote:
On Tue, Oct 18, 2011 at 03:15:29PM +0800, Wen Congyang wrote:
Hi, Jan Kiszka
At 10/10/2011 05:34 PM, Jan Kiszka Write:
On 2011-10-10 11:02, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 08:52:08AM +0200, Jan Kiszka wrote:
Run gdb with set
On 2011-10-18 09:58, Wen Congyang wrote:
At 10/18/2011 03:52 PM, Jan Kiszka Write:
On 2011-10-18 09:15, Wen Congyang wrote:
Hi, Jan Kiszka
At 10/10/2011 05:34 PM, Jan Kiszka Write:
On 2011-10-10 11:02, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 08:52:08AM +0200, Jan Kiszka wrote:
At 10/18/2011 04:19 PM, Jan Kiszka Write:
On 2011-10-18 09:58, Wen Congyang wrote:
At 10/18/2011 03:52 PM, Jan Kiszka Write:
On 2011-10-18 09:15, Wen Congyang wrote:
Hi, Jan Kiszka
At 10/10/2011 05:34 PM, Jan Kiszka Write:
On 2011-10-10 11:02, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011
On 2011-10-18 10:17, Jan Kiszka wrote:
On 2011-10-18 09:58, Daniel P. Berrange wrote:
On Tue, Oct 18, 2011 at 03:15:29PM +0800, Wen Congyang wrote:
Hi, Jan Kiszka
At 10/10/2011 05:34 PM, Jan Kiszka Write:
On 2011-10-10 11:02, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 08:52:08AM
On Tue, Oct 18, 2011 at 10:17:27AM +0200, Jan Kiszka wrote:
On 2011-10-18 09:58, Daniel P. Berrange wrote:
On Tue, Oct 18, 2011 at 03:15:29PM +0800, Wen Congyang wrote:
Hi, Jan Kiszka
At 10/10/2011 05:34 PM, Jan Kiszka Write:
On 2011-10-10 11:02, Daniel P. Berrange wrote:
On Mon, Oct
On 2011-10-18 10:25, Wen Congyang wrote:
At 10/18/2011 04:19 PM, Jan Kiszka Write:
On 2011-10-18 09:58, Wen Congyang wrote:
At 10/18/2011 03:52 PM, Jan Kiszka Write:
On 2011-10-18 09:15, Wen Congyang wrote:
Hi, Jan Kiszka
At 10/10/2011 05:34 PM, Jan Kiszka Write:
On 2011-10-10 11:02,
At 10/18/2011 04:26 PM, Jan Kiszka Write:
On 2011-10-18 10:25, Wen Congyang wrote:
At 10/18/2011 04:19 PM, Jan Kiszka Write:
On 2011-10-18 09:58, Wen Congyang wrote:
At 10/18/2011 03:52 PM, Jan Kiszka Write:
On 2011-10-18 09:15, Wen Congyang wrote:
Hi, Jan Kiszka
At 10/10/2011 05:34 PM,
On 2011-10-18 10:25, Daniel P. Berrange wrote:
On Tue, Oct 18, 2011 at 10:17:27AM +0200, Jan Kiszka wrote:
On 2011-10-18 09:58, Daniel P. Berrange wrote:
On Tue, Oct 18, 2011 at 03:15:29PM +0800, Wen Congyang wrote:
Hi, Jan Kiszka
At 10/10/2011 05:34 PM, Jan Kiszka Write:
On 2011-10-10
On 2011-10-18 10:31, Wen Congyang wrote:
At 10/18/2011 04:26 PM, Jan Kiszka Write:
On 2011-10-18 10:25, Wen Congyang wrote:
At 10/18/2011 04:19 PM, Jan Kiszka Write:
On 2011-10-18 09:58, Wen Congyang wrote:
At 10/18/2011 03:52 PM, Jan Kiszka Write:
On 2011-10-18 09:15, Wen Congyang wrote:
On Tue, Oct 18, 2011 at 10:31:10AM +0200, Jan Kiszka wrote:
On 2011-10-18 10:31, Wen Congyang wrote:
At 10/18/2011 04:26 PM, Jan Kiszka Write:
On 2011-10-18 10:25, Wen Congyang wrote:
At 10/18/2011 04:19 PM, Jan Kiszka Write:
On 2011-10-18 09:58, Wen Congyang wrote:
At 10/18/2011 03:52
On 2011-10-18 10:34, Richard W.M. Jones wrote:
On Tue, Oct 18, 2011 at 10:31:10AM +0200, Jan Kiszka wrote:
On 2011-10-18 10:31, Wen Congyang wrote:
At 10/18/2011 04:26 PM, Jan Kiszka Write:
On 2011-10-18 10:25, Wen Congyang wrote:
At 10/18/2011 04:19 PM, Jan Kiszka Write:
On 2011-10-18
On 2011-10-18 10:36, Jan Kiszka wrote:
Crash can decode kernel structures, providing for example process
listings and debugging into userspace processes. Crash actually
reuses gdb's code too, so it's kind of a superset.
Yeah, I see. Could also be solved via gdb scripts, but crash is already
At 10/18/2011 04:36 PM, Jan Kiszka Write:
On 2011-10-18 10:34, Richard W.M. Jones wrote:
Yeah, I see. Could also be solved via gdb scripts, but crash is already
there.
But let's see if the formats actually differ. In the end, crash is just
parsing the same information that also gdb sees.
On 2011-10-18 11:43, Wen Congyang wrote:
At 10/18/2011 04:36 PM, Jan Kiszka Write:
On 2011-10-18 10:34, Richard W.M. Jones wrote:
Yeah, I see. Could also be solved via gdb scripts, but crash is already
there.
But let's see if the formats actually differ. In the end, crash is just
parsing
On 10/18/2011 10:39 AM, Jan Kiszka wrote:
Yeah, I see. Could also be solved via gdb scripts, but crash is already
there.
[ BTW, crash is for the dead. But having those features in form of gdb
scripts would also allow live system analysis. Looks like it's worth
obsoleting crash on the long
On Tue, Oct 18, 2011 at 12:41:10PM +0200, Paolo Bonzini wrote:
On 10/18/2011 10:39 AM, Jan Kiszka wrote:
Yeah, I see. Could also be solved via gdb scripts, but crash is already
there.
[ BTW, crash is for the dead. But having those features in form of gdb
scripts would also allow live
On 2011-10-18 12:41, Paolo Bonzini wrote:
On 10/18/2011 10:39 AM, Jan Kiszka wrote:
Yeah, I see. Could also be solved via gdb scripts, but crash is already
there.
[ BTW, crash is for the dead. But having those features in form of gdb
scripts would also allow live system analysis. Looks
On 2011-10-18 12:42, Christoph Hellwig wrote:
On Tue, Oct 18, 2011 at 12:41:10PM +0200, Paolo Bonzini wrote:
On 10/18/2011 10:39 AM, Jan Kiszka wrote:
Yeah, I see. Could also be solved via gdb scripts, but crash is already
there.
[ BTW, crash is for the dead. But having those features in
On Tue, Oct 18, 2011 at 02:47:39PM +0200, Jan Kiszka wrote:
Crash can also do live system analysis. :)
crash in fact is gdb - with a lot of additional commands.
Is there a trick to make it work against a gdbserver?
No idea. I just noticed that crash was built around a gdb source
tree
On 2011-10-18 15:08, Christoph Hellwig wrote:
On Tue, Oct 18, 2011 at 02:47:39PM +0200, Jan Kiszka wrote:
Crash can also do live system analysis. :)
crash in fact is gdb - with a lot of additional commands.
Is there a trick to make it work against a gdbserver?
No idea. I just noticed
On Tue, Oct 18, 2011 at 12:47:23PM +0200, Jan Kiszka wrote:
On 2011-10-18 12:41, Paolo Bonzini wrote:
On 10/18/2011 10:39 AM, Jan Kiszka wrote:
Yeah, I see. Could also be solved via gdb scripts, but crash is already
there.
[ BTW, crash is for the dead. But having those features in
On 2011-10-18 15:30, Richard W.M. Jones wrote:
On Tue, Oct 18, 2011 at 12:47:23PM +0200, Jan Kiszka wrote:
On 2011-10-18 12:41, Paolo Bonzini wrote:
On 10/18/2011 10:39 AM, Jan Kiszka wrote:
Yeah, I see. Could also be solved via gdb scripts, but crash is already
there.
[ BTW, crash is for
On 10/18/2011 06:28 PM, Jan Kiszka wrote:
On 2011-10-18 11:43, Wen Congyang wrote:
At 10/18/2011 04:36 PM, Jan Kiszka Write:
On 2011-10-18 10:34, Richard W.M. Jones wrote:
Yeah, I see. Could also be solved via gdb scripts, but crash is already
there.
But let's see if the formats actually
On 2011-10-18 15:51, Wen Congyang wrote:
On 10/18/2011 06:28 PM, Jan Kiszka wrote:
On 2011-10-18 11:43, Wen Congyang wrote:
At 10/18/2011 04:36 PM, Jan Kiszka Write:
On 2011-10-18 10:34, Richard W.M. Jones wrote:
Yeah, I see. Could also be solved via gdb scripts, but crash is already
there.
On 10/18/2011 09:55 PM, Jan Kiszka wrote:
On 2011-10-18 15:51, Wen Congyang wrote:
On 10/18/2011 06:28 PM, Jan Kiszka wrote:
On 2011-10-18 11:43, Wen Congyang wrote:
At 10/18/2011 04:36 PM, Jan Kiszka Write:
On 2011-10-18 10:34, Richard W.M. Jones wrote:
Yeah, I see. Could also be solved
On 2011-10-18 16:17, Wen Congyang wrote:
On 10/18/2011 09:55 PM, Jan Kiszka wrote:
On 2011-10-18 15:51, Wen Congyang wrote:
On 10/18/2011 06:28 PM, Jan Kiszka wrote:
On 2011-10-18 11:43, Wen Congyang wrote:
At 10/18/2011 04:36 PM, Jan Kiszka Write:
On 2011-10-18 10:34, Richard W.M. Jones
On 10/18/2011 10:21 PM, Jan Kiszka wrote:
On 2011-10-18 16:17, Wen Congyang wrote:
I was talking about information you need in the crash dump file that is
not contained in those files crash processes by default. If there is no
such information, then it looks strange to me defining a new format.
On 2011-10-18 17:04, Wen Congyang wrote:
On 10/18/2011 10:21 PM, Jan Kiszka wrote:
On 2011-10-18 16:17, Wen Congyang wrote:
I was talking about information you need in the crash dump file that is
not contained in those files crash processes by default. If there is no
such information, then
At 10/18/2011 11:27 PM, Jan Kiszka Write:
On 2011-10-18 17:04, Wen Congyang wrote:
On 10/18/2011 10:21 PM, Jan Kiszka wrote:
On 2011-10-18 16:17, Wen Congyang wrote:
I was talking about information you need in the crash dump file that is
not contained in those files crash processes by
On Tue, 18 Oct 2011 10:31:10 +0200
Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-10-18 10:31, Wen Congyang wrote:
At 10/18/2011 04:26 PM, Jan Kiszka Write:
On 2011-10-18 10:25, Wen Congyang wrote:
At 10/18/2011 04:19 PM, Jan Kiszka Write:
On 2011-10-18 09:58, Wen Congyang wrote:
At
On 2011-10-11 04:20, Wen Congyang wrote:
The other reason why it would be good, is that we would then have a clearly
defined standard QEMU dump format, instead of libvirt dump format for
QEMU
A core file would be that format - for direct gdb processing. No
proprietary re-inventions please.
At 10/11/2011 02:58 PM, Jan Kiszka Write:
On 2011-10-11 04:20, Wen Congyang wrote:
The other reason why it would be good, is that we would then have a
clearly
defined standard QEMU dump format, instead of libvirt dump format for
QEMU
A core file would be that format - for direct gdb
On 2011-10-10 04:21, Wen Congyang wrote:
At 10/09/2011 06:23 PM, Richard W.M. Jones Write:
On Sun, Oct 09, 2011 at 10:49:57AM +0200, Jan Kiszka wrote:
As explained in the other replies: It is way more future-proof to use an
interface for this which was designed for it (remote gdb) instead of
At 10/10/2011 02:52 PM, Jan Kiszka Write:
On 2011-10-10 04:21, Wen Congyang wrote:
At 10/09/2011 06:23 PM, Richard W.M. Jones Write:
On Sun, Oct 09, 2011 at 10:49:57AM +0200, Jan Kiszka wrote:
As explained in the other replies: It is way more future-proof to use an
interface for this which
On 2011-10-10 08:59, Wen Congyang wrote:
At 10/10/2011 02:52 PM, Jan Kiszka Write:
On 2011-10-10 04:21, Wen Congyang wrote:
At 10/09/2011 06:23 PM, Richard W.M. Jones Write:
On Sun, Oct 09, 2011 at 10:49:57AM +0200, Jan Kiszka wrote:
As explained in the other replies: It is way more
Am 10.10.2011 um 08:52 schrieb Jan Kiszka jan.kis...@web.de:
On 2011-10-10 04:21, Wen Congyang wrote:
At 10/09/2011 06:23 PM, Richard W.M. Jones Write:
On Sun, Oct 09, 2011 at 10:49:57AM +0200, Jan Kiszka wrote:
As explained in the other replies: It is way more future-proof to use an
On 2011-10-10 09:08, Alexander Graf wrote:
Am 10.10.2011 um 08:52 schrieb Jan Kiszka jan.kis...@web.de:
On 2011-10-10 04:21, Wen Congyang wrote:
At 10/09/2011 06:23 PM, Richard W.M. Jones Write:
On Sun, Oct 09, 2011 at 10:49:57AM +0200, Jan Kiszka wrote:
As explained in the other replies:
At 10/10/2011 03:01 PM, Jan Kiszka Write:
On 2011-10-10 08:59, Wen Congyang wrote:
At 10/10/2011 02:52 PM, Jan Kiszka Write:
On 2011-10-10 04:21, Wen Congyang wrote:
At 10/09/2011 06:23 PM, Richard W.M. Jones Write:
On Sun, Oct 09, 2011 at 10:49:57AM +0200, Jan Kiszka wrote:
As explained in
On 2011-10-10 09:17, Wen Congyang wrote:
At 10/10/2011 03:01 PM, Jan Kiszka Write:
On 2011-10-10 08:59, Wen Congyang wrote:
At 10/10/2011 02:52 PM, Jan Kiszka Write:
On 2011-10-10 04:21, Wen Congyang wrote:
At 10/09/2011 06:23 PM, Richard W.M. Jones Write:
On Sun, Oct 09, 2011 at 10:49:57AM
At 10/10/2011 03:22 PM, Jan Kiszka Write:
On 2011-10-10 09:17, Wen Congyang wrote:
At 10/10/2011 03:01 PM, Jan Kiszka Write:
On 2011-10-10 08:59, Wen Congyang wrote:
At 10/10/2011 02:52 PM, Jan Kiszka Write:
On 2011-10-10 04:21, Wen Congyang wrote:
At 10/09/2011 06:23 PM, Richard W.M. Jones
On 2011-10-10 09:47, Wen Congyang wrote:
At 10/10/2011 03:22 PM, Jan Kiszka Write:
On 2011-10-10 09:17, Wen Congyang wrote:
At 10/10/2011 03:01 PM, Jan Kiszka Write:
On 2011-10-10 08:59, Wen Congyang wrote:
At 10/10/2011 02:52 PM, Jan Kiszka Write:
On 2011-10-10 04:21, Wen Congyang wrote:
At 10/10/2011 03:48 PM, Jan Kiszka Write:
On 2011-10-10 09:47, Wen Congyang wrote:
At 10/10/2011 03:22 PM, Jan Kiszka Write:
On 2011-10-10 09:17, Wen Congyang wrote:
At 10/10/2011 03:01 PM, Jan Kiszka Write:
On 2011-10-10 08:59, Wen Congyang wrote:
At 10/10/2011 02:52 PM, Jan Kiszka Write:
On Fri, Oct 07, 2011 at 02:56:56PM +0200, Jan Kiszka wrote:
On 2011-10-07 14:25, Wen Congyang wrote:
于 2011/10/7 18:16, Jan Kiszka 写道:
On 2011-10-07 11:46, Wen Congyang wrote:
Currently, virsh dump uses monitor command migrate to dump guest's memory
to file, and we can use crash to
On Mon, Oct 10, 2011 at 08:52:08AM +0200, Jan Kiszka wrote:
On 2011-10-10 04:21, Wen Congyang wrote:
At 10/09/2011 06:23 PM, Richard W.M. Jones Write:
On Sun, Oct 09, 2011 at 10:49:57AM +0200, Jan Kiszka wrote:
As explained in the other replies: It is way more future-proof to use an
On Mon, Oct 10, 2011 at 10:21:02AM +0800, Wen Congyang wrote:
At 10/09/2011 06:23 PM, Richard W.M. Jones Write:
On Sun, Oct 09, 2011 at 10:49:57AM +0200, Jan Kiszka wrote:
As explained in the other replies: It is way more future-proof to use an
interface for this which was designed for it
On Mon, Oct 10, 2011 at 10:08:26AM +0100, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 10:21:02AM +0800, Wen Congyang wrote:
At 10/09/2011 06:23 PM, Richard W.M. Jones Write:
On Sun, Oct 09, 2011 at 10:49:57AM +0200, Jan Kiszka wrote:
As explained in the other replies: It is way more
On 2011-10-10 11:02, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 08:52:08AM +0200, Jan Kiszka wrote:
On 2011-10-10 04:21, Wen Congyang wrote:
At 10/09/2011 06:23 PM, Richard W.M. Jones Write:
On Sun, Oct 09, 2011 at 10:49:57AM +0200, Jan Kiszka wrote:
As explained in the other replies:
On Mon, Oct 10, 2011 at 10:10:21AM +0100, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 10:08:26AM +0100, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 10:21:02AM +0800, Wen Congyang wrote:
At 10/09/2011 06:23 PM, Richard W.M. Jones Write:
On Sun, Oct 09, 2011 at 10:49:57AM
On 2011-10-10 11:10, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 10:08:26AM +0100, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 10:21:02AM +0800, Wen Congyang wrote:
At 10/09/2011 06:23 PM, Richard W.M. Jones Write:
On Sun, Oct 09, 2011 at 10:49:57AM +0200, Jan Kiszka wrote:
As
On 2011-10-10 11:34, Richard W.M. Jones wrote:
On Mon, Oct 10, 2011 at 10:10:21AM +0100, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 10:08:26AM +0100, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 10:21:02AM +0800, Wen Congyang wrote:
At 10/09/2011 06:23 PM, Richard W.M. Jones Write:
On Mon, Oct 10, 2011 at 11:34:44AM +0200, Jan Kiszka wrote:
On 2011-10-10 11:10, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 10:08:26AM +0100, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 10:21:02AM +0800, Wen Congyang wrote:
At 10/09/2011 06:23 PM, Richard W.M. Jones Write:
On
On Mon, Oct 10, 2011 at 11:34:44AM +0200, Jan Kiszka wrote:
On 2011-10-10 11:10, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 10:08:26AM +0100, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 10:21:02AM +0800, Wen Congyang wrote:
At 10/09/2011 06:23 PM, Richard W.M. Jones Write:
On
On 10/10/2011 12:21 PM, Alon Levy wrote:
A core file would be that format - for direct gdb processing. No
proprietary re-inventions please.
Just a note: A core file to windows core dump file would be nice for
windows guest crashes.
That requires cooperation from a kernel driver in the
On Mon, Oct 10, 2011 at 12:48:52PM +0200, Paolo Bonzini wrote:
On 10/10/2011 12:21 PM, Alon Levy wrote:
A core file would be that format - for direct gdb processing. No
proprietary re-inventions please.
Just a note: A core file to windows core dump file would be nice for
windows guest
On 10/10/2011 01:04 PM, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 12:48:52PM +0200, Paolo Bonzini wrote:
On 10/10/2011 12:21 PM, Alon Levy wrote:
A core file would be that format - for direct gdb processing. No
proprietary re-inventions please.
Just a note: A core
At 10/10/2011 06:19 PM, Daniel P. Berrange Write:
On Mon, Oct 10, 2011 at 11:34:44AM +0200, Jan Kiszka wrote:
On 2011-10-10 11:10, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 10:08:26AM +0100, Daniel P. Berrange wrote:
On Mon, Oct 10, 2011 at 10:21:02AM +0800, Wen Congyang wrote:
At
At 10/10/2011 05:34 PM, Jan Kiszka Write:
On 2011-10-10 11:02, Daniel P. Berrange wrote:
Run gdb with set debug remote 1 and watch the communication, it is not
that complex. But a dump command is probably simpler for those
scenarios, I agree.
We have determined to introduce a new command
On 2011-10-08 17:16, Richard W.M. Jones wrote:
On Fri, Oct 07, 2011 at 12:16:07PM +0200, Jan Kiszka wrote:
On 2011-10-07 11:46, Wen Congyang wrote:
Currently, virsh dump uses monitor command migrate to dump guest's memory
to file, and we can use crash to analyze the file.
Unfortunately,
On Sun, Oct 09, 2011 at 10:49:57AM +0200, Jan Kiszka wrote:
As explained in the other replies: It is way more future-proof to use an
interface for this which was designed for it (remote gdb) instead of
artificially relaxing reasonable constraints of the migration mechanism
plus having to
On 2011-10-09 12:23, Richard W.M. Jones wrote:
On Sun, Oct 09, 2011 at 10:49:57AM +0200, Jan Kiszka wrote:
As explained in the other replies: It is way more future-proof to use an
interface for this which was designed for it (remote gdb) instead of
artificially relaxing reasonable constraints
At 10/09/2011 06:23 PM, Richard W.M. Jones Write:
On Sun, Oct 09, 2011 at 10:49:57AM +0200, Jan Kiszka wrote:
As explained in the other replies: It is way more future-proof to use an
interface for this which was designed for it (remote gdb) instead of
artificially relaxing reasonable
On Fri, Oct 07, 2011 at 12:16:07PM +0200, Jan Kiszka wrote:
On 2011-10-07 11:46, Wen Congyang wrote:
Currently, virsh dump uses monitor command migrate to dump guest's memory
to file, and we can use crash to analyze the file.
Unfortunately, virsh dump can not work if guest uses host pci
Currently, virsh dump uses monitor command migrate to dump guest's memory
to file, and we can use crash to analyze the file.
Unfortunately, virsh dump can not work if guest uses host pci device. The
reason is that the device's status is also needed to migrate to remote machine,
and the host pci
On 2011-10-07 11:46, Wen Congyang wrote:
Currently, virsh dump uses monitor command migrate to dump guest's memory
to file, and we can use crash to analyze the file.
Unfortunately, virsh dump can not work if guest uses host pci device. The
reason is that the device's status is also needed to
于 2011/10/7 18:16, Jan Kiszka 写道:
On 2011-10-07 11:46, Wen Congyang wrote:
Currently, virsh dump uses monitor command migrate to dump guest's memory
to file, and we can use crash to analyze the file.
Unfortunately, virsh dump can not work if guest uses host pci device. The
reason is that the
On 2011-10-07 14:25, Wen Congyang wrote:
于 2011/10/7 18:16, Jan Kiszka 写道:
On 2011-10-07 11:46, Wen Congyang wrote:
Currently, virsh dump uses monitor command migrate to dump guest's memory
to file, and we can use crash to analyze the file.
Unfortunately, virsh dump can not work if guest
于 2011/10/7 20:56, Jan Kiszka 写道:
On 2011-10-07 14:25, Wen Congyang wrote:
于 2011/10/7 18:16, Jan Kiszka 写道:
On 2011-10-07 11:46, Wen Congyang wrote:
Currently, virsh dump uses monitor command migrate to dump guest's memory
to file, and we can use crash to analyze the file.
Unfortunately,
On 2011-10-07 16:05, Wen Congyang wrote:
于 2011/10/7 20:56, Jan Kiszka 写道:
On 2011-10-07 14:25, Wen Congyang wrote:
于 2011/10/7 18:16, Jan Kiszka 写道:
On 2011-10-07 11:46, Wen Congyang wrote:
Currently, virsh dump uses monitor command migrate to dump guest's memory
to file, and we can use
96 matches
Mail list logo
