qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@cs.utexas.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/3] Add options to make writing a front end easier
Date: Sat, 16 Dec 2006 11:57:17 -0600	[thread overview]
Message-ID: <4584337D.6040706@cs.utexas.edu> (raw)

Howdy,

I've been working on a QEMU front end for a bit now.  The following 
patch introduces a number of things to make writing front ends in 
general a bit easier.  This includes making the char devices exposable 
as unix sockets and adding a daemonize option.

Unix sockets are useful for a front end because their permissions can be 
controlled and it's easier to guarantee uniqueness (verses trying to 
find an unused TCP port).

The daemonize option is useful as it provides a deterministic way to 
know that QEMU is ready to accept connections (for something like VNC).  
Otherwise, you have to use a connect loop and timeout attempting to 
connect.  This gets particularly ugly when an error occurs for some reason.

I've made an attempt to support the Win32 build but I haven't verified 
that current CVS is buildable (my changes shouldn't make it any worse).

Regards,

Anthony Liguori

             reply	other threads:[~2006-12-16 17:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-16 17:57 Anthony Liguori [this message]
2006-12-16 18:00 ` [Qemu-devel] [PATCH 1/3] Add unix domain socket character device Anthony Liguori
2006-12-16 18:04 ` [Qemu-devel] [PATCH 2/3] Add unix domain socket and interface restriction to VNC Anthony Liguori
2006-12-16 18:08 ` [Qemu-devel] [PATCH 3/3] Add daemonize option Anthony Liguori
2006-12-19  1:08   ` [Qemu-devel] [PATCH 3/3] [UPDATE] " Anthony Liguori

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=4584337D.6040706@cs.utexas.edu \
    --to=aliguori@cs.utexas.edu \
    --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).