All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: support for more than 32 VCPUs when migrating PVHVM guest
Date: Mon, 02 Feb 2015 12:03:28 +0100	[thread overview]
Message-ID: <8761bkwp6n.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <54CF5838.5020007@citrix.com> (Andrew Cooper's message of "Mon, 2 Feb 2015 10:58:00 +0000")

Andrew Cooper <andrew.cooper3@citrix.com> writes:

> On 02/02/15 10:47, Vitaly Kuznetsov wrote:
>> Hi Konrad,
>>
>> I just hit an issue with PVHVM guests after save/restore (or migration),
>> if a PVHVM guest has > 32 VCPUs it hangs. Turns out, you saw it almost a
>> year ago and even wrote patches to call VCPUOP_register_vcpu_info after
>> resume. Unfortunately these patches never made it to xen/kernel. Do you
>> have a plan to pick this up? What were the arguments against your
>> suggestion?
>
> 32 VCPUs is the legacy limit for HVM guests, but should not have any
> remaining artefacts these days.
>
> Do you know why the hang occurs?  I can't spot anything in the legacy
> migration code which would enforce such a limit.
>
> What is the subject of the thread you reference so I can search for it?
>

Sorry, I should have send the link:

http://lists.xen.org/archives/html/xen-devel/2014-04/msg00794.html

Konrad's patches:

http://lists.xen.org/archives/html/xen-devel/2014-04/msg01199.html

The issue is that we don't call VCPUOP_register_vcpu_info after
suspend/resume (or migration) and it is mandatory.

-- 
  Vitaly

  reply	other threads:[~2015-02-02 11:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 10:47 support for more than 32 VCPUs when migrating PVHVM guest Vitaly Kuznetsov
2015-02-02 10:58 ` Andrew Cooper
2015-02-02 11:03   ` Vitaly Kuznetsov [this message]
2015-02-02 14:21     ` Konrad Rzeszutek Wilk
2015-02-03  9:38       ` Vitaly Kuznetsov

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=8761bkwp6n.fsf@vitty.brq.redhat.com \
    --to=vkuznets@redhat.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.