From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: RFC: PV vfb's and the handling of global vnc options
Date: Mon, 9 Nov 2015 10:51:49 -0500 [thread overview]
Message-ID: <20151109155149.GA8121@char.us.oracle.com> (raw)
In-Reply-To: <CAFLBxZZia83BH=Ztf2TOSydMHCiHKREbaBzdU5_qHpz87PY38A@mail.gmail.com>
On Mon, Nov 09, 2015 at 03:03:17PM +0000, George Dunlap wrote:
> 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.
Ha!
>
> 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
Keep in mind that for HVM guests we would want only the 'vnc' options
from the 'vfb'. That is because by default we boot with 'vga=cirrus'
and with both backends (VGA VNC and PV FB) the guest gets mighty
confused during bootup. That is - the initial 'text' console goes
to the PV FB and the KDM/GDM goes in the VGA VNC. But the 'PV FB'
is the first one and most tools except only one VNC backend.
>
> 2. Clarify the man page to make it clear that top-level vnc options
> will only have an effect if no vfb is specified.
The manpage was probably constructed during the reign of Xend. In
which you could have both options (vfb= and vnc=) .. and Xend would
happily expose in Xenstore the pvfb keys with the old QEMU
(which would default to the VGA for HVM guests). Which meant that the
guest would spend 30 seconds trying to use the PVFB backend driver :-(
>
> 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.
>
> Any opinions?
I like #1 as it would make it easy to use the old style Xend
configuration files doing the right thing.
With PVH and with 'qemu=none'..you would want the PVFB, if the
user used 'vnc' or 'vfb'.
>
> -George
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-11-09 15:51 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 [this message]
2015-11-11 10:28 ` Ian Campbell
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=20151109155149.GA8121@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=George.Dunlap@eu.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.