From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] Re: cs:21768 causes guest spend more time on boot up Date: Mon, 19 Jul 2010 12:46:25 +0100 Message-ID: References: <20100719105548.GK13291@whitby.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20100719105548.GK13291@whitby.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: Tim Deegan , "Zhang, Yang Z" Cc: "Xu, Jiajun" , "Zhang, Jianwu" , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 19/07/2010 11:55, "Tim Deegan" wrote: >> Yes, I am still looking into it. I think the address of the table is >> not causing it, though, so it might take some time to find the real >> cause. > > The hang turned out to be entirely unrelated to the SMBIOS tables; the > xenbus client zeroes out teh xenstore ring entirely, and it looks like > newer dom0 xenbus backends can't handle that, so: What would it have to do with an in-kernel driver? Doesn't the comms page only get looked at by [o]xenstored? In which case we could fix them. -- Keir > hvmloader: don't zero out the xenbus page. > Not all xenbus backends accept that gracefully. Instead rely on the > xenbus frontend in the guest being able to start up with non-zero ring > offsets. > > Signed-off-by: Tim Deegan