From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:54901) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UL5nC-00085u-DY for qemu-devel@nongnu.org; Thu, 28 Mar 2013 01:54:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UL5n9-0001X1-Qb for qemu-devel@nongnu.org; Thu, 28 Mar 2013 01:54:30 -0400 Received: from fgwmail5.fujitsu.co.jp ([192.51.44.35]:39801) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UL5n9-0001WT-As for qemu-devel@nongnu.org; Thu, 28 Mar 2013 01:54:27 -0400 Received: from m3.gw.fujitsu.co.jp (unknown [10.0.50.73]) by fgwmail5.fujitsu.co.jp (Postfix) with ESMTP id 70BB03EE0BC for ; Thu, 28 Mar 2013 14:54:22 +0900 (JST) Received: from smail (m3 [127.0.0.1]) by outgoing.m3.gw.fujitsu.co.jp (Postfix) with ESMTP id 55E8745DEBA for ; Thu, 28 Mar 2013 14:54:22 +0900 (JST) Received: from s3.gw.fujitsu.co.jp (s3.gw.fujitsu.co.jp [10.0.50.93]) by m3.gw.fujitsu.co.jp (Postfix) with ESMTP id 3F70845DEB6 for ; Thu, 28 Mar 2013 14:54:22 +0900 (JST) Received: from s3.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s3.gw.fujitsu.co.jp (Postfix) with ESMTP id 313EF1DB8038 for ; Thu, 28 Mar 2013 14:54:22 +0900 (JST) Received: from g01jpexchkw03.g01.fujitsu.local (g01jpexchkw03.g01.fujitsu.local [10.0.194.42]) by s3.gw.fujitsu.co.jp (Postfix) with ESMTP id D9613E08001 for ; Thu, 28 Mar 2013 14:54:21 +0900 (JST) Message-ID: <5153DADE.4000901@jp.fujitsu.com> Date: Thu, 28 Mar 2013 14:53:34 +0900 From: Kazuya Saito MIME-Version: 1.0 References: <2098812672.15904995.1364373909716.JavaMail.root@redhat.com> In-Reply-To: <2098812672.15904995.1364373909716.JavaMail.root@redhat.com> 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: Paolo Bonzini Cc: "qemu-devel@nongnu.org" (2013/03/27 17:45), Paolo Bonzini wrote:> >>> 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... That's a good point. >> 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"? I didn't try these commands. I tried them just now and it seems to solve the problem. So I think no need to add the tracepoints I posted. Thank you for your kindness. Kazuya