From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: Re: [PATCH 0 of 1] Deal with Serial Over LAN (SOL) IPMI interfaces. Date: Tue, 15 Dec 2009 00:48:19 +0200 Message-ID: <20091214224819.GS16033@reaktio.net> References: <20091214163609.GA26474@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20091214163609.GA26474@phenom.dumpdata.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: Konrad Rzeszutek Wilk Cc: "Gary.Grebus@oracle.com" , "xen-devel@lists.xensource.com" , Keir Fraser List-Id: xen-devel@lists.xenproject.org On Mon, Dec 14, 2009 at 11:36:09AM -0500, Konrad Rzeszutek Wilk wrote: > On Mon, Dec 14, 2009 at 04:38:33PM +0000, Keir Fraser wrote: > > On 14/12/2009 15:10, "Konrad Rzeszutek Wilk" wrote: > > > > > During the testing of Intel blades we found that the Serial Over LAN > > > does not generate IRQs that well. Gary came up with a patch that > > > figures out if it needs to poll or just work as before (IRQ). The benefit > > > of this patch is that you don't need to do: > > > > > > com1=115200,8n1,0 > > > > > > but instead can just do com1=115200,8n1 which is great in the field > > > where you don't want the bootup file to change. > > > > Kinda gross, and I'm not sure it's straightforward enough that I trust it on > > all systems that currently work fine (vast majority). I *might* consider it > > We (Virtual Iron) were confident enough to make it turned on in our production builds. > I do not have the list of machines we certified anymore (the web-page went > bye-bye) so I can't give you the test scope data :-( > Not sure if the Virtual Iron HCL helps.. it seems to be here: http://www.oracle.com/technology/products/vm/virtual-iron-documentation.html -- Pasi