xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Roger Pau Monne <roger.pau@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Valtteri Kiviniemi <kiviniemi.valtteri@gmail.com>,
	Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH V3] libxl: write IO ABI for disk frontends
Date: Fri, 17 May 2013 10:18:05 +0100	[thread overview]
Message-ID: <5195F5CD.1040908@eu.citrix.com> (raw)
In-Reply-To: <20130517090726.GA14853@zion.uk.xensource.com>

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

  reply	other threads:[~2013-05-17  9:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-25 21:36 [PATCH V3] libxl: write IO ABI for disk frontends Wei Liu
2013-04-26  9:18 ` Ian Campbell
2013-04-26  9:44   ` Wei Liu
2013-04-26  9:52     ` Ian Campbell
2013-04-26 10:11       ` Wei Liu
2013-04-26 10:22         ` Ian Campbell
2013-04-26 11:01           ` George Dunlap
2013-04-26 15:34             ` Ian Campbell
2013-05-16 12:43               ` Valtteri Kiviniemi
2013-05-16 13:33                 ` Wei Liu
2013-05-16 14:01                   ` Valtteri Kiviniemi
2013-05-17  7:36                     ` Valtteri Kiviniemi
2013-05-17  8:33                       ` Wei Liu
2013-05-17  8:56                         ` George Dunlap
2013-05-17  9:07                           ` Wei Liu
2013-05-17  9:18                             ` George Dunlap [this message]
2013-05-17  9:22                               ` Wei Liu
2013-05-17 10:53                                 ` Valtteri Kiviniemi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5195F5CD.1040908@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=kiviniemi.valtteri@gmail.com \
    --cc=roger.pau@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).