From: "Ed Swierk" <eswierk@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Remote console access though socket
Date: Wed, 8 Mar 2006 12:35:13 -0800 [thread overview]
Message-ID: <c1bf1cf0603081235u118aade2o120f94347602dc3b@mail.gmail.com> (raw)
In-Reply-To: <16af12af0603081035h5f61d947y6c24b7a7675eeb14@mail.gmail.com>
Daniel Veillard wrote:
> enclosed is a first version of a patch to allow remote access and control
> for QEmu instances, I'm not suggesting to apply it as is (though it seems
> to work in my limited testing) but would rather like to get comments back
> for choices I'm facing.
This sounds pretty nice. A few general comments:
A few weeks ago I wrote a qemu daemon manager. It's a pretty simple
script that manages multiple qemu processes, launching each one in an
instance of screen. screen does most of the dirty work of keeping
track of running processes, assigning a name to each process,
attaching to a process's console, terminating a process, etc. Of
course screen has many more features that we don't really need, but it
might be worth looking at screen as a model for implementing the
functions you describe.
The other problem my script deals with, which screen doesn't solve, is
managing resources like ports (for -redir) and network interface MAC
addresses (in cases where uniqueness matters), and providing some way
for the user to determine which resource has been assigned to a
particular qemu process.
If qemu provides access to its console via a socket, this is just
another resource that a manager can deal with, perhaps passing the
desired port number to qemu via the command line.
--Ed
next prev parent reply other threads:[~2006-03-08 20:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 14:52 [Qemu-devel] [PATCH] Remote console access though socket Daniel Veillard
[not found] ` <16af12af0603081035h5f61d947y6c24b7a7675eeb14@mail.gmail.com>
2006-03-08 20:35 ` Ed Swierk [this message]
2006-03-11 20:53 ` Daniel Veillard
2006-03-11 16:24 ` Oliver Gerlich
2006-03-11 20:59 ` Daniel Veillard
2006-03-11 22:22 ` Oliver Gerlich
2006-03-12 11:03 ` Daniel Veillard
2006-03-11 21:07 ` Daniel Veillard
-- strict thread matches above, loose matches on Subject: below --
2006-03-09 12:47 wanderer
2006-03-09 12:55 ` Daniel Veillard
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=c1bf1cf0603081235u118aade2o120f94347602dc3b@mail.gmail.com \
--to=eswierk@gmail.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).