Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1157765yba; Thu, 18 Apr 2019 16:33:49 -0700 (PDT) X-Google-Smtp-Source: APXvYqxg1KSi9GtcuXR4HleFKGMtR6xk9sLdSsWqCr2V0n1XT3AMGv8C0NnoZ5VZii388oKF0lGj X-Received: by 2002:a17:902:c1:: with SMTP id a59mr289878pla.176.1555630429724; Thu, 18 Apr 2019 16:33:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1555630429; cv=none; d=google.com; s=arc-20160816; b=BGlTsNJ4Wv7jzMRBQoO3iaO5mF3xxhtYRloFVhBVwIy14C8TI1v1XQATbLO+BP55DG axEWUL2bgiufOXYbO6+aN/ap1dC6OQW0yovwNddbzuRnV3lTLsDVwKv/9YPGegSUVA8N 8TCc4qUAe6kJESmb88r56q0dzAOY3+bEKdG/fmiYT5BaShTMKoNMtN+6MgoyfudoP+5V Q/q1/oUqV05WuY7SNQuKex133PR8N03PToMW694nXRUNGrjzePRKQ3K1gOIblJgCWI4R e3r3mhb2Gpf2RLuB43CfeYUeuZ2VipZo+vfNeUmVYOIbcBmqqS8ZGmlN5aSg6xUQ7puT XmUw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=ywfaOXTZJ2zxz/dHYMmSviCBHe2TwgFtto9ZFn+vsFw=; b=hqQOVGd+g/sNszDvcjCywXY/RiJKNTinMdyHINo6SJXGp3NuFQ5MsrGBgXcEIjJ2xa oDQ6+CXcwFaAQ1XIZMw8786wgTw1cUGVhfT2LzGPkQW5LpeNXENqn3Ull5g9ULFJnEp1 VZeGdhZ3BLS4K/YcFZ8al7rB59535zAgligghS/ml3vMTOHlkaIQxINeFh5rGzA9DhTa K9o2pcvG4V2kkZbdtmGYFyY9SVN4n5YNPMYILeG0ExoXeQWgvh3g7KFtwsY3LT1sS2cX aEIIt9FHVX5f5icpIY33C1sIVkOT0EbcyMGCr82puaXndGozzs5s8KzMD+t5TzLHAnLo vJmg== 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=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i19si3583808pfr.246.2019.04.18.16.33.34; Thu, 18 Apr 2019 16:33:49 -0700 (PDT) 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=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726844AbfDRXbW (ORCPT + 99 others); Thu, 18 Apr 2019 19:31:22 -0400 Received: from mga02.intel.com ([134.134.136.20]:4701 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726322AbfDRXbV (ORCPT ); Thu, 18 Apr 2019 19:31:21 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Apr 2019 16:31:21 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,367,1549958400"; d="scan'208";a="150578893" Received: from sjchrist-coffee.jf.intel.com (HELO linux.intel.com) ([10.54.74.181]) by FMSMGA003.fm.intel.com with ESMTP; 18 Apr 2019 16:31:20 -0700 Date: Thu, 18 Apr 2019 16:31:20 -0700 From: Sean Christopherson To: Takashi Iwai Cc: Greg Kroah-Hartman , Paolo Bonzini , Jiri Slaby , linux-kernel@vger.kernel.org Subject: Re: [REGRESSION 5.0.x] Windows XP broken on KVM Message-ID: <20190418233119.GF17218@linux.intel.com> References: <20190418075328.GA19532@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 18, 2019 at 10:05:34AM +0200, Takashi Iwai wrote: > On Thu, 18 Apr 2019 09:53:28 +0200, > Greg Kroah-Hartman wrote: > > > > On Thu, Apr 18, 2019 at 09:38:52AM +0200, Takashi Iwai wrote: > > > Hi, > > > > > > we've got a regression report on the recent 5.0.x kernel, starting > > > from 5.0.6, where Windows XP can't boot on KVM any longer. > > > > > > The culprit seems to be the patch > > > KVM: x86: update %rip after emulating IO > > > with the upstream commit 45def77ebf79e2e8942b89ed79294d97ce914fa0. > > > Reverting this alone fixed the problem. > > > > > > The report is found at openSUSE bugzilla: > > > https://bugzilla.suse.com/show_bug.cgi?id=1132694 > > > > > > Is there already a followup fix? If not, we need to revert it from > > > stable, at least. > > > > Is this also a problem in 5.1-rc5? > > Only 5.0.x has been tested, so far. > I'll ask the reporter to try 5.1-rc if Paolo can't reproduce the > problem in his side. I'd be surprised if 5.1-rc* changes anything relative to 5.0.x, the commit in question is fairly isolated and specific. Can we get the Qemu version and command line that is being run?