From mboxrd@z Thu Jan 1 00:00:00 1970 From: Radim =?utf-8?B?S3LEjW3DocWZ?= Subject: Re: KVM_MAX_VCPU hard limit of 255 on x86 Date: Mon, 4 Apr 2016 17:17:19 +0200 Message-ID: <20160404151719.GA21537@potion.brq.redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Hardik H Bagdi , kvm@vger.kernel.org, Igor Mammedov To: Bandan Das Return-path: Received: from mx1.redhat.com ([209.132.183.28]:42514 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754533AbcDDPRY (ORCPT ); Mon, 4 Apr 2016 11:17:24 -0400 Content-Disposition: inline In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: 2016-04-01 17:55-0400, Bandan Das: > Hardik H Bagdi writes: >> Hello, >> >> For research, I am experimenting with increasing the number of VCPUs >> in the guest OS. >> I can increase the number of VCPUs till 255 in the guest OS but more >> than that results in the following error- > > Radim (Cced) might have more info but the short answer is that you > can't just simply increase the number. For >255, you need x2apic > with interrupt remapping which is still missing. Yes, interrupt remapping is being developed for the split irqchip. You could hack around that (we chose not to) so another blocker is that QEMU cannot handle more than 255 VCPUs, mainly because of its AML generator. Igor (Cc'd) knows more about the status of ACPI. (And firmware doesn't implement x2APIC, and other minor problems ...) All pieces should be in place within half a year, though. The next hard limit is ~2^20 or ~2^32.