From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vitaly Kuznetsov Subject: support for more than 32 VCPUs when migrating PVHVM guest Date: Mon, 02 Feb 2015 11:47:56 +0100 Message-ID: <87k300wpwj.fsf@vitty.brq.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIEXz-0000Cl-IL for xen-devel@lists.xenproject.org; Mon, 02 Feb 2015 10:48:03 +0000 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: xen-devel@lists.xenproject.org List-Id: xen-devel@lists.xenproject.org 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? Thanks, -- Vitaly