From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MPz22-0007zv-Ct for qemu-devel@nongnu.org; Sun, 12 Jul 2009 09:23:54 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MPz1x-0007zi-NF for qemu-devel@nongnu.org; Sun, 12 Jul 2009 09:23:53 -0400 Received: from [199.232.76.173] (port=39351 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MPz1x-0007zf-HJ for qemu-devel@nongnu.org; Sun, 12 Jul 2009 09:23:49 -0400 Received: from mx20.gnu.org ([199.232.41.8]:39292) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MPz1x-0005SP-6b for qemu-devel@nongnu.org; Sun, 12 Jul 2009 09:23:49 -0400 Received: from an-out-0708.google.com ([209.85.132.242]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MPz1w-0005xV-NR for qemu-devel@nongnu.org; Sun, 12 Jul 2009 09:23:48 -0400 Received: by an-out-0708.google.com with SMTP id c38so906307ana.37 for ; Sun, 12 Jul 2009 06:23:47 -0700 (PDT) Message-ID: <4A59E3E1.30406@codemonkey.ws> Date: Sun, 12 Jul 2009 08:23:45 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [patch 2/2] QEMU BOCHS bios patches to use maxcpus value. References: <20090624083512.766907560@sgi.com> <20090624083725.264462154@sgi.com> <4A5667D2.2020404@codemonkey.ws> <4A59AF3C.8030005@redhat.com> In-Reply-To: <4A59AF3C.8030005@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Anthony Liguori , Jes Sorensen , qemu-devel@nongnu.org Avi Kivity wrote: > On 07/10/2009 12:57 AM, Anthony Liguori wrote: >> These changes make my Ubuntu server guest very unhappy. I get a >> bunch of messages about "Not responding." on startup. >> >> If nothing else, maxcpus ==smp_cpus under QEMU because we don't do >> CPU hotplug (and I don't think we should). >> > > Why shouldn't we do cpu hotplug? I don't think we should do cpu hotplug via ACPI. I don't think ACPI actually models CPU hotplug and the fact that this works with Linux in KVM is a happy accident. VMware only supports CPU hotplug for Windows 7/2k8 guests so I'm assuming their using Viridian PV extensions to do it. I think we should go the PV route for Linux too. I'd rather see us create all vcpu threads at once and then let the guest offline each vcpu via a PV notification. I don't see a lot of value in spawning/terminating vcpu threads dynamically and it adds an awful lot of complexity. There's very little overhead to an idle thread. Regards, Anthony Liguori