Skip to content

Add options to make writing a front end easier

Anthony Liguori qemu-devel 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3Add unix domain socket character deviceqemu-doc.texi qemu_socket.h vl.c+103 -200 replies
2/3Add unix domain socket and interface restriction to VNCqemu-doc.texi vl.c vl.h +1 more+85 -480 replies
3/3Add daemonize optionqemu-doc.texi vl.c+87 -00 replies
3/3Add daemonize optionqemu-doc.texi vl.c+88 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [Qemu-devel] [PATCH 0/3] Add options to make writing a front end easier

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