Xen devel - Jul 2008 - [PATCH] Allow xm to spawn vnc viewer

The new merged qemu no longer has the ability to spawn a vnc viewer
process in the bowels of the xend/qemu stack.  In this patch we
provide support for this use case in a different manner - one more
akin to the mechanism used for `xm console'' and `xm create
-c''.

We introduce new xm options:
   xm create --vncviewer [--vncviewer-autopass]
   xm vncviewer [--vncviewer-autopass]

These spawn a VNC viewer, obtaining the relevant information
(including the port number and if you tell it your viewer supports it
the password to use) directly from xenstore.

Like xm console it waits in the foreground for the vnc port to become
available; the timeout case isn''t handled as well as it might be - it
just causes the whole program (xm) to die with `Alarm clock'' but this
is difficult to deal with given the current structure of the xs Python
lowlevel interface, which doesn''t provide a timeout on the call to
wait for a xenstore watch.

Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

I wrote:
> The new merged qemu no longer has the ability to spawn a vnc viewer
> process in the bowels of the xend/qemu stack.  In this patch we
> provide support for this use case in a different manner - one more
> akin to the mechanism used for `xm console'' and `xm create
-c''.
I see that I made a small mistake in this patch in the exception
handling, which tends to cause the viewer to inherit a signal handler.

The attached patch fixes this up.

Apologies,
Ian.



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel