linux-kernel - Re: [Xen-devel] [PATCH] xen/xenbus: Add quirk to deal with misconfigured backends.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120322132102.GA22545@phenom.dumpdata.com>
Date:	Thu, 22 Mar 2012 09:21:02 -0400
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	Ian Campbell <Ian.Campbell@...rix.com>
Cc:	Stefano Stabellini <Stefano.Stabellini@...citrix.com>,
	"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [Xen-devel] [PATCH] xen/xenbus: Add quirk to deal with
 misconfigured backends.

On Thu, Mar 22, 2012 at 10:52:26AM +0000, Ian Campbell wrote:
> 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

How about looking for a particular Xen version? The patch
could check for anything less than 4.2 (does 4.2 use that version of
QEMU that has this implemented?). I can't find any way to get the QEMU
version from within the guest - DMI reports:

DMI: Xen HVM domU, BIOS 4.1-120322 03/22/2012

> > 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.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@...ts.xen.org
> http://lists.xen.org/xen-devel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/