From: Matt Wilson <msw@amazon.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] hvc_xen: introduce HVC_XEN_FRONTEND
Date: Tue, 13 Mar 2012 16:34:35 -0700 [thread overview]
Message-ID: <20120313233435.GC6940@US-SEA-R8XVZTX> (raw)
In-Reply-To: <20120313162944.GC19228@phenom.dumpdata.com>
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
prev parent reply other threads:[~2012-03-13 23:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 11:30 [PATCH] hvc_xen: introduce HVC_XEN_FRONTEND Stefano Stabellini
2012-02-21 14:43 ` Konrad Rzeszutek Wilk
2012-03-04 16:06 ` Konrad Rzeszutek Wilk
2012-03-05 22:45 ` Stefano Stabellini
2012-03-13 16:29 ` Konrad Rzeszutek Wilk
2012-03-13 18:30 ` Stefano Stabellini
2012-03-13 23:20 ` Konrad Rzeszutek Wilk
2012-03-13 23:34 ` Matt Wilson [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=20120313233435.GC6940@US-SEA-R8XVZTX \
--to=msw@amazon.com \
--cc=konrad.wilk@oracle.com \
--cc=stefano.stabellini@eu.citrix.com \
--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 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.