From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: pvops dom0 work roadmap Date: Wed, 19 Aug 2009 09:19:48 -0700 Message-ID: <4A8C2624.8090900@goop.org> References: <4A8AF65A.2040904@goop.org> <20090818200718.GD19938@edu.joroinen.fi> <4A8B0B1A.80406@goop.org> <20090819132609.GA21730@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20090819132609.GA21730@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: Xen-devel List-Id: xen-devel@lists.xenproject.org On 08/19/09 06:26, Konrad Rzeszutek Wilk wrote: > I found three issues with 2.6.30-rc3-tip (xen-tip/master): > - if you don't have CONFIG_HIBERNATION set it hangs at startup on the VGA init code (right after "about to get started"). I played > with turning CONFIG_SWAP off, which in turn unselects _HIBERNATION off. > Oh, interesting. > - if you set CONFIG_STACKPROTECTOR=y you get a nice big page fault right at the startup (doesn't even get to 'about to get started' message). > I have a tentative fix for this in rebase/master. > - poweroff doesn't turn the machine off (but I haven't verified whether the machine normally powers off with a non-Xen 2.6.30-rc3-tip kernel > so this might be an operator errro). > I've found that's fairly erratic even on native. But I guess its likely to be something to do with ACPI. Though I would have thought that Xen would have the responsibility for poweroff when the dom0 kernel terminates itself. I think you should continue using rebase/master rather than xen-tip/. J