From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Wilson Subject: Re: [PATCH] hvc_xen: introduce HVC_XEN_FRONTEND Date: Tue, 13 Mar 2012 16:34:35 -0700 Message-ID: <20120313233435.GC6940@US-SEA-R8XVZTX> References: <1329823842-10085-1-git-send-email-stefano.stabellini@eu.citrix.com> <20120304160635.GA449@phenom.dumpdata.com> <20120313162944.GC19228@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20120313162944.GC19228@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: "xen-devel@lists.xensource.com" , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On Tue, Mar 13, 2012 at 09:29:44AM -0700, Konrad Rzeszutek Wilk wrote: > On Mon, Mar 05, 2012 at 10:45:33PM +0000, Stefano Stabellini wrote: > > Only xen installations supporting vfb and qemu as a console backend are > > susceptible, so Amazon should be safe because I don't think they use any > > of them. > > I think they use the normal xenconsole .. but then the patch to return 0 > would work .. but upset future version of QEMU (or is it the other way > around). There are HVM instance types in EC2: Cluster Compute (HPC cc1.*, cg1.* and cc2.* instances) and all instances running Windows. When booting Linux on a Cluster Compute instance you may see: [ 1.887398] XENBUS: Device with no driver: device/vfb/0 [ 1.890850] XENBUS: Device with no driver: device/console/0 It's not safe to assume anything in regard to breaking compatibility with older versions of Xen or QEMU. Matt