From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: xenbus and the message of doom Date: Fri, 16 Dec 2011 18:01:54 +0100 Message-ID: <20111216170154.GA25941@aepfle.de> References: <4EEA4877.8010307@canonical.com> <1323982417.20936.898.camel@dagon.hellion.org.uk> <4EEB0CE9.4040405@canonical.com> <1324027918.20077.530.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1324027918.20077.530.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: "xen-devel@lists.xensource.com" , Stefan Bader , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On Fri, Dec 16, Ian Campbell wrote: > I think (or hope!) that Olaf tested with the most recent version of C > xenstored which did not support this new message and so I presume that > it correct returns an error for an unknown message but that doesn't help > us with the older C xenstored which you have. I just checked a SLES10SP3 host (xen 3.2.3) with a SLES11SP2 hvm guest and it booted fine. So I suspect EC2 is broken in this case. Olaf