From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: [PATCH V3] libxl: write IO ABI for disk frontends Date: Fri, 17 May 2013 10:18:05 +0100 Message-ID: <5195F5CD.1040908@eu.citrix.com> References: <20130426101137.GI27096@zion.uk.xensource.com> <1366971779.3142.59.camel@zakaz.uk.xensource.com> <517A5E8F.6000406@eu.citrix.com> <1366990467.3142.153.camel@zakaz.uk.xensource.com> <20130516133325.GA10146@zion.uk.xensource.com> <20130517083335.GB14401@zion.uk.xensource.com> <5195F0C6.2080903@eu.citrix.com> <20130517090726.GA14853@zion.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20130517090726.GA14853@zion.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Wei Liu Cc: Roger Pau Monne , "xen-devel@lists.xen.org" , Valtteri Kiviniemi , Ian Campbell List-Id: xen-devel@lists.xenproject.org On 05/17/2013 10:07 AM, Wei Liu wrote: > On Fri, May 17, 2013 at 09:56:38AM +0100, George Dunlap wrote: > [...] >>>> with Xen 4.3-rc1 and with xl tool stack. So the patch is working as >>>> intented. I also tested various xl commands and functions with my legacy >>>> domU and all of them seemed to be working (reboot, pause, unpause, shutdown >>> >>> Thanks for testing. >>> >>>> etc.) except suspend. Suspend crashes with "Internal error" and the guest >>>> console shows error message "Can't suspend SMP guests without >>>> CONFIG_HOTPLUG_CPU". >>>> >>>> 2.6.16.33 kernel does not seem to have cpu hotplug support, or then I just >>>> can find it in the kernel menuconfig. >>>> >>> >>> George, should this one be added to your list? (Just found out you're >>> already in CC ;-) ) >> >> ...add "Linux 2.6.16.33 HOTPLUG config option is hard to find" to my >> list? I'm not sure that would be a 4.3 release blocker... :-) >> > > I mean 'xl suspend' crashes with "Internal Error". Should not be a > blocker, but at least worthy of making its way to known issues list? (if > there is one). Well if it *fails* with "Internal Error" because there's an internal error, I'm not sure that's a bug. :-) If Valtteri wants to post a proper bug report, with the listed output and a suggestion of what would be a better output, we can consider putting it on the list. -George