From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 00FB4C43464 for ; Mon, 21 Sep 2020 08:31:15 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 680FB2076B for ; Mon, 21 Sep 2020 08:31:13 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="Kyh7A9lj" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 680FB2076B Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:47452 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kKHE8-0004Hg-Ft for qemu-devel@archiver.kernel.org; Mon, 21 Sep 2020 04:31:12 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:52702) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kKHD0-0003kp-Pb for qemu-devel@nongnu.org; Mon, 21 Sep 2020 04:30:02 -0400 Received: from us-smtp-2.mimecast.com ([207.211.31.81]:32388 helo=us-smtp-delivery-1.mimecast.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.90_1) (envelope-from ) id 1kKHCy-0002EI-Ta for qemu-devel@nongnu.org; Mon, 21 Sep 2020 04:30:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1600676999; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=fc9p6xiRkNInLlDy9qdxPXsoGigIkO7o5asnnXHTyHk=; b=Kyh7A9lj0z5+l1IYYchPdR/ljgbbdHrg3sOZdNeX5do1RXa4IOz96WFjwjrWRwU+g17jLs SsnY+SbSFcUpF/bm1UZPA1xlZbH3gWHxm2Sz6BhTxlTx37Cmp6z3BevIhCQcheQ69EIiNL GFtC3cUa8KEafcB14amJi5NE1wRjQIY= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-175-k9_wKUGAP1iWeWB4UQqX0A-1; Mon, 21 Sep 2020 04:29:55 -0400 X-MC-Unique: k9_wKUGAP1iWeWB4UQqX0A-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 975596414A; Mon, 21 Sep 2020 08:29:54 +0000 (UTC) Received: from redhat.com (ovpn-113-113.ams2.redhat.com [10.36.113.113]) by smtp.corp.redhat.com (Postfix) with ESMTPS id BBCCD55781; Mon, 21 Sep 2020 08:29:53 +0000 (UTC) Date: Mon, 21 Sep 2020 09:29:50 +0100 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: Peter Lieven Subject: Re: Limiting per vCPU Usage Message-ID: <20200921082950.GF1942072@redhat.com> References: <68336702-cedc-dc38-3d18-d153cd7652dd@kamp.de> MIME-Version: 1.0 In-Reply-To: <68336702-cedc-dc38-3d18-d153cd7652dd@kamp.de> User-Agent: Mutt/1.14.6 (2020-07-11) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=berrange@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Received-SPF: pass client-ip=207.211.31.81; envelope-from=berrange@redhat.com; helo=us-smtp-delivery-1.mimecast.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/09/21 03:43:14 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: -35 X-Spam_score: -3.6 X-Spam_bar: --- X-Spam_report: (-3.6 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.501, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Cc: "qemu-devel@nongnu.org" Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Sun, Sep 20, 2020 at 10:24:41PM +0200, Peter Lieven wrote: > Hi Qemu folks, > > > is there a BCP to limit just the maximum usage of a virtual (KVM) cpu? > > I know that there are many approaches, but as far as I know they all limit the complete qemu process which is far more > > than just the virtual CPUs. > > Is it possible to limit just the vCPU threads and leave threads that > handle the monitor, vnc, qmp, iothreads, storage backend etc. Libvirt uses cgroups to achieve what you describe. A cgroup for the QEMU process as a whole, then create child cgroups, one for each vCPUs, and a further one for non-vCPU threads. CPU limits are then applied on the child cgroups. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|