From: Ankur Arora <ankur.a.arora@oracle.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Olaf Hering <olaf@aepfle.de>
Cc: xen-devel@lists.xen.org
Subject: Re: live migration of HVM domUs with more than 32vcpus fails
Date: Fri, 23 Jun 2017 15:27:00 -0700 [thread overview]
Message-ID: <2483a721-ecc6-b066-55f5-fd387a772c52@oracle.com> (raw)
In-Reply-To: <9754827a-b4f3-1bb3-d527-cb3907dded5d@oracle.com>
On 2017-06-23 10:03 AM, Boris Ostrovsky wrote:
>
>
> On 06/23/2017 12:54 PM, Olaf Hering wrote:
>> On Thu, Jun 22, Boris Ostrovsky wrote:
>>
>>> They are queued for 4.13.
>>> git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-4.13
>>
>> This works for me. Thanks.
>>
>> I assume there is no ready-to-pull variant for linux-4.4.x?
>> nm.
>
>
> Not that I am aware of. Unless Ankur backported them to OL which is
> (loosely) based on 4.1.
There was an earlier version of this patch by Konrad -- which takes
care of the migration failure: https://patchwork.kernel.org/patch/6768031/
Olaf, can you try this out?
Thanks
Ankur
>
>
> -boris
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-06-23 22:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 13:57 live migration of HVM domUs with more than 32vcpus fails Olaf Hering
2017-06-22 14:34 ` Konrad Rzeszutek Wilk
2017-06-22 14:39 ` Olaf Hering
2017-06-22 14:54 ` Boris Ostrovsky
2017-06-23 16:54 ` Olaf Hering
2017-06-23 17:03 ` Boris Ostrovsky
2017-06-23 19:40 ` Ankur Arora
2017-06-23 22:27 ` Ankur Arora [this message]
2017-06-26 7:08 ` Olaf Hering
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=2483a721-ecc6-b066-55f5-fd387a772c52@oracle.com \
--to=ankur.a.arora@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=olaf@aepfle.de \
--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).