From: "Daniel P. Berrange" <berrange@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Wen Congyang <wencongyang@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [Question] dump memory when host pci device is used by guest
Date: Mon, 10 Oct 2011 10:00:51 +0100 [thread overview]
Message-ID: <20111010090051.GE9408@redhat.com> (raw)
In-Reply-To: <4E8EF718.1050402@siemens.com>
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 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 device's status is not stored in qemu. So it is unmigratable.
> >>>
> >>> I think we can we can add a option to qmp command migrate(eg: skip) to allow
> >>> the user to skip the check, and this option should be used only when dumping
> >>> the guest's memory.
> >>
> >> Why not simply attach gdb? That works independently of migration.
> >
> > If qemu has some problem, we can use gdb to debug it. But if guest os
> > has problem
> > (eg:kernel panic and kdump does not work), we should dump guest's memory
> > and use
> > crash to analyze.
>
> qemu-system-xxx -s (or "gdbserver" via monitor if qemu is already
> running), gdb vmlinux, then "target remote :1234".
That is already possible, but that is not what we need for 'virsh dump'.
The goal of that API is to provide a coredump of the guest, which can
then be analysed off-node/site. While in theory you could attach GDB
to the QEMU process and use GDB commands to then write out a coredump
this isn't really satisfactory because too many large companies have
security/audit compliance rules which forbid installation of developer
tools (compilers, debuggers, etc) on production servers. So we cannot
assume GDB is available.
We need to be able to create a coredump natively from either QEMU or
libvirt, with minimal of external tools.
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2011-10-10 9:01 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 9:46 [Qemu-devel] [Question] dump memory when host pci device is used by guest Wen Congyang
2011-10-07 10:16 ` Jan Kiszka
2011-10-07 12:25 ` Wen Congyang
2011-10-07 12:56 ` Jan Kiszka
2011-10-07 14:05 ` Wen Congyang
2011-10-07 15:06 ` Jan Kiszka
2011-10-10 9:00 ` Daniel P. Berrange [this message]
2011-10-08 15:16 ` Richard W.M. Jones
2011-10-09 8:49 ` Jan Kiszka
2011-10-09 10:23 ` Richard W.M. Jones
2011-10-09 10:26 ` Jan Kiszka
2011-10-10 2:21 ` Wen Congyang
2011-10-10 6:52 ` Jan Kiszka
2011-10-10 6:59 ` Wen Congyang
2011-10-10 7:01 ` Jan Kiszka
2011-10-10 7:17 ` Wen Congyang
2011-10-10 7:22 ` Jan Kiszka
2011-10-10 7:47 ` Wen Congyang
2011-10-10 7:48 ` Jan Kiszka
2011-10-10 8:28 ` Wen Congyang
2011-10-10 7:08 ` Alexander Graf
2011-10-10 7:10 ` Jan Kiszka
2011-10-10 9:02 ` Daniel P. Berrange
2011-10-10 9:34 ` Jan Kiszka
2011-10-11 2:27 ` Wen Congyang
2011-10-18 7:15 ` Wen Congyang
2011-10-18 7:52 ` Jan Kiszka
2011-10-18 7:58 ` Wen Congyang
2011-10-18 8:19 ` Jan Kiszka
2011-10-18 8:25 ` Wen Congyang
2011-10-18 8:26 ` Jan Kiszka
2011-10-18 8:31 ` Wen Congyang
2011-10-18 8:31 ` Jan Kiszka
2011-10-18 8:34 ` Richard W.M. Jones
2011-10-18 8:36 ` Jan Kiszka
2011-10-18 8:39 ` Jan Kiszka
2011-10-18 10:41 ` Paolo Bonzini
2011-10-18 10:42 ` Christoph Hellwig
2011-10-18 12:47 ` Jan Kiszka
2011-10-18 13:08 ` Christoph Hellwig
2011-10-18 13:13 ` Jan Kiszka
2011-10-18 10:47 ` Jan Kiszka
2011-10-18 13:30 ` Richard W.M. Jones
2011-10-18 13:34 ` Jan Kiszka
2011-10-18 9:43 ` Wen Congyang
2011-10-18 10:28 ` Jan Kiszka
2011-10-18 13:51 ` Wen Congyang
2011-10-18 13:55 ` Jan Kiszka
2011-10-18 14:17 ` Wen Congyang
2011-10-18 14:21 ` Jan Kiszka
2011-10-18 15:04 ` Wen Congyang
2011-10-18 15:27 ` Jan Kiszka
2011-10-19 1:23 ` Wen Congyang
2011-10-19 2:04 ` KAMEZAWA Hiroyuki
2011-10-19 11:40 ` Jan Kiszka
2011-10-20 1:22 ` Wen Congyang
2011-10-20 9:41 ` Jan Kiszka
2011-10-20 10:03 ` Wen Congyang
2011-10-21 7:11 ` Jan Kiszka
2011-10-21 7:50 ` Wen Congyang
2011-10-21 13:02 ` Dave Anderson
2011-10-21 13:16 ` Jan Kiszka
2011-10-21 14:12 ` Richard W.M. Jones
2011-10-24 2:25 ` Wen Congyang
2011-10-24 14:25 ` Dave Anderson
2011-10-24 15:01 ` Avi Kivity
2011-10-24 15:25 ` Dave Anderson
2011-10-24 15:30 ` Avi Kivity
2011-10-24 15:58 ` Dave Anderson
2011-10-25 1:37 ` Wen Congyang
2011-10-25 7:37 ` Jan Kiszka
2011-10-25 8:06 ` Wen Congyang
2011-10-25 8:23 ` Avi Kivity
2011-10-25 8:35 ` Paolo Bonzini
2011-10-25 8:52 ` Avi Kivity
2011-10-25 8:56 ` Paolo Bonzini
2011-10-25 9:19 ` Jan Kiszka
2011-10-25 13:18 ` Dave Anderson
2011-10-25 13:22 ` Avi Kivity
2011-10-18 7:58 ` Daniel P. Berrange
2011-10-18 8:17 ` Jan Kiszka
2011-10-18 8:25 ` Jan Kiszka
2011-10-18 8:25 ` Daniel P. Berrange
2011-10-18 8:30 ` Jan Kiszka
2011-10-10 9:08 ` Daniel P. Berrange
2011-10-10 9:10 ` Daniel P. Berrange
2011-10-10 9:34 ` Richard W.M. Jones
2011-10-10 10:17 ` Jan Kiszka
2011-10-10 9:34 ` Jan Kiszka
2011-10-10 10:19 ` Daniel P. Berrange
2011-10-11 2:20 ` Wen Congyang
2011-10-11 6:58 ` Jan Kiszka
2011-10-11 7:13 ` Wen Congyang
2011-10-10 10:21 ` Alon Levy
2011-10-10 10:48 ` Paolo Bonzini
2011-10-10 11:04 ` Daniel P. Berrange
2011-10-10 11:09 ` Paolo Bonzini
2011-10-10 12:00 ` [Qemu-devel] windows crash dump header. was: " Alon Levy
2011-10-10 12:38 ` Paolo Bonzini
2011-10-10 13:47 ` Alon Levy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111010090051.GE9408@redhat.com \
--to=berrange@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wencongyang@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).