From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47834) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bLUYK-0000k2-0Z for qemu-devel@nongnu.org; Fri, 08 Jul 2016 08:06:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bLUYE-0006XR-Sh for qemu-devel@nongnu.org; Fri, 08 Jul 2016 08:06:38 -0400 Received: from mx1.redhat.com ([209.132.183.28]:33997) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bLUYE-0006X1-Mv for qemu-devel@nongnu.org; Fri, 08 Jul 2016 08:06:34 -0400 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 71C9B80085 for ; Fri, 8 Jul 2016 12:06:33 +0000 (UTC) Date: Fri, 8 Jul 2016 14:06:31 +0200 From: Igor Mammedov Message-ID: <20160708140631.6562c90c@nial.brq.redhat.com> In-Reply-To: <20160708074600.GB78006@andariel.pipo.sk> References: <417b83d0e074e2004aa35bef337d32ac2c89f559.1467904342.git.pkrempa@redhat.com> <20160708122308.1f43b56a@voom.fritz.box> <20160708074600.GB78006@andariel.pipo.sk> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH 2/2] numa: Add node_id data in query-hotpluggable-cpus List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Krempa Cc: David Gibson , qemu-devel@nongnu.org On Fri, 8 Jul 2016 09:46:00 +0200 Peter Krempa wrote: [...] > Note: For libvirt it's a no-go to start a throwaway qemu process just to > query the information and thus it's desired to have a way to configure > all this without the need to query with a specific machine > type/topology. Is it no-go to start throwaway qemu on the new domain creation time? i.e. user create a new domain, with specific -machine/-smp layout libvirt stores results of query-hotpluggable-cpus and then allow user in (eg)virt-manager to pick which CPUs are enabled and optionally to which numa nodes they are mapped.