qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] QEMU Dbus support - a proposal management API
Date: Tue, 11 Dec 2007 15:58:42 +0000	[thread overview]
Message-ID: <20071211155842.GI17368@redhat.com> (raw)
In-Reply-To: <475EB146.9000105@codemonkey.ws>

On Tue, Dec 11, 2007 at 09:48:22AM -0600, Anthony Liguori wrote:
> Richard W.M. Jones wrote:
> 
> Actually, this was the original intention of the -name parameter.  What 
> a management tool would want to do is:
> 
> 1) if -name is specified by user, generate one with uuidgen
> 2) pass -name <name> and -pidfile /path/to/well/known/location/name.pid
> 
> This will ensure uniqueness of name without requiring the creation tool 
> to maintain any state (so no daemon is required).  Right now, you would 
> also have to store a monitor socket in that well known path.  However, 
> I'm working on a VNC tunnels patch right now that would allow the 
> monitor to be tunneled through a VNC session.  The idea here is that a 
> management tool could just store a hint about the VNC location and then 
> you can get at the rest of the character devices through the VNC session.
> 
> Otherwise, you end up with a bunch of temporary sockets for things like 
> the monitor, serial devices, parallel devices, etc.

Tunnelling things like the serial devices / parallel devices over VNC
would be very useful, as using a pty/file isn't useful for remote
management. Tunnelling the monitor over VNC is questionable though because
it has very significant security implications - if you can connect to the
VNC server, you essentially own the entire user account that the VM is
running under since the monitor can be used to map arbitrary files into
the guest VM. Now this may be useful in some cases, but for libvirt we
really just want the monitor accessible locally via a well-known UNIX
socket. Also, VNC ports are typically auto-allocated at startup so not
neccessary a good predictable access method.

The reason libvirt use the PTY & direct PID ownership was because we stared
off with QEMU 0.8.0. We should really just mandate use of QEMU 0.9.0 with
libvirt now since its been around quite a while. Then we could just run
with  -daemonize, -pidfile and -monitor unix:/well/known/path.

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

  reply	other threads:[~2007-12-11 15:58 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10  8:28 [Qemu-devel] [RFC] QEMU Dbus support - a proposal management API Yuval Kashtan
2007-12-10 20:51 ` Blue Swirl
2007-12-11  7:16   ` Yuval Kashtan
2007-12-11  9:10     ` Fabrice Bellard
2007-12-11  9:23       ` Laurent Vivier
2007-12-11 10:06         ` Brad Campbell
2007-12-11 10:07         ` Dor Laor
2007-12-11 14:51           ` Anthony Liguori
2007-12-11 15:00             ` Daniel P. Berrange
2007-12-11 15:21               ` Yuval Kashtan
2007-12-11 15:31                 ` Daniel P. Berrange
2007-12-11 15:36                 ` Anthony Liguori
2007-12-11 15:59                   ` Avi Kivity
2007-12-11 16:18                     ` Paul Brook
2007-12-11 16:40                       ` Avi Kivity
2007-12-11 15:02             ` Daniel P. Berrange
2007-12-11 15:15               ` Anthony Liguori
2007-12-11 15:40                 ` Richard W.M. Jones
2007-12-11 15:48                   ` Anthony Liguori
2007-12-11 15:58                     ` Daniel P. Berrange [this message]
2007-12-11 16:49                       ` Anthony Liguori
2007-12-11 17:04                         ` Daniel P. Berrange
2007-12-11 15:59                     ` Dor Laor
2007-12-11 15:17             ` Jean-Christian de Rivaz
2007-12-11 15:24               ` Daniel P. Berrange
2007-12-11 10:20         ` Andreas Färber
2007-12-11 10:29           ` Laurent Vivier
2007-12-11 10:50             ` Andreas Färber
2007-12-11 10:21         ` Heikki Lindholm
2007-12-11 11:05       ` Avi Kivity
2007-12-11 14:43         ` Anthony Liguori
2007-12-11 14:56         ` Daniel P. Berrange
2007-12-11 15:57           ` Avi Kivity
2007-12-11 16:07             ` Richard W.M. Jones
2007-12-11 15:44     ` Daniel P. Berrange
2007-12-11 16:10       ` Fabrice Bellard
2007-12-11 14:53 ` Daniel P. Berrange

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=20071211155842.GI17368@redhat.com \
    --to=berrange@redhat.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).