From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/13078] New: investigate qemu virtio-serial channel for talking to stap-sh
Date: Thu, 11 Aug 2011 18:21:00 -0000 [thread overview]
Message-ID: <bug-13078-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=13078
Bug #: 13078
Summary: investigate qemu virtio-serial channel for talking to
stap-sh
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap@sourceware.org
ReportedBy: fche@redhat.com
Classification: Unclassified
qemu's virtio/serial widget allows a secure bidirectional channel for
the host to talk to a guest. We could investigate setting up some guest-side
infrastructure to have a copy of stap-sh listen on one or more such channels,
to launch stap modules without having to set up ssh.
Possible user interface:
(HOST)
% qemu-kvm -chardev socket,id=systemtap.0,server,nowait,path=/PATH/TO/SOCKET
...
% stap --remote=unix:/PATH/TO/SOCKET ...
(GUEST)
Have a systemd or sysvinit script to start up / respawn
stap-sh </dev/virtio-ports/systemtap.0 >/dev/virtio-ports/systemtap.0 2>&1
See also:
http://www.linux-kvm.org/page/Virtio-serial_API
https://rwmj.wordpress.com/2011/07/07/how-does-libguestfs-live-work/
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-08-11 18:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 18:21 fche at redhat dot com [this message]
2011-08-17 0:42 ` [Bug runtime/13078] " jistone at redhat dot com
2011-08-17 0:43 ` jistone at redhat dot com
2011-08-17 22:54 ` jistone at redhat dot com
2013-08-09 18:17 ` jlebon at redhat dot com
2013-08-20 21:40 ` jistone at redhat dot com
2013-08-21 13:29 ` fche at redhat dot com
2013-08-21 14:00 ` jlebon at redhat dot com
2013-08-21 17:32 ` jistone at redhat dot com
2013-08-26 18:07 ` jlebon at redhat dot com
2013-08-27 16:20 ` jlebon at redhat dot com
2013-08-28 16:21 ` jlebon at redhat dot com
2013-08-30 20:37 ` jlebon at redhat dot com
2013-09-04 16:18 ` jlebon at redhat dot com
2013-09-11 18:49 ` jlebon at redhat dot com
2013-09-24 21:23 ` jlebon at redhat dot com
2013-09-26 20:54 ` jlebon at redhat dot com
2013-10-18 14:26 ` jlebon at redhat dot com
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=bug-13078-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).