From: Ian Campbell <ian.campbell@citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>, Wei Liu <wei.liu2@citrix.com>
Subject: Re: RFC: PV vfb's and the handling of global vnc options
Date: Wed, 11 Nov 2015 10:28:00 +0000 [thread overview]
Message-ID: <1447237680.11601.3.camel@citrix.com> (raw)
In-Reply-To: <CAFLBxZZia83BH=Ztf2TOSydMHCiHKREbaBzdU5_qHpz87PY38A@mail.gmail.com>
On Mon, 2015-11-09 at 15:03 +0000, George Dunlap wrote:
Adding other tools maintainers.
> So I had a user report that he couldn't get the vnclisten option to
> work. It turns out he was using a PV guest, and had the following in
> his config file:
>
> vfb=[ 'type=vnc' ]
> vnclisten='0.0.0.0'
>
> After digging around in the code, it turns out that the following is
> accepted for PV guests:
>
> vnc=1
> vnclisten='0.0.0.0'
>
> ...on the condition that there be *no* vfb option. If you set the vfb
> option, then the top-level vnc entries are completely ignored.
>
> The following also works (as one might expect):
>
> vfb=[ 'type=vnc,vnclisten=0.0.0.0' ]
>
> The man page is a bit unclear here; it says:
>
> If "Emulated VGA Graphics Device" options are used in a PV guest
> configuration, xl will pick up vnc, vnclisten, vncpasswd, vncdisplay,
> vncunused, sdl, opengl and keymap to construct paravirtual framebuffer
> device for the guest.
>
> I see two options:
>
> 1. Make vfb take defaults from the top-level vnc options
>
> 2. Clarify the man page to make it clear that top-level vnc options
> will only have an effect if no vfb is specified.
>
> I'm of two minds which one is best. At the moment I'm leaning towards
> #2, possibly adding a warning if it finds both vfb and toplevel vnc
> options, saying that it's ignoring the second.
One problem with #1 is that for some options (vncdisplay) having a global
default for potentially multiple vfb=[] stanzas would be wrong and a bit
confusing (although perhaps no more so than the current behaviour).
I suppose you could limit some or (better) all of the globals to only being
used for the first entry in the array (but I bet the code gets quite funky
in that case).
You'd probably want the warning you mention in #2 even in the #1 case.
Like you I'm not really sure.
A third option just to muddy the waters:
3. If any global options are given then a new vfb is pushed onto the front
of any array given by vfb=[], i.e. those vfbs implicitly go from devices
0..N to 1..N+1.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2015-11-11 10:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 15:03 RFC: PV vfb's and the handling of global vnc options George Dunlap
2015-11-09 15:51 ` Konrad Rzeszutek Wilk
2015-11-11 10:28 ` Ian Campbell [this message]
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=1447237680.11601.3.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.