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=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 755FFC433B4 for ; Thu, 22 Apr 2021 06:28:02 +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 C746D6144D for ; Thu, 22 Apr 2021 06:28:01 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C746D6144D Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=bugs.launchpad.net Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:53278 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lZSoi-0001qz-Ow for qemu-devel@archiver.kernel.org; Thu, 22 Apr 2021 02:28:00 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:45474) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lZSmk-0000T4-PY for qemu-devel@nongnu.org; Thu, 22 Apr 2021 02:26:00 -0400 Received: from indium.canonical.com ([91.189.90.7]:57144) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lZSmh-0007Ae-SV for qemu-devel@nongnu.org; Thu, 22 Apr 2021 02:25:58 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1lZSmf-0007nE-Bn for ; Thu, 22 Apr 2021 06:25:53 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 57A762E815F for ; Thu, 22 Apr 2021 06:25:53 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Thu, 22 Apr 2021 06:16:47 -0000 From: Thomas Huth <1829696@bugs.launchpad.net> To: qemu-devel@nongnu.org X-Launchpad-Notification-Type: bug X-Launchpad-Bug: product=qemu; status=Incomplete; importance=Undecided; assignee=None; X-Launchpad-Bug-Tags: centos clock qemu-kvm redhat X-Launchpad-Bug-Information-Type: Public X-Launchpad-Bug-Private: no X-Launchpad-Bug-Security-Vulnerability: no X-Launchpad-Bug-Commenters: berrange qianxi416 th-huth X-Launchpad-Bug-Reporter: qianxi (qianxi416) X-Launchpad-Bug-Modifier: Thomas Huth (th-huth) References: <155832450585.26079.9550620234862222790.malonedeb@soybean.canonical.com> Message-Id: <161907220737.31825.14180852222339531413.malone@soybean.canonical.com> Subject: [Bug 1829696] Re: qemu-kvm takes 100% CPU when running redhat/centos 7.6 guest VM OS X-Launchpad-Message-Rationale: Subscriber (QEMU) @qemu-devel-ml X-Launchpad-Message-For: qemu-devel-ml Precedence: bulk X-Generated-By: Launchpad (canonical.com); Revision="1552fceb1603b3da6cfa437575d9c9fc4b2e683a"; Instance="production" X-Launchpad-Hash: 54760ec3232b11c1f6928d8dd90bd2bdec608a13 Received-SPF: none client-ip=91.189.90.7; envelope-from=bounces@canonical.com; helo=indium.canonical.com X-Spam_score_int: -65 X-Spam_score: -6.6 X-Spam_bar: ------ X-Spam_report: (-6.6 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Bug 1829696 <1829696@bugs.launchpad.net> Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now. If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or please mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience. ** Changed in: qemu Status: New =3D> Incomplete -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1829696 Title: qemu-kvm takes 100% CPU when running redhat/centos 7.6 guest VM OS Status in QEMU: Incomplete Bug description: Description =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D When running redhat or centos 7.6 guest os on vm, the cpu usage is very low on vm(100% idle), but on host, qemu-kvm reports 100% cpu busy usage. After searching some related bugs report, I suspect that it is due to the clock settings in vm's domain xml. My Openstack cluster uses the default clock settings as follow: And in this report, https://bugs.launchpad.net/qemu/+bug/1174654 it claims that can solve the 100% c= pu usage problem when using Windows Image Guest OS, but I makes some tests, the solusion dose not work for me. = Steps to reproduce =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D * create a vm using centos or redhat 7.6 image * using sar tool inside vm and host to check the cpu usage, and compare t= hem = Expected result =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D host's cpu usage report should be same with vm's cpu usage = Actual result =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D vm's cpu usage is 100% idle, host's cpu usage is 100% busy = Environment =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 1. Exact version of OpenStack you are running. # rpm -qa | grep nova openstack-nova-compute-13.1.2-1.el7.noarch python2-novaclient-3.3.2-1.el7.noarch python-nova-13.1.2-1.el7.noarch openstack-nova-common-13.1.2-1.el7.noarch 2. Which hypervisor did you use? (For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...) What's the version of that? # libvirtd -V libvirtd (libvirt) 3.9.0 # /usr/libexec/qemu-kvm --version QEMU emulator version 2.6.0 (qemu-kvm-ev-2.6.0-28.el7_3.6.1), Copyright (= c) 2003-2008 Fabrice Bellard = Logs & Configs =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D The VM xml: instance-00005022 7f5a66a5-****-****-****-75dec****bbb ******* 2019-05-20 03:08:46 2048 12 2048 0 1 **** **** 2097152 2097152 1 1024 /machine Fedora Project OpenStack Nova 13.1.2-1.el7 64ab0e89-****-****-****-05312ef66983 7f5a66a5-****-****-****-75decaf82bbb Virtual Machine hvm IvyBridge destroy restart destroy /usr/libexec/qemu-kvm