From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6372 invoked by alias); 10 Oct 2011 13:41:01 -0000 Received: (qmail 6363 invoked by uid 22791); 10 Oct 2011 13:40:59 -0000 X-SWARE-Spam-Status: No, hits=-7.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS,TW_QE X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 10 Oct 2011 13:40:45 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p9ADej0o020358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 10 Oct 2011 09:40:45 -0400 Received: from localhost (vpn1-4-177.ams2.redhat.com [10.36.4.177]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p9ADehfB008391; Mon, 10 Oct 2011 09:40:44 -0400 Date: Mon, 10 Oct 2011 13:41:00 -0000 From: "Richard W.M. Jones" To: "Frank Ch. Eigler" Cc: systemtap@sources.redhat.com Subject: Re: Systemtap + tracing processes inside a qemu guest Message-ID: <20111010134043.GQ16799@amd.home.annexia.org> References: <20111010091026.GA15664@amd.home.annexia.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2011-q4/txt/msg00032.txt.bz2 On Mon, Oct 10, 2011 at 09:35:30AM -0400, Frank Ch. Eigler wrote: > "Richard W.M. Jones" writes: > > > [...] > > However to get the complete picture I'd like to > > instrument the daemon too. The aim would be to get timing information > > across both the host program and the daemon: > > > > 0.001s program event #1 send message > > 0.005s daemon event #1 receive message > > 0.010s daemon event #2 send reply > > 0.025s program event #2 receive reply > > [...] > > What's possible at the moment? > > You're looking for probing two separate systems (the host and the > guest) together. The general model does not stretch that far right > now (and probably would not be easy to extend it that way). The > closest thing would be running separate scripts, one on the host, and > one on the guest via --remote, and merging the events together after > the fact. Can you point me to an example of using --remote in this simpler case (just into a qemu guest)? Could events from inside the qemu guest be somehow transferred to the host kernel so that we can collect them all in one place? (I don't really know exactly how this works ...) Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org