Xen devel - Jan 2007 - [PATCH][PVFB][TOOLS] Update xmdomain.cfg.pod.5

Document vfb configuration.

Signed-off-by: Markus Armbruster <armbru@redhat.com>


diff -r 887168cf7532 docs/man/xmdomain.cfg.pod.5
--- a/docs/man/xmdomain.cfg.pod.5	Mon Jan 15 18:09:16 2007 +0000
+++ b/docs/man/xmdomain.cfg.pod.5	Tue Jan 16 19:03:55 2007 +0100
@@ -135,6 +135,55 @@ one will be randomly chosen by xen with 
 
 =back
 
+=item B<vfb>
+
+A virtual frame buffer stanza in the form:
+
+    vfb = [ "stanza" ]
+
+The stanza specifies a set of I<name = value> options separated by
+commas, in the form: "name1=value1, name2=value2, ..."
+
+B<OPTIONS>
+
+=over 4
+
+=item I<type>
+
+There are currently two valid options: I<vnc> starts a VNC server that
+lets you connect an external VNC viewer, and I<sdl> starts an internal
+viewer.
+
+=item I<vncdisplay>
+
+The VNC display number to use, defaults to the domain ID.  The
+VNC server listens on port 5900 + display number.
+
+=item I<vnclisten>
+
+The listening address for the VNC server, default 127.0.0.1.
+
+=item I<vncunused>
+
+If non-zero, the VNC server listens on the first unused port above
+5900.
+
+=item I<vncpasswd>
+
+Overrides the XenD configured default password.
+
+=item I<display>
+
+Display to use for the internal viewer, defaults to environment
+variable I<DISPLAY>.
+
+=item I<xauthority>
+
+Authority file to use for the internal viewer, defaults to environment
+variable I<XAUTHORITY>.
+
+=back
+
 =back
 
 =head1 ADDITIONAL OPTIONS

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

Are there any plans to unify configuration for the vfb and the HVM virtual 
display?  They both have a similar set of options, so it would be nice if 
they could be tied together at the UI level.

Moreover, unifying the config options would make it somewhat straightforward 
to tweak the system to allow booting a domain in either HVM or paravirt 
mode - which would be cool (imagine a user of an HVM domain
"upgrading" to
PV, or a PV domain user who needed full platform emulation for some testing).

Cheers,
Mark

On Tuesday 16 January 2007 18:15, Markus Armbruster
wrote:
> Document vfb configuration.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
>
>
> diff -r 887168cf7532 docs/man/xmdomain.cfg.pod.5
> --- a/docs/man/xmdomain.cfg.pod.5	Mon Jan 15 18:09:16 2007 +0000
> +++ b/docs/man/xmdomain.cfg.pod.5	Tue Jan 16 19:03:55 2007 +0100
> @@ -135,6 +135,55 @@ one will be randomly chosen by xen with
>
>  =back
>
> +=item B<vfb>
> +
> +A virtual frame buffer stanza in the form:
> +
> +    vfb = [ "stanza" ]
> +
> +The stanza specifies a set of I<name = value> options separated by
> +commas, in the form: "name1=value1, name2=value2, ..."
> +
> +B<OPTIONS>
> +
> +=over 4
> +
> +=item I<type>
> +
> +There are currently two valid options: I<vnc> starts a VNC server
that
> +lets you connect an external VNC viewer, and I<sdl> starts an
internal
> +viewer.
> +
> +=item I<vncdisplay>
> +
> +The VNC display number to use, defaults to the domain ID.  The
> +VNC server listens on port 5900 + display number.
> +
> +=item I<vnclisten>
> +
> +The listening address for the VNC server, default 127.0.0.1.
> +
> +=item I<vncunused>
> +
> +If non-zero, the VNC server listens on the first unused port above
> +5900.
> +
> +=item I<vncpasswd>
> +
> +Overrides the XenD configured default password.
> +
> +=item I<display>
> +
> +Display to use for the internal viewer, defaults to environment
> +variable I<DISPLAY>.
> +
> +=item I<xauthority>
> +
> +Authority file to use for the internal viewer, defaults to environment
> +variable I<XAUTHORITY>.
> +
> +=back
> +
>  =back
>
>  =head1 ADDITIONAL OPTIONS
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

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