Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp4200646yba; Tue, 23 Apr 2019 17:21:17 -0700 (PDT) X-Google-Smtp-Source: APXvYqzto/1itxCFMjvfM1BYhflMEa3f1QmvyXaOnHS+Io0P7N19a3mih8zXm6oRhjrlIeaf8rcd X-Received: by 2002:a17:902:758b:: with SMTP id j11mr27159195pll.87.1556065277720; Tue, 23 Apr 2019 17:21:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556065277; cv=none; d=google.com; s=arc-20160816; b=sNKVCbYsztVVrQllud/gvPy6cTPa3OvnFH6vp+HKHIy2u+m9GsCuP7TJYoUciaZeG0 4q+kERAI/K7B2kGiE8ctUXsSBoO1w3jnPFX3QgVOXINJgm20PkEy+C6Rgvl9u8ewO7nR fNuG1nP9Np5lc0F7ql/SQut+xQlFvMS6vmFE3/XZTvw+EnIXK7gegaLGKmGV1xqCVDub UgfKUBd9f8vrslDBJ2XQGXQTnSPc4ElxfSW7ibLmA7Hx2MqfYP13zq4GPytp7uqmlHcT z6qiDfdPHXEYja0wAM6q+a6iym69A9xz5qDr1gnoaABSnjAVaFu9v+JC3KK3CUYJQs3g B4fw== 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=9PDrjcypVdKZ1d+PoA6DkGR71bB/ENH+s9K5mQ3D6kE=; b=ywZGJ/s9yld4OdzsyKt5EriUsSEQXvcBbGeil4qF2M9mU9WUtwOxrRhPxzJmSNKvvX u00ytqdrgTR7isaW5AFgou9tkYCbv6gjiMFXQaelqoyXoLmfL8oc+SZgQ3ZLNtj/RyO1 9SkgaRpZeTmYGkXi1TyHtOUb6xMgtjQo+e/b1ebRGrfQTcDk/2J+f/UDUWy9mmEfvGeG tI9A/1F+RTNtz8EJvJCDTyGOCMCk+Gs9TheLEfTA320mhN29BNhgUaRSl8GIMY207BzU MajDNQUAySQv3Ua76G4mjbaANxGgUPjSWoVT+TvrTC8/AEWy3AogLyOTwvpE83mTLC7x XsGQ== 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 o123si18378998pfb.116.2019.04.23.17.20.59; Tue, 23 Apr 2019 17:21:17 -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 S1728951AbfDXASm (ORCPT + 99 others); Tue, 23 Apr 2019 20:18:42 -0400 Received: from mga02.intel.com ([134.134.136.20]:18963 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728353AbfDXASm (ORCPT ); Tue, 23 Apr 2019 20:18:42 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Apr 2019 17:18:42 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,387,1549958400"; d="scan'208";a="340208899" Received: from sjchrist-coffee.jf.intel.com (HELO linux.intel.com) ([10.54.74.181]) by fmsmga006.fm.intel.com with ESMTP; 23 Apr 2019 17:18:41 -0700 Date: Tue, 23 Apr 2019 17:18:41 -0700 From: Sean Christopherson To: Greg Kroah-Hartman Cc: Paolo Bonzini , Takashi Iwai , Jiri Slaby , linux-kernel@vger.kernel.org Subject: Re: [REGRESSION 5.0.x] Windows XP broken on KVM Message-ID: <20190424001841.GA14422@linux.intel.com> References: <20190423202317.GA15182@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190423202317.GA15182@kroah.com> 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 Tue, Apr 23, 2019 at 10:23:17PM +0200, Greg Kroah-Hartman wrote: > On Thu, Apr 18, 2019 at 09:56:02AM +0200, Paolo Bonzini wrote: > > On 18/04/19 09:38, 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. > > > > No, it's the first time I hear this and I actually test Windows XP > > before every pull request I send to Linus... I'll download 5.0.x and > > test it there. > > Any further ideas about this? I followed up on the bugzilla to request more information. My best guess at this point is that the issue is related to an older version of Qemu or a specific emulated device, but without additional details we're stuck.