Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp480921imu; Fri, 16 Nov 2018 05:38:22 -0800 (PST) X-Google-Smtp-Source: AJdET5dqsL/ufOUrw1PTh2S+CLAQQf1GF8a1wZSFKqTpy4bZfEwDQVdrBWFKmc9zi1DTB4XS3Ywp X-Received: by 2002:a63:200e:: with SMTP id g14mr10001710pgg.235.1542375502783; Fri, 16 Nov 2018 05:38:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542375502; cv=none; d=google.com; s=arc-20160816; b=tvkmZ1jvANpkHa39XhigK07JTPdX4/o4aS0hwecl24CNM3H7YxpPcNRPbYZ6T69YZK 4S2Qgz8chAretpaAYWj9mkx2C9ItRtZLS1ac1colKLXM/P5Jz9bZQcblw2Yp+K+Z6yAw AJL2ZPRbUF4EErofHsMLyaLv1aANIBEnWIe389I42Gr2CjR+wXuEdKHLYcVTiiJBSdFA 3b4o2pKWIpawqgQx/8chK4FM/G6p71n4QFRCLHRHoTuOJr0MkkaQ9WDxGQQT6QVexp5s L/ugP0rAMnwYc5WgaOcMMCyOxBC01OG4k3fgE/9li2s2Dyy3qXGEgqfy3YtaLZ4j7MDS oiXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from; bh=3+ppL4P6H0037CikFtJ2Th5dd4SzJg1zjPKtGB9YXbg=; b=kouh+bC5p/lWJD6yvlDgnvpZw64oY7yGCNNw2qvsxQX/+7/HdrRzUlUlkAQS0SUvpr oyH3nxGz+OWGUfVqdRCRTPPnQcOGxfFy0DkZBg5J54IgqTYuv+pRUh/uar6QMqrHmf/c syjvHOGzl1AlsJ9BglJ2I8y0YsgA3TAEKalpvGxSXuOmqbB3WoT/hGWYt1E1XCseGAik ZQQ9TAH65SPvZ9/xisXz6DTXPZ1WeFBya/vJMnJ0GytMKJZ72o+mjNX7zM24DBbo67bD t4nvNhFyf/X2ftmafFzVOkoOKMM/uwjzAdNcRMxRzigsXCOWAp4LDw1fukxOLwPFCE45 aGsg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b7-v6si31884098pgm.540.2018.11.16.05.38.07; Fri, 16 Nov 2018 05:38:22 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389960AbeKPXtZ (ORCPT + 99 others); Fri, 16 Nov 2018 18:49:25 -0500 Received: from mx1.redhat.com ([209.132.183.28]:55304 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727711AbeKPXtZ (ORCPT ); Fri, 16 Nov 2018 18:49:25 -0500 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 18793723D9; Fri, 16 Nov 2018 13:37:00 +0000 (UTC) Received: from vitty.brq.redhat.com.redhat.com (unknown [10.43.2.155]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A17AA5C6A5; Fri, 16 Nov 2018 13:36:55 +0000 (UTC) From: Vitaly Kuznetsov To: Ahmed Soliman Cc: Anders Roxell , Shuah Khan , linux-kselftest@vger.kernel.org, Paolo Bonzini , Peter Xu , linux-kernel@vger.kernel.org, Andrew Jones Subject: Re: KVM selftests are failing In-Reply-To: References: <20181114180807.6crs7awhvo26ldbr@hawk.localdomain> <20181115090203.5z25gwa2yznj6mmu@kamzik.brq.redhat.com> <20181115145028.qijg7hjswcuabrt2@kamzik.brq.redhat.com> <87efbmqore.fsf@vitty.brq.redhat.com> Date: Fri, 16 Nov 2018 14:36:54 +0100 Message-ID: <8736s1qh3d.fsf@vitty.brq.redhat.com> MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Fri, 16 Nov 2018 13:37:00 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Ahmed Soliman writes: > Hello once again, > > I noticed that there is still more problems with kvmself test (at > least on my machine) > > Any test that would successfully reach the guest's code immediately > VMexit by a shutdown. > > $ ./vmx_tsc_adjust_test > ==== Test Assertion Failure ==== > x86_64/vmx_tsc_adjust_test.c:156: run->exit_reason == KVM_EXIT_IO > pid=8499 tid=8499 - Success > 1 0x00005604f07bd36c: ?? ??:0 > 2 0x00007f5c0dc53ae6: ?? ??:0 > 3 0x00005604f07bd4b9: ?? ??:0 > Got exit_reason other than KVM_EXIT_IO: 8 (SHUTDOWN) > Hm, this is weird. Do other KVM users, e.g. qemu work on this host? Are you sure this happens on the first VCPU_RUN invocation? Could you try doing trace-cmd record -e kvm ./x86_64/vmx_tsc_adjust_test && trace-cmd report to see if there's anything suspicious? -- Vitaly