On Thu, Mar 24, 2016 at 10:13:17AM +, Stefan Hajnoczi wrote:
> There are probably race conditions if the tsc offset is queried
> independently from the trace collection. For example, imagine the host
> is suspend right when tracing begins. I think the TSC could be adjusted
> when the host wak
On Thu, Mar 24, 2016 at 09:02:08AM -0400, Luiz Capitulino wrote:
> On Thu, 24 Mar 2016 13:16:20 +0800
> Peter Xu wrote:
>
> > Hi, Steven,
> >
> > On Fri, Mar 04, 2016 at 08:23:11AM -0500, Steven Rostedt wrote:
> > > My idea for a trace-cmd server, is to have a --client operation, for
> > > runni
On Thu, 24 Mar 2016 13:16:20 +0800
Peter Xu wrote:
> Hi, Steven,
>
> On Fri, Mar 04, 2016 at 08:23:11AM -0500, Steven Rostedt wrote:
> > My idea for a trace-cmd server, is to have a --client operation, for
> > running on the guest.
> >
> > trace-cmd server --client
> >
> > The connection wil
On Thu, Mar 24, 2016 at 04:42:42PM +0800, Peter Xu wrote:
> On Fri, Mar 04, 2016 at 11:19:33AM +, Stefan Hajnoczi wrote:
> > On Thu, Mar 03, 2016 at 02:35:01PM -0500, Luiz Capitulino wrote:
> > > trace-cmd-server
> > >
> > >
> > > Everything I described could look like this:
>
On Fri, Mar 04, 2016 at 11:19:33AM +, Stefan Hajnoczi wrote:
> On Thu, Mar 03, 2016 at 02:35:01PM -0500, Luiz Capitulino wrote:
> > trace-cmd-server
> >
> >
> > Everything I described could look like this:
> >
> > # trace-cmd server [ in the host ]
> > # trace-cmd record
Hi, Steven,
On Fri, Mar 04, 2016 at 08:23:11AM -0500, Steven Rostedt wrote:
> My idea for a trace-cmd server, is to have a --client operation, for
> running on the guest.
>
> trace-cmd server --client
>
> The connection will be some socket, either network or something
> directly attached to th
On 07/03/2016 17:26, Steven Rostedt wrote:
> > > How's the connection set up. That is, how does it know the commands are
> > > coming from the host? And how does it know that the commands from the
> > > host is from a trusted source? If the host is compromised, is there
> > > anything keeping an
On Mon, 7 Mar 2016 09:10:10 -0700
Eric Blake wrote:
> On 03/07/2016 08:49 AM, Steven Rostedt wrote:
> > On Mon, 7 Mar 2016 15:17:05 +
> > Stefan Hajnoczi wrote:
> >
> >
> >> qemu-guest-agent runs inside the guest and replies to RPC commands from
> >> the host. It is used for backups, sh
On 03/07/2016 08:49 AM, Steven Rostedt wrote:
> On Mon, 7 Mar 2016 15:17:05 +
> Stefan Hajnoczi wrote:
>
>
>> qemu-guest-agent runs inside the guest and replies to RPC commands from
>> the host. It is used for backups, shutdown, network configuration, etc.
>> From time to time people have w
On Mon, 7 Mar 2016 15:17:05 +
Stefan Hajnoczi wrote:
> qemu-guest-agent runs inside the guest and replies to RPC commands from
> the host. It is used for backups, shutdown, network configuration, etc.
> From time to time people have wanted the ability to execute an arbitrary
> command insid
On Fri, Mar 04, 2016 at 08:23:11AM -0500, Steven Rostedt wrote:
> The problem I have with the guest server, and something that we may be
> able to fix later on, but should always keep it in the back of our
> minds, is the security issue. For this to work, the guest server needs
> to run as root. It
On Fri, 4 Mar 2016 11:19:33 +
Stefan Hajnoczi wrote:
> > 2. Build a trace-cmd-server
> >
> > Which does the following:
> >
> > 1. Receive trace-cmd record commands from a guest,
> > to be performed in the host
>
> Sometimes the opposite is desirable: the host control
On Thu, Mar 03, 2016 at 02:35:01PM -0500, Luiz Capitulino wrote:
> trace-cmd-server
>
>
> Everything I described could look like this:
>
> # trace-cmd server [ in the host ]
> # trace-cmd record [ in the guest ]
> # trace-cmd report [ in the host, to merge the traces ]
>
>
Very recently, trace-cmd got a few new features that allow you
to merge the host and guest kernel traces using the host TSC.
Those features originated in the tracing we're doing to debug spikes
in real-time KVM. However, as real-time KVM uses a very specific
setup and as we have so far debugged a
14 matches
Mail list logo
