From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: CPU hot-plugging interface Date: Thu, 10 Dec 2009 14:55:03 +0100 Message-ID: <4B20FDB7.1050203@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit To: kvm Return-path: Received: from goliath.siemens.de ([192.35.17.28]:19467 "EHLO goliath.siemens.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751487AbZLJNy6 (ORCPT ); Thu, 10 Dec 2009 08:54:58 -0500 Received: from mail2.siemens.de (localhost [127.0.0.1]) by goliath.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id nBADt354007447 for ; Thu, 10 Dec 2009 14:55:03 +0100 Received: from [139.25.109.167] (mchn012c.mchp.siemens.de [139.25.109.167] (may be forged)) by mail2.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id nBADt3Zh024099 for ; Thu, 10 Dec 2009 14:55:03 +0100 Sender: kvm-owner@vger.kernel.org List-ID: Hi, based on my naive and unsuccessful tests to add a CPU that was not declared on qemu startup via "-smp", I assume that the monitor command "cpu_set" lacks some range check, right? Or is it allowed to add CPUs dynamically that way? Then there would be some bug in qemu-kvm's (next branch) CPU management. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux