From: Ian Campbell <Ian.Campbell@citrix.com>
To: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"JBeulich@novell.com" <JBeulich@novell.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] xen/xenbus: Add quirk to deal with misconfigured backends.
Date: Thu, 22 Mar 2012 10:52:26 +0000 [thread overview]
Message-ID: <1332413546.8817.64.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1203221040030.15151@kaball-desktop>
On Thu, 2012-03-22 at 10:44 +0000, Stefano Stabellini wrote:
> On Thu, 22 Mar 2012, Konrad Rzeszutek Wilk wrote:
> > A rather annoying and common case is when booting a PVonHVM guest
> > and exposing the PV KBD and PV VFB - as both of those do not
> > make any sense. The HVM guest is using the VGA driver and the emulated
> > keyboard for this. So we provide a very basic quirk framework
> > (can be expanded in the future) to not wait for 6 minutes for those devices
> > to initialize - they never wont.
> >
> > To trigger this, put this in your guest config:
> >
> > vfb = [ 'vnc=1, vnclisten=0.0.0.0 ,vncunused=1']
> >
> > instead of this:
> > vnc=1
> > vnclisten="0.0.0.0"
>
> While I do understand the issue you are trying to solve, it actually
> makes sense to have PV KBD (and PV VFB maybe in the future) in a PVonHVM
> guest. In particular PV KVB is already enabled in upstream QEMU for
> PVonHVM guests because it allows users to have a keyboard and mouse
> without USB emulation, that requires lots of wakes up in QEMU.
>
> Maybe we could just reduce the timeout in general for all the PV
> devices? After all, why are we waiting 6 minutes? I could understand 6
> seconds, but 6 minutes seem really too much.
This was increased based on empirical evidence, way back (circa
150:09c88868e344 in linux-2.6.18-xen.hg)
It really can happen when starting lots of guests on a heavily loaded
dom0 that you timeout when connecting devices, at which point the guest
fails to boot if it happened to contain the root filesystem.
Maybe a halfway house would be to wait a the longer time for more
critical devices (like disks and nics)?
Ian.
next prev parent reply other threads:[~2012-03-22 10:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 2:59 Konrad Rzeszutek Wilk
2012-03-22 10:44 ` Stefano Stabellini
2012-03-22 10:52 ` Ian Campbell [this message]
2012-03-22 13:21 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-03-22 15:16 ` Stefano Stabellini
2012-03-28 19:45 ` Konrad Rzeszutek Wilk
2012-03-29 11:16 ` Stefano Stabellini
2012-04-18 18:19 Konrad Rzeszutek Wilk
2012-04-19 11:37 ` Stefano Stabellini
2012-04-19 15:33 ` Konrad Rzeszutek Wilk
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=1332413546.8817.64.camel@zakaz.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@novell.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®