From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:48966) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UKlys-0003tD-4s for qemu-devel@nongnu.org; Wed, 27 Mar 2013 04:45:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UKlyq-0001RL-W0 for qemu-devel@nongnu.org; Wed, 27 Mar 2013 04:45:14 -0400 Received: from mx4-phx2.redhat.com ([209.132.183.25]:56626) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UKlyq-0001RE-Oe for qemu-devel@nongnu.org; Wed, 27 Mar 2013 04:45:12 -0400 Date: Wed, 27 Mar 2013 04:45:09 -0400 (EDT) From: Paolo Bonzini Message-ID: <2098812672.15904995.1364373909716.JavaMail.root@redhat.com> In-Reply-To: <51529001.8040102@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 0/5] Add some tracepoints for clarification of the cause of troubles List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kazuya Saito Cc: qemu-devel@nongnu.org > > Wouldn't you get the same information from the command line? > > I think the information you said is different from what I meant. The > information I wanted to know is whether QEMU creates/deletes a device > successfully or not. Failing to create a device will always exit QEMU. If you cannot assume that, you're really in debugging territory and your tools should be the "info" monitor commands (info qtree, info pci) or gdb... > We cannot get it from the command line. > I was sure I specified a NIC device for the guest, but the Windows > guest didn't have it when it booted. There were two possibilities. One > was QEMU failed to create the NIC device, and the other was QEMU created > it successfully and the Windows guest failed to detect it. Since QEMU > output limited message at the moment, it was difficult to prove that > it was not QEMU's issue. I took a coredump of the QEMU and proved > the QEMU must have a valid structures for the NIC device. I believe the > tracepoints could have allowed me to figure out where the issue > existed a lot faster and easier. Had you tried "info qtree" or "info pci"? Paolo